Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for developers who already use Claude Code, Codex CLI, Cursor, Gemini CLI, or OpenCode and want a lightweight workflow layer around those runs instead of another chat app.
Who should use it
Who should skip it
Move on from OracleNep/AgentFlowDesk if the licensing terms, language support, or platform requirements do not fit your project.
About this signal
OracleNep/AgentFlowDesk is tracked by RepoRadar as a workflow manager in the Developer Tools section. It was first seen on 2026-06-29 and last updated on 2026-06-29. The current verdict is 'try now' with a Gold tier and easy setup difficulty. OracleNep/AgentFlowDesk leads on workflow potential (9.5) and setup ease (8.8); its lowest signal is momentum (6.0), so factor that in before investing setup time. 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 OracleNep/AgentFlowDesk a composite score of 8.0 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 1.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 vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
AgentFlowDesk is built to launch and track coding-agent commands on your machine, so treat the first rollout like any other local code-execution workflow and keep it scoped to non-sensitive repos until your checks are dialed in.