Agent Runs now available in the Vercel MCP and CLI
Your coding agent can now pull its own Agent Runs traces—reasoning, tool calls, token usage—from Vercel via MCP or CLI, so it can debug its runs and refine skills from real production behavior.
**The gist** Vercel exposed **Agent Runs** through the **Vercel MCP** and **CLI** for the **eve** open-source agent framework, whose traces auto-ingest on deploy. Four MCP tools (`list_agent_run_projects`, `list_agent_runs`, `get_agent_run`, `get_agent_run_trace`) and four CLI commands (`vercel agent-runs projects/list/inspect/trace`) surface turns, messages, reasoning, tool calls, and token usage.
**Why it matters** An agent can now inspect its own past runs to debug failures or update its skills—ask it "show me the latest production runs" or "update skills from recent runs." Every CLI subcommand supports **`--json`**, and traces render as **markdown when piped**, so agents without MCP access can shell out to the CLI directly.
**The gist** Vercel exposed **Agent Runs** through the **Vercel MCP** and **CLI** for the **eve** open-source agent framework, whose traces auto-ingest on deploy. Four MCP tools (`list_agent_run_projects`, `list_agent_runs`, `get_agent_run`, `get_agent_run_trace`) and four CLI commands (`vercel agent-runs projects/list/inspect/trace`) surface turns, messages, reasoning, tool calls, and token usage. **Why it matters** An agent can now inspect its own past runs to debug failures or update its skills—ask it "show me the latest production runs" or "update skills from recent runs." Every CLI subcommand supports **`--json`**, and traces render as **markdown when piped**, so agents without MCP access can shell out to the CLI directly. **Watch out** Trace ingestion is tied to the **eve** framework deployed on Vercel; if you run a different agent stack this doesn't apply. Setup needs the Vercel MCP installed or the latest `vercel` CLI.