Delegates

A Delegate is an identity for an agent, script, or integration. It can only see and change what you allow, and its name stays attached to its activity.

For a chat app, connect through MCP with your existing Tapestry sign-in. Tapestry creates the connection’s Delegate automatically; you do not need to generate or copy a key. Manual keys are for scripts and integrations that use the API directly.

Make a separate Delegate for each thing you connect. That keeps its activity recognizable, and lets you turn off one integration without interrupting the others.

Creating a manual Delegate

Go to Settings → Delegates and click New delegate.

Tapestry will ask you to choose a scope and an access level. Review both, then click Generate key. Copy the key before closing the setup window: it is only shown once.

Treat the key like a password. Put it in the agent or integration’s secret store, not in a task, comment, prompt, screenshot, or repository. If you lose it, revoke the Delegate and make a new one.

Tapestry gives each new Delegate a generated name. You can rename it later; short names such as research or triage make assignments and activity easier to read. Delegate names cannot contain spaces.

Choosing a scope

Scope	What the Delegate can see
One workspace	Only the workspace you choose.
All visible	Every workspace you can access.

Use One workspace unless the work genuinely crosses workspace boundaries. Free-plan Delegates must use this scope.

Choosing an access level

Access	What the Delegate can do
Read only	Inspect the workspaces, tasks, comments, and activity in its scope.
Read/write	Create and edit tasks; complete, comment on, assign, date, link, and archive them through the API.
Allow delete and heal	Also delete tasks and reconnect the graph around them. This is a separate switch and is off by default.

Even a read/write Delegate cannot manage your account or workspace settings. If a Delegate needs a different scope or access level later, revoke it and create a replacement.

Hosted MCP never grants deletion and does not expose comment posting or account/workspace administration. Archiving and unarchiving use ordinary write access; graph healing still requires editing permission on the affected tasks.

Assigning work

Delegates appear in the assignee picker alongside people. Assign a task to a Delegate when you want the agent to find that work, rather than guessing what it should do next.

The Assigned to Delegates page shows all work assigned to your Delegates. You can keep one combined list or split it by Delegate. Edits, comments, assignments, and completions are recorded with the Delegate’s name, so you can tell what the agent changed.

Pausing and revoking

Use Pause when you want a Delegate to stop temporarily. Its key will stop working until you resume it.

Use Revoke when the integration is finished, the key may have leaked, or you no longer trust it. Revocation takes effect immediately and cannot be undone. You can always create a new Delegate afterwards.

For chat-app setup and everyday prompts, see Tapestry in your chat app. For instructions you can hand directly to an agent, see the agent operating guide.