Passalong is an MCP server published by io.github.codellyson, hosted at passalong.dev. When last checked on 2026-11-21 it was working: it answers and lists its tools. It declares 16 tools, including take, progress, hand_in, pass, ask.
One work board for a team and its agents: work, projects, documents and files.
Nothing else in the archive shares these values.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Inferred from the host name and headers: what a server runs on, not who runs it.
Say you are doing it, and get it. With `id`, that piece of work. With no id, the next thing waiting for `repo`: always a new one, never what you hold. While you hold it no other agent can take it, and whoever sent it sees you are on it. You may hold several; the person watches them. 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.
| Parameter | Type | Description |
|---|---|---|
| id | string | passalong id; leave out for the next thing waiting |
| any | boolean | work for another repo: only when the user asks |
| repo | string | owner/repo the work is in; omit for work for no repo |
| agent * | string | a name for you, the same on every call, e.g. chat-7f3k2m9q |
{
"name": "take",
"title": "Take work",
"description": "Say you are doing it, and get it. With `id`, that piece of work. With no id, the next thing waiting for `repo`: always a new one, never what you hold. While you hold it no other agent can take it, and whoever sent it sees you are on it. You may hold several; the person watches them. 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.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"agent"
],
"properties": {
"id": {
"type": "string",
"description": "passalong id; leave out for the next thing waiting"
},
"any": {
"type": "boolean",
"description": "work for another repo: only when the user asks"
},
"repo": {
"type": "string",
"description": "owner/repo the work is in; omit for work for no repo"
},
"agent": {
"type": "string",
"pattern": "^[a-z0-9-]{8,64}$",
"description": "a name for you, the same on every call, e.g. chat-7f3k2m9q"
}
},
"additionalProperties": false
},
"outputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {},
"additionalProperties": true
},
"annotations": {
"title": "Take work",
"readOnlyHint": false,
"openWorldHint": false,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| id * | string | |
| note | string | one plain sentence in the first person, as you would tell the person: "Reading the settings page to find where the toggle goes." Start it with BLOCKED: when you are stopped and need an answer |
| agent * | string | a name for you, the same on every call, e.g. chat-7f3k2m9q |
{
"name": "progress",
"title": "Report progress",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"id",
"agent"
],
"properties": {
"id": {
"type": "string"
},
"note": {
"type": "string",
"description": "one plain sentence in the first person, as you would tell the person: \"Reading the settings page to find where the toggle goes.\" Start it with BLOCKED: when you are stopped and need an answer"
},
"agent": {
"type": "string",
"pattern": "^[a-z0-9-]{8,64}$",
"description": "a name for you, the same on every call, e.g. chat-7f3k2m9q"
}
},
"additionalProperties": false
},
"outputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"id"
],
"properties": {
"id": {
"type": "string"
},
"note": {
"type": "string"
},
"lease_until": {
"type": "string"
}
},
"additionalProperties": true
},
"annotations": {
"title": "Report progress",
"readOnlyHint": false,
"openWorldHint": false,
"destructiveHint": false
}
}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 defect) or, for backend work, the one command and the line of its output that shows it works. Send `evidence`: the commands you ran and the lines that decided it, the test summary. The link to the change goes in `pr`, which is how a person sees what changed. A check only a picture can answer goes in `checks`, with the line add_file returned in `ran`: this server has no shell to run a command, and an account of what you saw is refused. DO NOT write new work to carry your evidence: it belongs on this call. What you had to adapt goes in `writeup`; what you learned about the project goes into its documents (save_document).
| Parameter | Type | Description |
|---|---|---|
| id * | string | |
| pr | string | the web link to the pull request, branch or commit with this change, when you pushed one: the person opens it to see what changed |
| note * | string | one plain sentence, in the first person, saying what you did and how it went: "Added the toggle to Settings; it survives a reload." It is the first thing the person reads, and the evidence is behind it |
| risk | string | what this could break, in one line: a shared helper changed, a migration that cannot be undone, a route other clients call. Optional; leave it out when there is nothing specific, rather than writing "low risk" |
| agent * | string | a name for you, the same on every call, e.g. chat-7f3k2m9q |
| checks | array |
Not yours to do, or you are stuck: give it back with the reason. It is open again, and the reason goes to whoever is next: say why, or they start where silence left them.
| Parameter | Type | Description |
|---|---|---|
| id * | string | |
| why * | string | one line: why it is not yours, or where you got stuck |
| agent * | string | a name for you, the same on every call, e.g. chat-7f3k2m9q |
{
"name": "pass",
"title": "Pass it",
"description": "Not yours to do, or you are stuck: give it back with the reason. It is open again, and the reason goes to whoever is next: say why, or they start where silence left them.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"id",
"agent",
"why"
],
"properties": {
"id": {
"type": "string"
},
"why": {
"type": "string",
"description": "one line: why it is not yours, or where you got stuck"
},
"agent": {
"type": "string",
"pattern": "^[a-z0-9-]{8,64}$",
"description": "a name for you, the same on every call, e.g. chat-7f3k2m9q"
}
},
"additionalProperties": false
},
"outputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"id"
],
"properties": {
"id": {
"type": "string"
},
"passed": {
"type": "boolean"
}
},
"additionalProperties": true
},
"annotations": {
"title": "Pass it",
"readOnlyHint": false,
"openWorldHint": false,
"destructiveHint": false
}
}You need the person's answer before you can go on. Ask one clear question, with the context it needs to be answered without opening your conversation. You keep what you hold and nobody else can take it. Then STOP and tell the user you are waiting: do not carry on guessing. When they have replied, call take with this id and their reply comes back with it. Use `pass` instead when the work is not yours. When the answer is a choice between options, offer them as `choices` so the person can pick one with a tap.
| Parameter | Type | Description |
|---|---|---|
| id * | string | |
| agent * | string | a name for you, the same on every call, e.g. chat-7f3k2m9q |
| choices | array | when the answer is a pick between options (two layouts, three fixes): two to four, each with a screenshot when it is something to look at. The person picks one in the hub with a tap; their pick comes back as the reply |
| question * | string | one clear question in the first person, a few sentences at most, plain text: "Should the dark-mode toggle live in Settings or the header? The header is crowded on mobile." What you were about to do, if they just say yes, helps |
{
"name": "ask",
"title": "Ask the person",
"description": "You need the person's answer before you can go on. Ask one clear question, with the context it needs to be answered without opening your conversation. You keep what you hold and nobody else can take it. Then STOP and tell the user you are waiting: do not carry on guessing. When they have replied, call take with this id and their reply comes back with it. Use `pass` instead when the work is not yours. When the answer is a choice between options, offer them as `choices` so the person can pick one with a tap.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"id",
"agent",
"question"
],
"properties": {
"id": {
"type": "string"
},
"agent": {
"type": "string",
"pattern": "^[a-z0-9-]{8,64}$",
"description": "a name for you, the same on every call, e.g. chat-7f3k2m9q"
},
"choices": {
"type": "array",
"items": {
"type": "object",
"required": [
"label"
],
"properties": {
"label": {
"type": "string",
"description": "what this option is, in a few words"
},
"detail": {
"type": "string",
"description": "one line more: what it means or costs"
},
"picture": {
"type": "string",
"description": "a screenshot of it, uploaded with add_file first: the /v1/shots/ link"
}
},
"additionalProperties": false
},
"maxItems": 4,
"minItems": 2,
"description": "when the answer is a pick between options (two layouts, three fixes): two to four, each with a screenshot when it is something to look at. The person picks one in the hub with a tap; their pick comes back as the reply"
},
"question": {
"type": "string",
"description": "one clear question in the first person, a few sentences at most, plain text: \"Should the dark-mode toggle live in Settings or the header? The header is crowded on mobile.\" What you were about to do, if they just say yes, helps"
}
},
"additionalProperties": false
},
"outputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"id"
],
"properties": {
"id": {
"type": "string"
},
"lease_until": {
"type": "string"
}
},
"additionalProperties": true
},
"annotations": {
"title": "Ask the person",
"readOnlyHint": false,
"openWorldHint": false,
"destructiveHint": false
}
}Write down work someone must still do (one piece, or several at once): a plan broken into steps, or every defect a test run turned up, each its own item so each can be taken on its own. Check what is open first (find_work): if this session answers something you hold, hand_in that instead. Each item is Ready at once and reaches whoever it is for; `draft: true` holds them all for a person to read first. Pictures and files the user gave you go in `files`, each item naming its own by position (`files: [0]`); with one item, every file goes to it. A line from add_file goes in `body` instead. Knowledge is not work: what someone needs to know goes into a project's documents.
| Parameter | Type | Description |
|---|---|---|
| to | string | team slug, team/@handle for one teammate, team/@mark,@brian for several, or team/#group for the people who do a thing; default is your team when you are in one |
| draft | boolean | hold it all in Draft for a person to read and make Ready |
| files | array | files the user gave you, filled in by the client; each item names its own |
| items * | array |
{
"name": "create_work",
"title": "Write work down",
"description": "Write down work someone must still do (one piece, or several at once): a plan broken into steps, or every defect a test run turned up, each its own item so each can be taken on its own. Check what is open first (find_work): if this session answers something you hold, hand_in that instead. Each item is Ready at once and reaches whoever it is for; `draft: true` holds them all for a person to read first. Pictures and files the user gave you go in `files`, each item naming its own by position (`files: [0]`); with one item, every file goes to it. A line from add_file goes in `body` instead. Knowledge is not work: what someone needs to know goes into a project's documents.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"items"
],
"properties": {
"to": {
"type": "string",
"description": "team slug, team/@handle for one teammate, team/@mark,@brian for several, or team/#group for the people who do a thing; default is your team when you are in one"
},
"draft": {
"type": "boolean",
"description": "hold it all in Draft for a person to read and make Ready"
},
"files": {
"type": "array",
"items": {
"type": "object",
"required": [
"download_url",
"file_id"
],
"properties": {
"file_id": {
"type": "string",
"description": "the host's id for the file"
},
"file_name": {
"type": "string",
"description": "original filename, used as the label"
},
"mime_type": {
"type": "string",
"description": "image/png, application/pdf, text/csv, …"
},
"download_url": {
"type": "string",
"description": "where the file can be fetched (https)"
}
},
"additionalProperties": false
},
"description": "files the user gave you, filled in by the client; each item names its own"
},
"items": {
"type": "array",
"items": {
"type": "object",
"required": [
"title",
"summary"
],
"properties": {
"to": {
"type": "string",
"description": "who it is for, when not the same as the top-level `to`"
},
"body": {
"type": "string",
"description": "markdown for whoever does it: what is wrong or wanted, what you found, what done looks like if you know: in whatever shape fits"
},
"repo": {
"type": "string",
"description": "owner/repo it is for, when there is one"
},
"tags": {
"type": "array",
"items": {
"type": "string"
},
"description": "words that describe it, e.g. bug, feature, question; nothing turns on one"
},
"after": {
"type": "array",
"items": {
"type": "integer"
},
"description": "positions (from 0) of earlier items this one needs done first"
},
"files": {
"type": "array",
"items": {
"type": "integer",
"minimum": 0
},
"default": [],
"description": "positions in the top-level `files` that belong to this item, from 0"
},
"title": {
"type": "string",
"description": "what it is, in a few words"
},
"parent": {
"type": "string",
"description": "id of the work this comes out of: a bigger piece, a customer request"
},
"summary": {
"type": "string",
"description": "one or two plain sentences for a PERSON, no ids or paths: what this is and whether anybody has to act. 400 characters at most"
}
},
"additionalProperties": false
},
"maxItems": 20,
"minItems": 1
}
},
"additionalProperties": false
},
"outputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"work"
],
"properties": {
"work": {
"type": "array",
"items": {
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"type": "string"
},
"title": {
"type": "string"
}
},
"additionalProperties": true
}
}
},
"additionalProperties": true
},
"annotations": {
"title": "Write work down",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": false
}
}READ work without taking it. With `id`, that piece of work: its markdown, read only; work over 20,000 characters comes back as an outline unless you ask for `section` or `full`. With `query`, the work whose words match. With neither, the board: what needs the user, who is on what, and what is ready: hosts that draw MCP Apps show it as one. To DO the work, call take instead: it is the only way anyone learns somebody picked it up.
| Parameter | Type | Description |
|---|---|---|
| id | string | passalong id, e.g. k3mq2xa7 |
| full | boolean | with id: the whole text, however long |
| query | string | words to look for in titles, tags and text |
| scope | string | with query: "all" (default), "mine", or a team slug |
| section | string | with id: only the part under this heading; see the outline |
{
"name": "find_work",
"title": "Find work",
"description": "READ work without taking it. With `id`, that piece of work: its markdown, read only; work over 20,000 characters comes back as an outline unless you ask for `section` or `full`. With `query`, the work whose words match. With neither, the board: what needs the user, who is on what, and what is ready: hosts that draw MCP Apps show it as one. To DO the work, call take instead: it is the only way anyone learns somebody picked it up.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"id": {
"type": "string",
"description": "passalong id, e.g. k3mq2xa7"
},
"full": {
"type": "boolean",
"description": "with id: the whole text, however long"
},
"query": {
"type": "string",
"description": "words to look for in titles, tags and text"
},
"scope": {
"type": "string",
"description": "with query: \"all\" (default), \"mine\", or a team slug"
},
"section": {
"type": "string",
"description": "with id: only the part under this heading; see the outline"
}
},
"additionalProperties": false
},
"outputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"id": {
"type": "string",
"description": "with id: the work read"
},
"work": {
"type": "array",
"items": {
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"type": "string"
},
"title": {
"type": "string"
}
},
"additionalProperties": true
},
"description": "with query: what matched"
},
"needs": {
"type": "array",
"items": {
"$ref": "#/properties/work/items"
}
},
"ready": {
"type": "array",
"items": {
"$ref": "#/properties/work/items"
}
},
"counts": {
"type": "object",
"properties": {
"done": {
"type": "number"
},
"open": {
"type": "number"
},
"needs": {
"type": "number"
},
"working": {
"type": "number"
}
},
"description": "with nothing: the board",
"additionalProperties": true
},
"working": {
"type": "array",
"items": {
"$ref": "#/properties/work/items"
}
},
"markdown": {
"type": "string",
"description": "with id: its text, or the part asked for"
}
},
"additionalProperties": true
},
"annotations": {
"title": "Find work",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}Change work that exists, when the person asks or when you wrote it. `status`: ready (whoever it is for may take it), draft (held for a person to read), or archived (off the board; it comes back to Draft). `to`: who it is for: @handle, several as @mark,@brian, #group, or "" for the whole team; whoever held it and is left out has it taken back and is told. `markdown`: its whole text, frontmatter first, as find_work gave it: say what changed, keep what did not. `project`: a project id (find_projects) in the work's own space to move it into; it leaves the project it was in, and keeps its id and thread.
| Parameter | Type | Description |
|---|---|---|
| id * | string | |
| to | string | "@handle", "@mark,@brian", "#group", or "" for the team |
| status | string | one of ["ready","draft","archived"] |
| project | string | a project id to move it into |
| markdown | string | the whole document, frontmatter first, to replace its text |
{
"name": "update_work",
"title": "Change work",
"description": "Change work that exists, when the person asks or when you wrote it. `status`: ready (whoever it is for may take it), draft (held for a person to read), or archived (off the board; it comes back to Draft). `to`: who it is for: @handle, several as @mark,@brian, #group, or \"\" for the whole team; whoever held it and is left out has it taken back and is told. `markdown`: its whole text, frontmatter first, as find_work gave it: say what changed, keep what did not. `project`: a project id (find_projects) in the work's own space to move it into; it leaves the project it was in, and keeps its id and thread.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"id"
],
"properties": {
"id": {
"type": "string"
},
"to": {
"type": "string",
"description": "\"@handle\", \"@mark,@brian\", \"#group\", or \"\" for the team"
},
"status": {
"enum": [
"ready",
"draft",
"archived"
],
"type": "string"
},
"project": {
"type": "string",
"description": "a project id to move it into"
},
"markdown": {
"type": "string",
"description": "the whole document, frontmatter first, to replace its text"
}
},
"additionalProperties": false
},
"outputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"id"
],
"properties": {
"id": {
"type": "string"
}
},
"additionalProperties": true
},
"annotations": {
"title": "Change work",
"readOnlyHint": false,
"openWorldHint": false,
"destructiveHint": true
}
}With `id`, one project: its documents, files and the projects inside it. With `query`, the projects whose name, description or any document mentions those words, each naming its matching documents. With neither, every project you can see, briefly: id, title, repos and how much is in it; ask for one by `id` for the rest. Each answer's `space` says where it lives: private, or a named team; `repo` is the repo it is built from, "" when it has none. Read that repo when you write or check its documents.
| Parameter | Type | Description |
|---|---|---|
| id | string | project id |
| query | string | words to look for in projects and their documents |
| scope | string | "all" (default), "mine", or a team slug |
{
"name": "find_projects",
"title": "Find projects",
"description": "With `id`, one project: its documents, files and the projects inside it. With `query`, the projects whose name, description or any document mentions those words, each naming its matching documents. With neither, every project you can see, briefly: id, title, repos and how much is in it; ask for one by `id` for the rest. Each answer's `space` says where it lives: private, or a named team; `repo` is the repo it is built from, \"\" when it has none. Read that repo when you write or check its documents.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"id": {
"type": "string",
"description": "project id"
},
"query": {
"type": "string",
"description": "words to look for in projects and their documents"
},
"scope": {
"type": "string",
"description": "\"all\" (default), \"mine\", or a team slug"
}
},
"additionalProperties": false
},
"outputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {},
"additionalProperties": true
},
"annotations": {
"title": "Find projects",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}With no `id`, make a project, after find_projects shows none fits: a `title` and a short `description`, and its `repo` when it has one, or `repos` when it is built from several (a web app, its API, its mobile app: one product, one project). Leave out `team` for a private one, and pass a team slug only when the person wants it shared; `parent` puts it inside another, in that one's space. With `id`, change its title, description, repo ("" for none), repos (the whole list, the main one first), colour or place (`parent` "" for the top level); its space never changes. The answer's `space` says where it is: tell the person.
| Parameter | Type | Description |
|---|---|---|
| id | string | the project to change; leave out to make one |
| repo | string | the repo it is built from, e.g. github.com/acme/billing; "" for none |
| team | string | new project only: team slug; omit for private |
| color | string | one of ["","coral","amber","green","blue","violet"] |
| repos | array | every repo it is built from, the main one first; replaces the list. Work written in any of them is filed in this project and its agents read this project's README |
| title | string | name of the product or body of work |
| parent | string | project to put it inside; "" for the top level |
| description | string | what it is for, in a line |
One document's Markdown and its `version`, which save_document needs. `history: true` lists its earlier versions, newest first; `version` returns that version's text. To bring one back, save it over the current version.
| Parameter | Type | Description |
|---|---|---|
| history | boolean | list its earlier versions |
| project * | string | project id |
| version | integer | read this earlier version |
| document * | string | document id |
{
"name": "read_document",
"title": "Read a document",
"description": "One document's Markdown and its `version`, which save_document needs. `history: true` lists its earlier versions, newest first; `version` returns that version's text. To bring one back, save it over the current version.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"project",
"document"
],
"properties": {
"history": {
"type": "boolean",
"description": "list its earlier versions"
},
"project": {
"type": "string",
"description": "project id"
},
"version": {
"type": "integer",
"description": "read this earlier version",
"exclusiveMinimum": 0
},
"document": {
"type": "string",
"description": "document id"
}
},
"additionalProperties": false
},
"outputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {},
"additionalProperties": true
},
"annotations": {
"title": "Read a document",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}Write what someone needs to know into a project. With no `document`, a new one: `name` and `body`. With `document`, change it: `body` with the `version` read_document gave you (a newer edit is refused, so nobody's writing is lost) and/or `name` to rename it, and/or `move_to` another project in the same space. Its id and history stay. Update the page that already covers something rather than adding another. A document has no owner and no state and tells nobody: anything someone must still act on is work (create_work). The README is special: an agent taking work in the project is shown its first 4,000 characters. Put there what it must know before changing anything (what this is, the rules not to break, the words used, where things are) and the detail on other pages, named in it. Refer to other pages by their names, not file names.
| Parameter | Type | Description |
|---|---|---|
| body | string | the whole Markdown text |
| name | string | its name: required for a new one, a rename otherwise |
| move_to | string | a project id in the same space to move it into |
| project * | string | project id |
| version | integer | with `body` on an existing document: the version you read |
| document | string | the document to change; leave out for a new one |
{
"name": "save_document",
"title": "Save a document",
"description": "Write what someone needs to know into a project. With no `document`, a new one: `name` and `body`. With `document`, change it: `body` with the `version` read_document gave you (a newer edit is refused, so nobody's writing is lost) and/or `name` to rename it, and/or `move_to` another project in the same space. Its id and history stay. Update the page that already covers something rather than adding another. A document has no owner and no state and tells nobody: anything someone must still act on is work (create_work). The README is special: an agent taking work in the project is shown its first 4,000 characters. Put there what it must know before changing anything (what this is, the rules not to break, the words used, where things are) and the detail on other pages, named in it. Refer to other pages by their names, not file names.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"project"
],
"properties": {
"body": {
"type": "string",
"description": "the whole Markdown text"
},
"name": {
"type": "string",
"description": "its name: required for a new one, a rename otherwise"
},
"move_to": {
"type": "string",
"description": "a project id in the same space to move it into"
},
"project": {
"type": "string",
"description": "project id"
},
"version": {
"type": "integer",
"description": "with `body` on an existing document: the version you read",
"exclusiveMinimum": 0
},
"document": {
"type": "string",
"description": "the document to change; leave out for a new one"
}
},
"additionalProperties": false
},
"outputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {},
"additionalProperties": true
},
"annotations": {
"title": "Save a document",
"readOnlyHint": false,
"openWorldHint": false,
"destructiveHint": false
}
}Delete one document, with its earlier versions. It cannot be brought back, so do it only when the person asked for that document to go; to change what it says, use save_document.
| Parameter | Type | Description |
|---|---|---|
| project * | string | |
| document * | string |
{
"name": "delete_document",
"title": "Delete a document",
"description": "Delete one document, with its earlier versions. It cannot be brought back, so do it only when the person asked for that document to go; to change what it says, use save_document.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"project",
"document"
],
"properties": {
"project": {
"type": "string"
},
"document": {
"type": "string"
}
},
"additionalProperties": false
},
"outputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"removed"
],
"properties": {
"removed": {
"type": "boolean"
}
},
"additionalProperties": true
},
"annotations": {
"title": "Delete a document",
"readOnlyHint": false,
"openWorldHint": false,
"destructiveHint": true
}
}Put a picture or any other file into Passalong and get back the markdown line that points at it. With `file` (a file the user gave you, filled in by the client), it is stored now. Without it, you get a one-time upload link and the curl command that sends the file to it: run that where the file is (a code sandbox, a disk) and its JSON answer has the line. The link works once and expires in 10 minutes; never base64 a file into a tool call instead. If the command cannot reach passalong.dev, the sandbox's network settings block it: tell the user to allow that domain. Accepts image/png, image/jpeg, image/webp, image/gif; other files up to 10MB. WHERE THE LINE GOES DEPENDS ON WHAT THE FILE IS EVIDENCE OF. Proof that work you are handing in holds (a screen that renders right, a total that matches) goes in that check's `ran` on hand_in, and nothing new is written: a check answered with a picture is shown, which is what the hand-in asks for. A picture that is part of the work itself (the screenshot of a bug, a diagram it explains) goes in its text (create_work, or update_work), because work travels as its text and a file beside it does not travel at all. DO NOT WRITE NEW WORK TO CARRY SCREENSHOTS: six images and a caption each is a hand-in. With `project`, the file is kept in that project instead. Pictures (png, jpg, webp, gif) are drawn where they are named; anything else is a file to download.
| Parameter | Type | Description |
|---|---|---|
| file | object | the file the user gave you, filled in by the client |
| kind | string | for an upload link: `image` (the default) for a picture, `file` for a log, PDF, CSV or zip. The link takes only what it was made for |
| name | string | for an upload link: the filename with its extension, which says what it is |
| project | string | keep it in this project instead |
Read a picture or a small text file kept in a project into this conversation. Other files stay downloads in the hub.
| Parameter | Type | Description |
|---|---|---|
| file * | string | file id |
| project * | string |
{
"name": "read_file",
"title": "Read a file",
"description": "Read a picture or a small text file kept in a project into this conversation. Other files stay downloads in the hub.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"project",
"file"
],
"properties": {
"file": {
"type": "string",
"description": "file id"
},
"project": {
"type": "string"
}
},
"additionalProperties": false
},
"outputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"id",
"name",
"type"
],
"properties": {
"id": {
"type": "string"
},
"name": {
"type": "string"
},
"type": {
"type": "string"
}
},
"additionalProperties": true
},
"annotations": {
"title": "Read a file",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}Delete one file from a project. It cannot be brought back, so do it only when the person asked for that file to go.
| Parameter | Type | Description |
|---|---|---|
| file * | string | file id |
| project * | string |
{
"name": "delete_file",
"title": "Delete a file",
"description": "Delete one file from a project. It cannot be brought back, so do it only when the person asked for that file to go.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"project",
"file"
],
"properties": {
"file": {
"type": "string",
"description": "file id"
},
"project": {
"type": "string"
}
},
"additionalProperties": false
},
"outputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"removed"
],
"properties": {
"removed": {
"type": "boolean"
}
},
"additionalProperties": true
},
"annotations": {
"title": "Delete a file",
"readOnlyHint": false,
"openWorldHint": false,
"destructiveHint": true
}
}Passalong keeps a team's work and what it knows, as four things. WORK is something someone must still do (one thing, with no kinds, sections or templates): a title, a summary for a person, and whatever text, pictures and files the next reader needs, in whatever shape fits. Read it and work out what done means; nothing tells you in advance. A PROJECT is a place for one product or body of work; its DOCUMENTS are what to know about it: a README saying what it is, who uses it and how it is built, a page per area, a Log of what changed. FILES are pictures and other files, on work or in a project. DOING WORK. Every call that works on something carries an `agent` name you make up once and reuse on every call. take (with an id, or none for the next thing waiting for `repo`) says you are doing it and returns it; nobody else can take it while you hold it, and whoever sent it sees you are on it. progress, with a one-line note at each milestone; 30 minutes of silence marks it stalled. hand_in when it is done. pass, with the reason, when it is not yours or you are stuck. ask, with a question, when you need the person's answer: you keep it, stop and wait, and take it again once they have replied. Every answer ends with `next`: what to call now. Follow it, and when it says to stop, stop. OPEN WORK YOU MEAN TO DO WITH take, NOT find_work: find_work only reads, and nobody learns you are on it. If take says somebody else has it, tell the user instead of doing the work twice. EVERY HAND-IN CARRIES EVIDENCE: what you ran and what came back, with the command and the lines that decided it, a test summary, a link to the change, or a screenshot url. Collect it as you work rather than writing it from memory at the end. hand_in without it is refused, because your note is your word for your own work and evidence is the part a person can check. WRITING WORK DOWN. create_work takes one piece of work or several. Each says what it is to a person in `summary`: one or two plain sentences, 400 characters at most, no ids, paths or jargon, saying what this is and whether anybody has to act. It is what the person sees first; the text behind it is for agents: exact, dense, full of ids and paths. New work is Ready: it reaches whoever it is for at once. Pass `draft: true` when a person should read it first (a plan of several pieces, or something you are unsure of) and tell them: a draft reaches nobody until they mark it Ready in the hub. A tag such as bug, feature or question may describe it; nothing turns on one. BEFORE WRITING ANYTHING DOWN, CHECK WHAT IS ALREADY OPEN: find_work with nothing shows the board. If this session's work answers something you hold, hand_in that: never write a second piece of work about it. Defects you found and are not fixing go in one create_work call, each its own item, so each can be taken on its own. AN IMAGE THE USER SHOWED YOU IS EVIDENCE, NOT CONTEXT: pass it in create_work's `files`, or add_file it and put the line it returns in the text: a screenshot described instead of attached is the most useful thing in the report, thrown away. If you hold a file rather than a file input (in a code sandbox, or on disk), call add_file with no `file` and run the command it returns; never base64 a file into a tool call. update_work changes work that exists: Ready, Draft or archived, who it is for, or its text. WHAT YOU LEARN GOES INTO THE PROJECT'S DOCUMENTS. When the user asks you to pass this along, hand it off, capture it, or share what was just done, write what the next person needs to know into the project's documents: find_projects, read_document its README and the page for that area, and save_document to update the page that already covers it rather than adding a new one each time, with a line on its Log. Never hand knowledge to one person as a piece of work. "Update the passalong", "add this to passalong" and the like are ambiguous: hand in what you hold, update the documents, or write new work? Ask which, in one line, rather than writi
Names, descriptions and schemas were written by the server and are shown as data.
Pattern matches on what the server declares. They show what it says it can do, not what it does.
None yet. Changes appear after a server's second daily check.
| one entry per thing the work asked for that a picture shows |
| writeup | string | what you had to adapt to make it work here: a version, a name, a step the work did not mention. 500 characters at most. Optional; leave it out when it went as written |
| evidence | string | what you ran and what came back, with the command and the lines that decided it, a test summary, a link to the change, or a screenshot url. "it works" is a claim, not evidence |
{
"name": "hand_in",
"title": "Hand it in",
"description": "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 defect) or, for backend work, the one command and the line of its output that shows it works. Send `evidence`: the commands you ran and the lines that decided it, the test summary. The link to the change goes in `pr`, which is how a person sees what changed. A check only a picture can answer goes in `checks`, with the line add_file returned in `ran`: this server has no shell to run a command, and an account of what you saw is refused. DO NOT write new work to carry your evidence: it belongs on this call. What you had to adapt goes in `writeup`; what you learned about the project goes into its documents (save_document).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"id",
"agent",
"note"
],
"properties": {
"id": {
"type": "string"
},
"pr": {
"type": "string",
"description": "the web link to the pull request, branch or commit with this change, when you pushed one: the person opens it to see what changed"
},
"note": {
"type": "string",
"description": "one plain sentence, in the first person, saying what you did and how it went: \"Added the toggle to Settings; it survives a reload.\" It is the first thing the person reads, and the evidence is behind it"
},
"risk": {
"type": "string",
"description": "what this could break, in one line: a shared helper changed, a migration that cannot be undone, a route other clients call. Optional; leave it out when there is nothing specific, rather than writing \"low risk\""
},
"agent": {
"type": "string",
"pattern": "^[a-z0-9-]{8,64}$",
"description": "a name for you, the same on every call, e.g. chat-7f3k2m9q"
},
"checks": {
"type": "array",
"items": {
"type": "object",
"required": [
"check",
"ran"
],
"properties": {
"ran": {
"$ref": "#/properties/evidence"
},
"says": {
"type": "string",
"description": "what happened, in one plain sentence for a PERSON: \"The badge reads 3 after a reload.\" No file paths or commands: it is the row they read"
},
"check": {
"type": "string",
"description": "what the work asked for that this answers, in its own words, for a PERSON: no file paths, commands or code names. People read this line with a tick beside it; the run behind it is not shown"
}
},
"additionalProperties": false
},
"description": "one entry per thing the work asked for that a picture shows"
},
"writeup": {
"type": "string",
"description": "what you had to adapt to make it work here: a version, a name, a step the work did not mention. 500 characters at most. Optional; leave it out when it went as written"
},
"evidence": {
"type": "string",
"description": "what you ran and what came back, with the command and the lines that decided it, a test summary, a link to the change, or a screenshot url. \"it works\" is a claim, not evidence"
}
},
"additionalProperties": false
},
"outputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"id"
],
"properties": {
"id": {
"type": "string"
},
"state": {
"type": "string"
}
},
"additionalProperties": true
},
"annotations": {
"title": "Hand it in",
"readOnlyHint": false,
"openWorldHint": false,
"destructiveHint": false
}
}{
"name": "save_project",
"title": "Save a project",
"description": "With no `id`, make a project, after find_projects shows none fits: a `title` and a short `description`, and its `repo` when it has one, or `repos` when it is built from several (a web app, its API, its mobile app: one product, one project). Leave out `team` for a private one, and pass a team slug only when the person wants it shared; `parent` puts it inside another, in that one's space. With `id`, change its title, description, repo (\"\" for none), repos (the whole list, the main one first), colour or place (`parent` \"\" for the top level); its space never changes. The answer's `space` says where it is: tell the person.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"id": {
"type": "string",
"description": "the project to change; leave out to make one"
},
"repo": {
"type": "string",
"description": "the repo it is built from, e.g. github.com/acme/billing; \"\" for none"
},
"team": {
"type": "string",
"description": "new project only: team slug; omit for private"
},
"color": {
"enum": [
"",
"coral",
"amber",
"green",
"blue",
"violet"
],
"type": "string"
},
"repos": {
"type": "array",
"items": {
"type": "string"
},
"description": "every repo it is built from, the main one first; replaces the list. Work written in any of them is filed in this project and its agents read this project's README"
},
"title": {
"type": "string",
"description": "name of the product or body of work"
},
"parent": {
"type": "string",
"description": "project to put it inside; \"\" for the top level"
},
"description": {
"type": "string",
"description": "what it is for, in a line"
}
},
"additionalProperties": false
},
"outputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"project"
],
"properties": {
"project": {
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"type": "string"
}
},
"additionalProperties": true
}
},
"additionalProperties": true
},
"annotations": {
"title": "Save a project",
"readOnlyHint": false,
"openWorldHint": false,
"destructiveHint": false
}
}{
"name": "add_file",
"title": "Add a file",
"description": "Put a picture or any other file into Passalong and get back the markdown line that points at it. With `file` (a file the user gave you, filled in by the client), it is stored now. Without it, you get a one-time upload link and the curl command that sends the file to it: run that where the file is (a code sandbox, a disk) and its JSON answer has the line. The link works once and expires in 10 minutes; never base64 a file into a tool call instead. If the command cannot reach passalong.dev, the sandbox's network settings block it: tell the user to allow that domain. Accepts image/png, image/jpeg, image/webp, image/gif; other files up to 10MB. WHERE THE LINE GOES DEPENDS ON WHAT THE FILE IS EVIDENCE OF. Proof that work you are handing in holds (a screen that renders right, a total that matches) goes in that check's `ran` on hand_in, and nothing new is written: a check answered with a picture is shown, which is what the hand-in asks for. A picture that is part of the work itself (the screenshot of a bug, a diagram it explains) goes in its text (create_work, or update_work), because work travels as its text and a file beside it does not travel at all. DO NOT WRITE NEW WORK TO CARRY SCREENSHOTS: six images and a caption each is a hand-in. With `project`, the file is kept in that project instead. Pictures (png, jpg, webp, gif) are drawn where they are named; anything else is a file to download.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"file": {
"type": "object",
"required": [
"download_url",
"file_id"
],
"properties": {
"file_id": {
"type": "string",
"description": "the host's id for the file"
},
"file_name": {
"type": "string",
"description": "original filename, used as the label"
},
"mime_type": {
"type": "string",
"description": "image/png, application/pdf, text/csv, …"
},
"download_url": {
"type": "string",
"description": "where the file can be fetched (https)"
}
},
"description": "the file the user gave you, filled in by the client",
"additionalProperties": false
},
"kind": {
"enum": [
"image",
"file"
],
"type": "string",
"description": "for an upload link: `image` (the default) for a picture, `file` for a log, PDF, CSV or zip. The link takes only what it was made for"
},
"name": {
"type": "string",
"description": "for an upload link: the filename with its extension, which says what it is"
},
"project": {
"type": "string",
"description": "keep it in this project instead"
}
},
"additionalProperties": false
},
"outputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"id": {
"type": "string"
},
"url": {
"type": "string"
},
"command": {
"type": "string",
"description": "the curl command to run where the file is"
},
"markdown": {
"type": "string",
"description": "the line that points at it"
},
"upload_url": {
"type": "string",
"description": "one-time link that takes the file's bytes"
}
},
"additionalProperties": true
},
"annotations": {
"title": "Add a file",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": false
}
}