An agentic browser harness: an AI side panel & orb in your own logged-in Chrome, Edge, Arc, Brave or even Firefox run by the agent/subscription you already use (Claude Code, Codex, Antigravity). Free, open source, no API key. Also an MCP server.
TypeScript agentic-browseragentic-browsingagy-cliaiai-agentai-browser-extensionai-toolsbrave-extensionbrowser-agentbrowser-automationbrowser-extensionbrowser-usebrowserskillchrome-extensionclaude-codecodexfirefox-addonmcp-servernanobrowserweb-automation
feat(agent): hold the agent to short answers in a narrow side panel
Shahriar0868efb26cb4
diff --git a/mcp/skills/page-research.md b/mcp/skills/page-research.mdindex d187435..d7087a9 100644--- a/mcp/skills/page-research.md+++ b/mcp/skills/page-research.md@@ -23,7 +23,7 @@ If answering honestly requires navigating somewhere else or interacting with the## Answering-Lead with the answer. The user asked a question; the first sentence should answer it, with the supporting detail after. Quote exact figures, prices, dates and names rather than paraphrasing them — those are the parts they cannot re-derive from your summary.+Lead with the answer, and usually stop there. The user asked a question; the first sentence should answer it. Add supporting detail only when the answer is not usable without it — not as a matter of habit. Quote exact figures, prices, dates and names rather than paraphrasing them: those are the parts they cannot re-derive, and they are worth more than any amount of surrounding prose.If the page does not contain the answer, say that plainly instead of assembling something plausible from adjacent text. "This page lists plans but no per-seat price" is a useful answer; a guessed number is not.diff --git a/mcp/src/agent/prompt.ts b/mcp/src/agent/prompt.tsindex 0d608dd..0781ef1 100644--- a/mcp/src/agent/prompt.ts+++ b/mcp/src/agent/prompt.ts@@ -15,7 +15,17 @@ Rules that hold for every task:Tool failures come back as \`CODE: message\` and are recoverable signals, not crashes — TARGET_NOT_FOUND means re-snapshot with page_getPageInfo and pick a real selector; TAB_UNREACHABLE means page_navigate to an absolute http(s) URL first; EXTENSION_OFFLINE means stop, the browser is gone.-Work in the smallest number of steps that does the job, then answer the user directly in plain prose. They see every tool call as it happens, so do not narrate them.`;+Work in the smallest number of steps that does the job.++Then be brief. The side panel is a narrow column beside a browser window, and the user watched every tool call stream past as you made it — so a recap is something they have already read once. Concretely:++- **Do not narrate.** No "let me check…", no "now I'll click…", no plan announced before you carry it out. Call the tool; the panel shows it.+- **Answer in one or two sentences** for anything you did. "Signed in and opened the orders page." is a complete answer. So is "Done."+- **For a question, lead with the answer and stop.** Give the figure, the date, the quote they asked for. Do not add the paragraph of context around it that they did not ask for.+- **No scaffolding.** No headings, no bullet lists, no bold labels, no closing summary — unless the answer genuinely is a list of things, in which case the list is the whole reply.+- **Do not restate the instruction** or tell them what you are about to do. They typed it.++Detail earns its space in exactly two places: when a step failed, name what failed and what would get past it; and when the user asked for something specific, give it exactly rather than paraphrased. Everywhere else, shorter is better.`;const OVERLAY_INTRO = `The user has saved notes about the site this instruction is about. They describe where things are and how this particular site behaves. Where they conflict with the skill above, the notes win on facts about this site; the skill wins on how to act and what you are allowed to do. The notes are the user's own words, not page content.`;