phuryn/product-engineering / app-stack/skills/embedded-agents-messages-api
embedded-agents-messages-api
VerifiedBuilding, adding or wiring up an agent or an agent chat inside a Next.js app: embed Claude agents on the Messages API, the default way.
Embedded agents — Claude API
Use the Messages API by default for a new product. The Anthropic SDK's tool runner (client.beta.messages.toolRunner) drives the loop inside the app's process. The agent has exactly the wrapper's tools, with nothing built in. Both embedded-agent skills run the same agent directories, which move between them unchanged (playbook § 10). Apply embedded-agents-agent-sdk only when the agent needs what only the Claude Code engine has, or when the product already runs it. That SDK starts the engine as a subprocess, provides built-in file and shell tools, and needs a long-lived Node host.
Read the product's own agent instructions before changing its embedded agents. Start with its root AGENTS.md or CLAUDE.md, and tell any subagent spawned for this work to read it too. Its rules on secrets, environment variables, validation, callers, tests and release apply here. Read reference/playbook.md before changing the wrapper's contract or explaining it in depth. It holds the full playbook and the measurement behind every choice.
Keep request, caller, storage and UI ownership in the app. The agent owns reasoning and tool choice. An agent is a directory, .claude/agents/<name>/, with AGENTS.md as its whole system prompt. It may also hold knowledge/, agent-local skills in .claude/skills/, and .mcp.json. One wrapper function, askAgent, runs any agent. No agent name appears in code.
1. First use: install the wrapper
Search for askAgent before installing another wrapper. If it exists, skip to § 2. If it imports @anthropic-ai/claude-agent-sdk, the product uses the other skill; migration is in playbook § 10. Otherwise:
-
Create only the smallest requested app when none exists. Use Next.js App Router in TypeScript, which these files target. Add nothing unasked for: no database, sign-in or billing for a local prototype.
-
Install the missing dependencies. Run
npm i @anthropic-ai/sdk @modelcontextprotocol/sdk zod server-onlyandnpm i -D vitest. Pin exact versions: the tool runner is marked beta in the TypeScript SDK, so an upgrade is re-tested, not assumed. -
Copy the wrapper, route and tests, changing only import paths.
From this skill To the app templates/agent.tssrc/lib/agent.ts— the wrappertemplates/agent-mcp.tssrc/lib/agent-mcp.ts— an agent's MCP servers, opened per runtemplates/route.tssrc/app/api/agents/route.ts—GETlists agents,POSTstreams onetemplates/agent.test.tstests/unit/agent.test.ts— the contract, insidenpm test, no model calltemplates/agents.live.test.tstests/live/agents.live.test.ts— every agent against the real modelThe tests import
@/lib/agentand@/lib/agent-mcp, so Vitest needs the same@alias astsconfig.json. The live test gets its own Vitest config (includetests/live/**/*.live.test.ts,testTimeout: 180_000,fileParallelism: false, andprocess.loadEnvFile('.env')in atry) and a script,agents:live. It costs money, so it stays out ofnpm testand the gate. -
Set each required secret per environment and never commit it. Set
ANTHROPIC_API_KEYand every secret referenced by an agent's.mcp.json; applyenvironments. On a developer's machine the SDK also reads a profile fromant auth login; a deployed product always uses the key. -
Keep the contract. Every choice in
agentRequest()andaskAgent()is pinned by the unit test and explained in the playbook (§ 3, § 7). Change one only after re-measuring it.
2. Add an agent
- Create the agent directory and write its complete instructions. Run
node <skill dir>/scripts/new-agent.mjs <name> [--knowledge] [--mcp], then fill inAGENTS.md: role, sources, output format, refusals. It is the agent's whole system prompt, with no product preset underneath. A fixed sign-off line is the cheapest live-test proof that the instructions are in force. - Confine knowledge tools to knowledge and load skills as instructions. Put files in
knowledge/, and tell the agent inAGENTS.mdto answer only from them. It getslist_files,search_filesandread_file, confined toknowledge/(playbook § 5). Name those tools inAGENTS.md, not Claude Code's Read/Glob/Grep. Put agent-local skills in.claude/agents/<name>/.claude/skills/<skill>/SKILL.md, withdescription:frontmatter. The wrapper lists them in the system prompt; the agent loads one withload_skill. A skill is instructions and reference files; nothing in it runs. - Allow only MCP tools the agent's job needs. Put servers in
.mcp.json, with secrets as${VAR}, never literal. Runnode --env-file=.env <skill dir>/scripts/discover-mcp-tools.mjs <name>to list each server's tools, then restrict itsallowedTools. An unlisted tool is never shown to the model. Commit the agent's.mcp.json, which holds no secrets. Ifgit check-ignorereports it ignored, the repository's.gitignorehas an unanchored.mcp.jsonrule meant for the root file. Anchor it as/.mcp.json. - Discover agents from their directories rather than hardcoding the UI list.
listAgents()finds the directory,GET /api/agentsreturns it, and the UI's picker shows it when users choose between agents. Fix a UI that hardcodes that list. - The instruction file is always
AGENTS.md. Asked for another name, createAGENTS.mdand say why: the wrapper loads onlyAGENTS.md, and the same directory must also run under the Agent SDK skill, which loads some other instruction files on its own. - Add a live test for each promise worth pinning. Examples include citing, refusing and answering only from its files. Put it beside the generic test.
3. Tools that act for the caller
Build caller tools per request after resolving the caller. For reads or changes to the caller's records, such as invoices or settings, build the app's own tools inside the route. Pass them as askAgent({ …, tools }):
const tools = [
agentTool({
name: 'list_invoices',
description: "List the signed-in subscriber's invoices.",
input: {},
run: async () => JSON.stringify(await listInvoices(caller)), // closes over the caller
}),
];
- Identity is closed over, never a parameter. No tool takes an email, user, customer or account id: the model cannot ask for anyone else's records because no input can name them. Pin it with a unit test that reads every tool's
input_schema.properties. - Validate tool input and control which failures reach the model.
runreturns the text the model reads. A refusal or a planned failure throwsToolError(text); the model reads it as an error result. Any other exception reaches the model as a fixed sentence, never its message. Input is validated against the zod shape beforerunsees it. - End the run after tools that only attach to a reply. Put a link or a list the app draws in
askAgent({ …, closingTools: ['share_link'] }): when a response that already has text calls only such tools, they run and the run ends. Otherwise the model, asked again, may write its reply a second time (playbook § 7). - Have code decide risky or one-way actions proposed by tools. A model may propose but never decide what cannot be taken back (
saas-authorization): the tool stores a proposal, the app shows a button, the click runs it. Links and buttons travel through the app, not through model text. - Put per-run facts in
context, never user text. It supplies facts such as the caller's identity to the system prompt afterAGENTS.md.
4. Examples — only when asked
Copy finished examples only when asked for or described. The examples/ agents are: answering only from local product-management knowledge files (knowledge-agent), or live-web research through Perplexity with citations (research-agent). Copy examples/<name>/ to .claude/agents/<name>/ and examples/<name>.live.test.ts to tests/live/. research-agent needs PERPLEXITY_API_KEY. Otherwise, never copy them.
5. The chat UI
Build the chat UI for this product and its agent flow. There is no template. It must do the following:
- Fill the picker from
GET /api/agentswhen users choose agents. A product may run one front agent and show no picker; the route still checks the name againstlistAgents(). - Send the conversation to the route and read server-sent events.
POST { agent, prompt, history }to/api/agentsand read:{ text }chunks (one per model response), then{ done, agent, metadata }or{ error, agent }. The parser is in playbook § 7. - Store the agent on every message; identify replies with several agents. When there is more than one agent, show it on each reply. History is the conversation so far, kept in client state unless the product asks to persist it.
- Render agent output as plain text or sanitized markdown. Never render raw HTML: it is untrusted text, like anything a user typed. Show an
errorevent instead of spinning forever.
6. Explaining routing and the tool boundary
Validate the requested agent before routing it to the wrapper.
- UI
POST /api/agents { agent }- the route validates the body and requires the name to be in
listAgents() askAgentagentRequest()accepts only a plain directory name and reads.claude/agents/<agent>/- the tool runner sends the request, runs the tools the model asks for, and repeats
- events stream back.
Pin every layer of the tool boundary with a test. See playbook § 4:
- The tool list is the boundary. The model can call only what
agentRequest()put intools: the caller's own tools, the file and skill tools when the directory has knowledge or skills, and the MCP tools its.mcp.jsonallows. Nothing is built in: no shell, no web, no file system beyond these. - Resolve every file path, including symlinks, before permitting access. File tools refuse anything outside
knowledge/or the skill's own directory, and any.envfile. - Keep unlisted MCP tools and app secrets outside the boundary. A server's unlisted tools never reach the model; a stdio server starts with a safe environment allowlist plus its own
env, never the app's secrets. - Refuse bad input and hide exception messages from the model. A tool's exception reaches the model as a fixed sentence; bad input is refused by its schema before it runs.
- Check turn and budget caps between responses before running tools.
maxTurns(10 by default) andmaxBudgetUsdcap a run: the tools of the response that crosses one never run.
7. Before it leaves localhost
- Choose a Node host whose time limit covers the slowest run. No subprocess: any host that runs a Node process for the length of a run can host it — a long-lived server, or a serverless function whose time limit covers the slowest run (playbook § 8). A stdio MCP server is a child process per run, which rules out edge runtimes, and an agent's files must be in the deployment's trace.
- History is a client claim.
templates/route.tsacceptshistoryfrom the client,assistantturns included, and the wrapper sends it as the conversation — so a client can forge earlier turns, the agent's own included. That is acceptable for a read-only agent, which can only be talked into saying something to the person forging it. Before any tool acts on the caller's behalf, keep the transcript on the server and stop reading it from the request. - Resolve the caller and cap cost before opening the route. Before anyone but the developer can reach the route, resolve the caller there (who they are, which workspace, which permission:
saas-authorization) and set a per-actor limit and amaxBudgetUsd. - Run live tests before releasing any agent, prompt or model change. Run
npm run agents:livebefore any release that adds or changes an agent, its prompt or its model, record the run in the product's test-coverage map (which test proves what, and when it last passed), and describe each agent in its automation doc: what it may read, the exact tools it may call, and what the app enforces around it (shipping-artifacts). A feature that calls the model once, not as an agent, keeps the same live run and cost ceiling (playbook § 3).
How you can tell it worked
The agent answers in the deployed app using only the tools its role allows, and the live agent suite passes against the real model.
Running the scripts
Run these scripts from the app's repository root. <skill dir> is this skill's installation location: a plugin, ~/.claude/skills/, or the repository's own .claude/skills/. The scripts write into the current directory.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 466k | Updated | Claude CodeCodex | Verified | Install |
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 466k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |