RobotRock
Chats & agents

Overview

RobotRock chat agents are durable Eve deployments you connect to a workspace. Team members chat with them from the Inbox sidebar, approve gated tool calls inline, and route work to other people when the agent cannot self-approve.

This is different from the SDK integrations elsewhere in these docs:

PatternWhere it runsBest for
Chat agents (this section)Eve deployment + RobotRock inbox UIInteractive assistants, internal copilots, demos
sendToHumanYour app / workerOne-off approval tasks from code
Trigger.dev / Vercel WorkflowBackground jobsDurable HITL waits without holding HTTP
MCPCursor and other MCP clientsCoding agents that poll get_task

Chat agents can still call sendToHuman (via the create_robotrock_task tool) to delegate inbox tasks — the chat updates when someone handles them.

Inbox experience

Once an agent is connected and enabled, it appears under Agents in the inbox sidebar (/{tenant}/inbox?agent=…).

  • Conversations — each session is a durable Eve chat owned by one person. Transcripts and transport state persist in Convex so you can resume after refresh.
  • New chat — start a fresh session from the agent's conversation list.
  • History — browse archived sessions per agent.

The legacy /agents route redirects into the inbox with the same query params.

Human-in-the-loop in chat

Eve agents can pause for human input in two ways:

Tool approvals

When the agent calls a gated tool (for example deploy_release or a high-value refund_charge), RobotRock renders an action panel in the chat thread. The user approves or denies; the agent continues from that decision.

ask_question

For choices that are not tied to a dangerous tool, agents should call Eve's ask_question tool. RobotRock renders buttons (or a radio form for more than six options). Plain-text bullet lists in the assistant message do not produce buttons.

See Build agents for agent-authoring rules.

Inbox task delegation

Agents with the RobotRock Eve integration can call create_robotrock_task to send work to someone else's inbox — for example routing a large refund to the finance group.

  • The chat shows a live task card with status (pending, handled, expired).
  • When the assignee handles the task, RobotRock resumes the Eve session with a summary so the agent can tell the user what was decided.
  • If you are not allowed to self-approve (wrong group, delegation rules), the UI explains why and links to the task in the inbox.

This complements — not replaces — sendToHuman from your own services. Use the tool when the chat user needs another team to decide; use the SDK when your backend creates tasks directly.

Quick start

  1. Try the hosted agent — in Settings → Agents, connect https://robotrock-agent.vercel.app. Enable RobotRock agent (robotrock-agent) in the agent list.
  2. Open Inbox → Agents → RobotRock agent and start a chat.
  3. Ask about sendToHuman, integrations, or request a demo refund approval to see delegation.

To run your own Eve deployment, see Connect an agent and Build agents.

Next steps

  • Connect an agent — hosted, self-hosted, and developer-registry deployments
  • Build agents — Eve + RobotRock tools, ask_question, and create_robotrock_task
  • Chats API — create chats programmatically with client.chats

On this page