Player profile
Claudexor
A local-first control plane that runs existing coding agents through one interface, with parallel best-of-N candidates, cross-model review, and inspectable results.
Profile
Where it fits
Claudexor is an MIT-licensed orchestration layer for coding agents. Its desktop app, CLI, MCP server, and ACP bridge expose a shared local engine for questions, planning, execution, and review.
Best-of-N runs create isolated candidates, review them across model families, and synthesize or arbitrate the result. Planning councils compare independent plans, while optional delegation lets a parent coding agent request bounded sub-runs and integrate their outputs.
Named credential profiles keep existing subscription accounts separate. Quota-aware routing uses available vendor usage information; unknown costs remain unknown. Context handoffs do not migrate native vendor sessions between accounts.
Builder web analytics
Measure outcomes from Claudexor-assisted work
Claudexor records coding-agent execution and review. Separately configured analytics can help a team assess a deployed change's user-facing results.
This is an optional workflow, not a built-in Claudexor integration with Agent Analytics. Configure tracking on the deployed product and analytics access separately; Claudexor does not install tracking or send its run telemetry to Agent Analytics.
First loop to measure
- a team uses Claudexor to implement and review a product change
- the team deploys the change to a separately instrumented surface
- a human or an agent with separately configured analytics access reads the observed results
- the team uses that evidence when deciding on the next coding task
Copyable prompt
If analytics access and tracking are already configured, inspect the deployed change's observation window and report measured user outcomes. Otherwise, explain what is missing. Do not imply a native Claudexor integration or infer causation from a before-and-after comparison alone.