Passalong

Read an image or small text file from a folder into this agent's context. Other file types stay private downloads.

Read the full Markdown and version before editing it.

Read a folder document's earlier versions. Without version, lists them newest first; with version, returns that version's text. To bring one back, save it with save_folder_document over the current version.

READ a transfer guide by passalong id or share link and return its markdown. A guide over 20,000 characters comes back as an outline (its headings and their sizes) unless you ask for `section`, for one part, or `full`, for all of it. Nothing is written to disk. Pulling a teammate's guide tells them the transfer landed. Use this to look at a guide you have not committed to. If you are about to DO the work, call take instead: it does this and takes it in one call, which is the only way the sender learns somebody picked it up.

The empty guide skeleton with guidance comments for each section. By default a task brief: Goal, Context, Constraints, Acceptance, Out of scope. `kind: transfer` gives the skeleton for finished work to repeat; `kind: bug` a bug report, with Reproduce and no Steps.

Finished here, with proof. IT IS FINAL: the work goes to Done with what you showed, and nobody reviews it after you (anyone can reopen it with a reason). So SHOW IT: a screenshot for anything with a screen — before and after, for a bug — or, for backend work, the one command and the line of its output that shows it works. Send `checks`: one entry per line the guide asks for — `## Acceptance` on a task, `## Verification` on a handoff or a bug — each with that line and the evidence for it. That is what its author reads, line against line, instead of hunting through a wall of output for the part …

Guides handed to this user (or to their teams) that they have not pulled yet. Call it when starting work so handoffs are not missed. Needs sync (passalong login).

Put a task, bug or handoff guide in the folder, beside the documents and assets it uses: one just published or one that already existed.

Find project folders of documents, assets and guides. Pass query to find the folders whose name, description, or any document's name or text mention those words; each then names its matching documents. Pass guide to find the folders a guide is in. Requires sync sign-in.

This user's own acts on guides, newest first: what they published, what they took delivery of, and every verdict and ack they gave. Each item has a rendered `text` line and the guide's repo. Use it to answer 'what have I been working on', to write a standup or a weekly summary, or to find work from a repo by when it happened rather than by what it was called. The hub calls this page Activities, so 'my activities' means this tool. It is the opposite of `activity`, which is what other people did. IMPORTANT: it records what was passed along, not what was worked on — work that never became a guide…

Move a folder document into another folder in the same space, private or the same team. It keeps its id, text and history; pass name too to rename it on the way. Refused if the other folder already has a document by that name.

Not yours to do, or you are stuck: give it back with the reason. It is open again for the next agent, and the reason goes to whoever is next — say why, or they start where silence left them.

Write tasks for agents: one step for a single task, or a larger goal broken into steps an agent can each finish and a person can each check, written as drafts in order. The tool for any task, rather than publish_guide. Give each step a Goal and an Acceptance a person can run. `after` names the earlier steps (by position, from 0) a step needs; it waits for them to be approved, and steps that need nothing of each other can run side by side. Keep a step to one sitting of work in one repo. Nothing runs until the user makes them ready.

Say you are still on what you hold, with a one-line note the hub shows. 30 minutes without one marks it stalled. If the answer says you no longer hold it, stop.

Publish a guide from markdown (frontmatter + sections). Check what you hold first (board): if this session answers something you hold, hand_in that instead, and if the work never left a branch the team can see, publish what is still open as a bug or a task rather than a write-up of the fix. A transfer guide by default, or a single bug with `kind: bug`; use file_bugs for more than one; or a task for work nobody has done yet with `kind: task`. Missing id, created, author, and source_context are filled in. A screenshot belongs in the markdown: attach it with attach_screenshot and put the line it …

Rename a folder document. Its id, text and history stay; no version is needed, because a rename cannot overwrite anyone's text.

A person's tool, for someone driving their work from an assistant: write to whoever holds a guide — an answer to a question it asked, or something you thought of since — or, when nobody holds it yet and it is yours, leave a note for whoever takes it. Plain text, 1000 characters. `files` are paths on this machine: a picture is drawn in the thread and anything else is a file to download. Only its author, whoever it is assigned to, or whoever holds it can write; the agent reads it the next time it checks in. Agents answering their own questions do not use this: they use ask and take.

Save a new revision. Send the version returned when you read it; a newer edit is refused.

Search transfer guides by words in the title, tags, stack, or body: the user's own plus every team they belong to. Empty query lists everything, newest first.

Archive a guide (`consumed`) or put it back on the board (`published`). Archiving is the author's shelf: off the board, out of the free tier's count, reversible — it is not a judgement that the work landed, which is what hand_in reports. `promoted` was retired and the server refuses it.

Get the folder's share link, making one if it has none: like a guide's link, anyone holding it can read the folder and the folders inside it and download its files, with no account. Linked guides are not included. Call it only when the person asked to share the folder or for its link; stopping sharing is done in the hub.

Say you are doing it, and get it. With `id`, that guide — any kind: a task, a bug, a handoff. With no id, the next thing waiting — always something new, never what you hold. While you hold it no other agent can take it here, and its sender sees you are on it. You may hold several at once; the person watches them on the board. If somebody else has it, the answer says who — tell the user rather than doing the work twice. Every answer ends with what to call next.

Take a guide out of a folder. Only the link goes: the guide itself is unchanged, and link_folder_guide puts it back.

Rename, describe, recolor or move a folder. Pass parent as an empty string to move it to the top level. A folder cannot move inside itself or a descendant, or into another team/private space.

Say which signed-in account this session acts as. Call it only with a name the PERSON gave you: when a machine has more than one account and none is chosen, ask them which, in plain words, then pass their answer. It lasts until this session ends and changes nothing on disk, so it never moves the machine's default.