Connect an agent

Connect Eve agents under Settings → Agents (admins only). RobotRock classifies each deployment at connect time and stores credentials in WorkOS Vault — secrets never live in Convex.

Hosted reference agent

The fastest way to try chat agents:

Open Settings → Agents.
Add a connection with URL https://robotrock-agent.vercel.app.
RobotRock verifies the deployment via GET /eve/v1/info and checks for the robotrock-ready hook.
Enable RobotRock agent in the agent list.
Open Inbox → Agents and start a conversation.

The hosted agent uses platform user-context JWTs (RS256) and a service token (ras_*) minted from Developer → Agent deployments. You do not copy ROBOTROCK_API_KEY onto the hosted deployment.

Self-hosted Eve deployment

For your own agent on Vercel, a VM, or local dev:

Deploy an Eve agent that advertises RobotRock readiness (see Build agents).
In Settings → Agents, paste the deployment origin (for example https://my-agent.example.com).
On first connect, RobotRock shows credentials to copy into your agent environment:
- ROBOTROCK_API_KEY — workspace API key (ll_*) for task and chat API calls
- ROBOTROCK_USER_CONTEXT_SECRET — HMAC secret for verifying user identity from the dashboard proxy
Enable the agent and test from the inbox.

Deployment kinds

Kind	How RobotRock detects it	Runtime auth
Multi-tenant	URL matches a verified entry in Developer → Agent deployments	`ras_*` service token + platform user-context JWT
Single-tenant	Unknown public HTTPS URL	Per-workspace `ROBOTROCK_API_KEY` + `ROBOTROCK_USER_CONTEXT_SECRET`
Localhost	`localhost` / `127.0.0.1` (dashboard blocks this in production)	Same as single-tenant

Multi-tenant deployments let one Eve app serve many RobotRock workspaces. Register the deployment origin in Developer → Agent deployments, verify ownership, and mint a ras_* token for the agent runtime.

Enable and configure agents

After connecting, the Agents card lists every agent slug from the Eve deployment:

Enable — show the agent in the inbox sidebar.
Display name — override the label shown in the UI.
Hide from inbox — keep the agent available for API/cron use without cluttering the sidebar.

Re-sync refreshes the agent list and Eve version from /eve/v1/info.

Disconnecting

Disconnecting removes the Eve connection and Vault credentials for that origin. Existing chat transcripts remain for audit, but live sessions cannot resume until you reconnect.

Troubleshooting

Symptom	What to check
"Not RobotRock-ready"	Deployment exposes the `robotrock-ready` hook on `/eve/v1/info`
Auth errors in chat	`ROBOTROCK_API_KEY` and `ROBOTROCK_USER_CONTEXT_SECRET` on self-hosted agents; reconnect to rotate
Agent missing from sidebar	Agent is enabled and not hidden from inbox
Local agent won't connect in prod	Localhost connections are dev-only; deploy to HTTPS

For building the Eve side, see Build agents.