Player profile
AgentRQ
An Apache-2.0 real-time human-in-the-loop task manager where AI agents and operators share tasks, replies, approvals, and workspace state through MCP.
Profile
Where it fits
AgentRQ is an open-source agent-human collaboration platform for Claude Code, ACP-compatible agents, Gemini CLI, and related autonomous agent sessions.
It belongs in Open Orchestrators because it turns human oversight into a first-class orchestration surface: one workspace per agent, task boards, real-time notifications, MCP tools, supervisor/workspace MCP endpoints, ACP gateway support, Claude channels, and Codex gateway integration.
The repository is Apache-2.0, Go/Vue-based, and documents a self-hosted stack with a Fiber API server, integrated MCP server, CoreMCP supervisor, SQLite persistence, Google OAuth, SSE notifications, and a Vue control panel.
Builder web analytics
Measure projects built with AgentRQ
AgentRQ keeps autonomous agent work connected to operator decisions. Agent Analytics gives those agents and operators user-facing outcome data after an AgentRQ-coordinated change ships.
Install Agent Analytics on the project surfaces AgentRQ agents change. Agent Analytics measures user behavior after deployment; it is not a replacement for AgentRQ's task board, MCP notification channels, approval queue, or workspace state.
First loop to measure
- an operator uses AgentRQ to assign, approve, answer, or coordinate one or more agent tasks
- the agent-built change ships to a website, docs site, app, onboarding flow, campaign, or product surface
- the changed surface reports visits, sources, CTA clicks, signup, activation, retention, funnels, and experiment events to Agent Analytics
- a later AgentRQ task asks an agent to fetch the Agent Analytics results and decide what to improve next
Copyable prompt
Use Agent Analytics for this project. If event reporting is missing, add the tracker and report events for this project surface, including AgentRQ-coordinated page, docs path, traffic source, CTA click, signup, activation event, approval flow, funnel step, or shipped task. Verify events are arriving. Then fetch the last 7 days and compare them with the prior 7 days. Tell me which AgentRQ-coordinated page, docs path, traffic source, CTA click, signup, activation event, approval flow, funnel step, or shipped task moved users toward value, where users dropped off, which sources mattered, and what my agent workflow should improve next.