razzant/ouroboroshub/agentrq-bridge

AgentRQ Bridge

Connects Ouroboros to an AgentRQ workspace via the MCP Streamable HTTP transport. AgentRQ is a task orchestration platform for structured human-agent collaboration.

What it provides

• 6 agent tools that map to the AgentRQ per-workspace MCP surface:

rq_workspace, rq_pull_next, rq_create_task, rq_reply, rq_update_status, rq_get_messages.

• Real-time SSE listener — a companion process that holds a

persistent SSE connection to the AgentRQ MCP endpoint and captures events (new tasks, human replies, permission verdicts) into the AgentRQ place through /presence/turn.

• Declarative widget showing live workspace connection status.
• Zero external dependencies — uses only Python stdlib (urllib,

json, socket, signal).

Setup

1. Deploy AgentRQ (Docker: docker pull agentrq/agentrq:latest or

self-host via SETUP.md).

1. Create a workspace in the AgentRQ UI. Copy its MCP URL and Token

from the workspace setup modal.

1. In Ouroboros Settings → Secrets, add two keys:

• AGENTRQ_MCP_URL — the workspace MCP endpoint

(e.g. https://WORKSPACE_ID.mcp.agentrq.com/ or http://localhost:8080/mcp/WORKSPACE_ID)

• AGENTRQ_TOKEN — the 16-char workspace token

1. Enable this skill and grant the two keys when prompted.

Agent workflow

rq_workspace()             → see mission + stats
rq_pull_next()             → dequeue next task
rq_update_status(ongoing)  → mark task in progress
... do the work ...
rq_reply(task_id, result)  → post result to task thread
rq_update_status(completed)→ mark task done

To request human permission for a sensitive action:

rq_create_task(title="Approve: deploy to prod", assignee="human")
→ human sees it in AgentRQ UI, replies allow/deny
rq_get_messages(task_id) → read the verdict

AgentRQ place

Connect provider agentrq with the workspace MCP URL (without credentials or query parameters) as the account ID. Tasks are conversations. Assigned agent tasks and human replies carry direct_message; other updates are captured without inventing addressing. Place notes and wakes govern participation. A places-capable Host is required; events never enter owner chat.

Notifications are persisted before submission. Provider event/message IDs are preferred; when absent, the complete notification supplies a stable digest. Host receipts and deferred references survive restart. Automatic replies use the task's reply operation and a live place check: Silent/Paused holds them. Uncertain physical delivery is recorded and never retried automatically. Events without a task ID are heard at the workspace; a reply without a task is held.