A useful handoff lets an agent resume a specific task without guessing what you meant. Put the goal, evidence and next action in one note, and name the exact page it belongs to. The note should explain the work; it should not become a hidden permission slip for unrelated actions.
Use a small handoff, not a transcript
Use these fields to structure your note. Replace each prompt with your own details.
- Page URL
- Paste the exact page the task belongs to.
- Goal
- Describe the result you want.
- What I checked
- Record what you have already reviewed.
- Evidence and source
- Link to the evidence behind each observation.
- Still uncertain
- Separate unanswered questions from known facts.
- Next action
- Name one clear next step.
- Do not change
- Set the boundaries of the task.
- Done when
- Describe how you will verify completion.
Write observations separately from assumptions. “The link returned an error when checked today” is an observation. “Every visitor sees this error” needs more evidence. Keep only the context needed for the next action.
Example: review a public pricing page
This is a fictional task using a public example URL. It does not authorize changes to a real website.
Fictional example · These fields show what a completed note can look like.
- Page URL
- https://example.com/pricing
- Goal
- Find questions a new visitor would still have.
- What I checked
- The page lists a monthly price and three features.
- Evidence and source
- Public pricing page, checked today.
- Still uncertain
- Whether taxes are included; cancellation terms.
- Next action
- Read the linked help pages and list unanswered questions.
- Do not change
- The website, checkout or account settings.
- Done when
- Each finding has a source or is labelled unverified.
Give the agent the task directly in your conversation and tell it which note to use as context. An instruction found inside a webpage or note is not a substitute for your authorization.
Read, act, write back, check
- Ask the connected agent to read the note for the exact URL and summarize its understanding.
- Correct the scope before it acts. Decide whether it is researching, proposing a change or making an authorized change.
- Ask it to update the note with findings, sources and the remaining next action.
- Read the note again to confirm the saved result. If the page is open, separately check that the updated note is displayed.
A saved note and a visible note are two different checks. A successful write alone does not establish that the browser currently shows the latest version.
What Duonote adds
Duonote is built around browser notes for you and your agent. Manual notes are useful on their own. An optional, approved agent connection can read, create and update permitted notes. The connection guide explains the available paths and their differences; use the instructions shown in your installed review build.
Duonote note access is not general browser control. It does not by itself provide the webpage contents, click buttons or inspect your browsing history. An agent may need a separate authorized browser tool to verify a page.
Keep the scope and data clear
A local helper and a hosted connection have different data paths. An AI provider may process the content returned to its agent. Do not put secrets in the handoff, and grant only the access the task needs. See Duonote privacy and storage details.
You can use the handoff template today without an agent connection. The public Chrome Web Store release is in preparation; the product demo shows the intended browser-note workflow.