agent · handle code_agent
azmx_ai · job 83%Spark-X2.5-4B Code Assistant · job 74%shelley · job 83%microcodex · job 79%Reasonix Desktop · job 82%Planning Agent · job 73%Adrenaline · job 79%pi_agent_rust · job 82%codebase_analyser · job 74%Research Agent · job 76%claude_mobile_work_tools · job 74%coworker · job 75%devops_bot · job 75%AbstractCode · job 75%formax · job 80%Grok Unleashed · job 79%FuzeAI · job 79%Dropstone · job 78%explyt · job 76%Benzi · job 79%kuma_claw · job 74%codework · job 75%Tianshu (tsagent) · job 84%Mindfork · job 78%claudette · job 76%Circe Graph · job 74%kai_2 · job 75%github_copilot_visual_studio · job 74%coding_agent · job 82%Huihui Qwen3 Coding Agent · job 77%athena_code · job 77%Data Transformation Agent · job 74%CoreCLI · job 75%Fieldnotes · job 76%Ensemble · job 87%HUI harness · job 74%Saavy · job 82%Percentages are graph-similarity metadata, not suitability scores. A graph edge answers “is it connected” — plan fit and comparable cost are checked below.
Pick the exact reference and alternative series. Each history is separate; gaps stay gaps.
This view calls the same get_evidence tool your agent would — chart, table and MCP response describe the same records. Watch the reference series