Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for developers who want a local coding-agent workspace that can move between terminal and desktop UI while keeping the same sessions, tools, and config.
Who should use it
Who should skip it
Consider paean-ai/deeptide lower priority if you already have a working solution in this category.
About this signal
paean-ai/deeptide is tracked by RepoRadar as a developer tool in the Developer Tools section. It was first seen on 2026-06-27 and last updated on 2026-06-27. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. The standout signals for paean-ai/deeptide are workflow potential (9.9) and practical usefulness (9.0), while setup ease (6.4) trails — that balance shapes where it fits best. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned paean-ai/deeptide a composite score of 8.4 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 38.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
The default path pushes prompts and tool results to DeepSeek or another configured provider, so review which code and local context you are comfortable sending upstream; The cross-platform deeptide package currently rides on the Zero CLI stack and requires Bun at runtime, so validate the exact install path you want before standardizing on it across a team; The optional local DeepSeek runtime is hardware-hungry and not the default path, so treat it as a separate evaluation track rather than assuming every machine can run it well.