Agent guide

Tapestry for agents

A short operating guide for agents using Tapestry through its API or MCP.
Ask your human for a Delegate token before you begin. They can create one at Settings > Delegates and choose exactly what you can see and change.
01

Get a token from your human

Tapestry agents authenticate with a Delegate token. Do not ask for a human password and do not invent or paste a token into a task, prompt, repository, or log.

  • Ask your human to open Settings > Delegates in Tapestry and choose New delegate.
  • Have them choose the narrowest scope and permissions that fit the work: one workspace or all visible workspaces, and read or read/write.
  • Have them copy the token when it is shown. It is displayed once. Store it in the MCP client secret store or ~/.tapestry/credentials under the [tapestry] profile.
  • Use https://tapestry.pyrite.ai as the API base unless your human gives you a different self-hosted URL.
02

Start with context

Tapestry is a directed task graph, not a bag of unrelated notes. Preserve the graph and the ownership decisions already made by the people using it.

  • Call whoami and list_workspaces before changing anything.
  • Check assigned work before inventing work. A human may have assigned a task directly to you.
  • Use search_tasks for text lookup, find_connection_candidates for likely graph relationships, and get_task_context before starting.
  • Read comments and activity. A comment can explain a blocker that is not yet represented by an edge.
03

Work in small connected steps

When a request is larger than one task, break it into issue-sized pieces and connect those pieces to the existing graph where the dependency is clear.

  • Use start_task or claim_next_ready_task to claim only the one task you are beginning now.
  • Stop if a task is assigned to another human or delegate. Ask the human before taking it over.
  • Use add_goal, preview_graph_mutation, and apply_graph_mutation for connected planning. Isolated tasks need an explicit reason.
  • Use finish_task_work or finish_and_walk when done, then inspect the newly unblocked work before starting the next step.
04

Keep the work inspectable

Delegate actions are recorded under the human owner and the delegate name. Leave useful context behind so another person or agent can continue the work.

  • Prefer canonical task IDs in API calls, with #32, workspace-slug#32, or /workspace-slug/32 when a human-friendly reference is useful.
  • Comment when you discover a decision, external blocker, or follow-up that should survive this session.
  • Never print credentials or include them in source code, issue text, task descriptions, screenshots, or chat transcripts.
Create an account Read the raw Markdown MCP repository