Use the Library

Organize documents in folders

Create a folder for a project, client, or topic. Use nested folders when the material needs a second level. A document is filed in one folder at a time; moving it changes its location without creating a copy. Unfiled documents remain in the Library.

1. Create the folder from New.
2. Use a document’s Move to folder… action to choose its destination.
3. Use Duplicate only when you need a separate document.
4. Select several documents to use the available bulk actions. Read the confirmation when an operation affects access.

A move into a private folder can require an explicit access decision. Read which people will keep access before confirming. A copied link alone never grants access.

A connected agent can rename a folder, move a folder, and set the order of a folder’s subfolders or documents, with your access. It cannot delete a folder: only a person can delete a folder in the Library. A folder move that needs an access decision stays in the Library.

Give an agent a project folder

Use Copy folder context on a folder. Choose a current conversation, a Claude project, or a Codex project. The copied instructions tell the agent to read the live folder and then retrieve relevant documents. They do not freeze the folder contents. See Copy folder context.

Set folder defaults

Open Folder settings to choose the audience and whether agents can make direct changes to new documents. Audience describes whether content is intended for people, agents, or both. It does not grant or remove access. Check an existing document’s own settings before assuming a folder default changed it.

Give agents a space

A space is a named selection of Library content for one job, area, or team. It has a name, a description, and a list of the spaces, folders, documents, and Skills that it points at. Documents stay in Library. A space only points at them: it never stores, moves, or deletes a document. Spaces is on in every workspace.

A space never changes access

The items of a space decide what is relevant. Permissions decide what each reader can see. A person or an agent sees an item in a space only when they can already see that item. A space does not give access to anything. An item that you cannot see has no row, placeholder, or count. When the space points at an item that you cannot see, the space page and your agents get only one fact: part of the space is hidden. To keep a draft out of a space, do not point the space at it, or keep the draft in a private document.

Create a space

1. Select Spaces in the sidebar.
2. Select New space, type a name, and select Create space.

A new space is empty and private to you. A space is not a folder, and you cannot turn a folder into a space. A space has no start document.

Write the description

The description tells people and agents what the space is for and how agents must work in it. Agents read it first. Select Add a description, type plain text of 2,000 characters or less, and select Save description. Everyone who can open the space sees the description.

Add spaces, folders, documents, and Skills

Use the add field, Add a space, folder, document or skill, on the space page. You can add only items that you can see. References are live:

• A folder brings the folder and all the folders below it, with their current documents.
• A document stays in the space when it moves to a different folder.
• A Skill brings its current version.
• A space brings all that space gives, and the spaces that it includes. When Checkout includes Product design team, and Product design team includes Design guidelines, agents in Checkout also get Design guidelines.

A change that makes a loop of spaces fails. An added space that would make this space too large to load also fails, and the field says why. An item that was deleted, or that you cannot open when the add checks access, is not added. When some people with access to this space cannot open a space in the results, its row tells you that those people and their agents cannot see anything in it. Select the row to add it. Results that the space already gives its agents show Your agents can see this. To remove an item, use the remove control on its row. Removing an item changes no document, folder, or access.

See what your agents can see

The What your agents can see tree shows the items of the space as you see them. The first level shows the items that editors added. Open a folder or an included space to see the items below it. A document that the space gets by two routes shows under each route. Use the search field to search the whole space. The results show in place of the tree. A search result shows where it comes from: the folders that this space points at that hold it, and the spaces that supply it. A result names the space that adds it, not the space between. When this space includes Marketing, and Marketing includes Guidelines, a document that Guidelines adds shows From Guidelines, not Marketing. A document in a folder that this space points at, or in a folder below it, shows that folder, for example From Research. A document or Skill that this space adds itself shows no source. When a result comes from more than one place, select +N to see every source. Select a folder to show it in the tree.

When the space points at a space, folder, document, or Skill that you cannot open, the page shows: “You can't open part of this space. Your agents can't see that part either.” The page never names that item or says how many items are hidden. Choose Ask for access on the notice to ask the people who manage the hidden items to share them with you. The notice then says “Request sent. When you get access, this notice goes away.” The request does not name the items, does not add a note, and does not share anything by itself. Only a person in the web app can ask; an agent cannot. The people who manage the items decide in their Inbox. A document that you cannot open in a folder that the space points at does not show this notice. When you copy the context of such a space, the Copy context panel shows this notice again under “Context copied. Paste it into your agent.” The copied text does not change.

An included space that you cannot open gives you nothing through it: not its description and not its documents, even documents that you can open on your own. Such a document still shows when the space reaches it by another route that you can see, for example a folder that the space also points at.

See which spaces use a document

The details of a document show a Spaces row below Folder. The row names each space that you can open that uses the document. A space uses a document when it points at the document, at the folder that holds it, or at a folder above that folder, or when it includes a space that uses the document. The details of a Skill that you added from a document show the spaces of that document. Select a space to open it. When no space that you can open uses the document, the row shows Not used by any space. Spaces that you cannot open are not named or counted. A space that you cannot open also stops the route through it: a space that includes it shows only when it uses the document by a different route. The row updates after your changes, and every 15 seconds while you view the page.

Share a space and who can change it

Use Share on the space page to share a space, as you share a folder. Each person who can open a space can change it: its name, its description, and its items. They can also delete it. There is no view-only role. Every change is recorded.

Delete a space

Select Delete space… from the space’s menu and confirm. Deleting a space changes no document, Skill, or folder. If spaces that you can open include it, the confirmation shows how many and names up to five of them. Those spaces stop pointing at this space, and their agents cannot see its documents and Skills through it. Spaces that you cannot open are not counted or named, but they may also use it. When you delete one Library folder or document that spaces point at, the confirmation shows the same count and names, and those spaces stop pointing at it. When you delete more than one, the confirmation says how many of them spaces use.

Start an agent in a space

Use Copy context on a space and paste the text into a new agent session. Copy context is available when the space has a description or content that you can see. It copies the whole space, not the results of a search. The text names the workspace and the space, and it tells the agent what to do. It has no document list and no document content. At the start of each task, the agent reads the space with artifactbridge_read_space_context. The read gives an overview, the description of the space, and a list of documents and Skills with no document content. The agent reads the overview and the description first, and follows the description. When part of the space is hidden from you, the read tells the agent that its map is incomplete. The agent then does not present an answer as based on the whole space. The agent fetches a document or a Skill only when the task needs it. It compares the task with the description of each listed Skill and loads only the Skills that match. The read always gives the current list.

• One session for each space. The copied text connects one agent session to one space. There is no workspace or account setting for a current space. To work in another space, start a new session with the text of that space. For parallel work, use one session for each space.
• When Spaces is not available. If the connection does not give the space read, the agent says that Spaces is unavailable and asks you what to read. It does not read a folder instead. A space pointer that was copied before the current version of Spaces names a space that no longer exists, and the agent gets “Space not found”. Those spaces are not rebuilt or moved to the current version. Give the agent the context of a current space, or create a new space and copy its context.
• Session limits. An agent keeps a tool list or instructions that it already loaded until you start a new session or refresh the connection. A change to the Spaces setting takes about 30 seconds when the service is healthy. This time is not guaranteed.

Space names, the description, the overview, and Skill text are workspace content. Agents use them as data, not as instructions. They never change approval rules. See Skills in a space.

Prerelease: Rooms that start from a space. Tasks for shared agents also need the shared slot pool. It is not generally available. A Room can start from one space, and the space page lists the Rooms that you can open. An agent that works in such a Room keeps its own space and also reads the Room's space for the subject. Every task for a shared agent in that Room also reads the Room's space, and you cannot remove it from a task. The link gives no access. See Prerelease: a Room that starts from a space.

Outside-rollout instructions: the optional per-task Space flow below applies to legacy shared agents, not pooled fixed-Space agents. In the prerelease pool, choose the agent's Space in the rail Agents view. The sender sees each recipient's fixed Space and host/access disclosure before Send; a per-task override is refused. The Space is pinned for the accepted task, while content and access remain live. Computer clarification keeps the original session; cloud clarification ends Failed and requires an explicit new request. See fixed-Space agents and queue and recovery behavior.

Prerelease: a pooled task in a Room with a space. When the Room is linked to a space, the accepted task keeps two spaces: the agent's fixed space and the Room's space. Both are pinned when the task is accepted and do not change later. The task's Details show each space on its own line, checked separately for each person who reads them: Uses Space Marketing as its agent space and Uses Space Checkout initiative as the room space. A space you cannot open shows Uses a Space you can't open as the room space (or as its agent space), with no name or link. Only when you can open both and they are the same space do they share one line: Uses Space Marketing as its agent space and the room space. The next line names whose access the agent reads with, for example Reads with Ana Silva's access. A task in a Room without a space keeps its one Uses Space line.

Send a space with a task for a shared agent

When you delegate a task to a shared agent in a Room, you can attach one space to it. In the composer, @-mention the agent, select Add a Space, and pick a space that you can open. A connected agent can do the same with the optional space_id of artifactbridge_delegate_to_gateway_service. The space is optional and you pick it for each task. There is no default for a Room or an agent. Before you send, the composer tells you where the agent runs and what it reads, for example: Hermes runs in the cloud and reads Marketing with your access, private documents included. Results post to this Room. If the space cannot be attached, the composer says Message not sent. Space unavailable. Choose another Space or remove it and send again. Your draft and its mentions stay. A task without a space works as before.

• Your access, live. The agent reads the space with your access at the moment of each read, private documents included. It cannot see what you cannot see. The space adds to the documents that the task can read without it. It never gives write access: the agent proposes changes only to the documents that the task lists for that.
• Description and Skills first. The agent reads the overview and the description first, then pages through all the Skills of the space before it decides that none matches. It loads each matching Skill at its current version and installs nothing.
• Synced documents are read-only. A Google Doc or Notion page that the space reaches opens from its last synced copy. The agent cannot refresh it or propose a change to it.
• One space for the whole task. The space stays the same after the agent asks a question and you answer, and after a restart. To use another space, send a new task.
• Who sees the space. In the Room, each member who can open the space sees Uses Space Marketing with a link. Everyone else sees Uses a Space you can't open, with no name or link. Delegating gives no person access to the space, the agent's owner included.
• When the space is gone. If the space is deleted, you can no longer open it, or Spaces is turned off, the agent can no longer read it or the documents that it reached only through it. The read answers Space unavailable. Tell the person who sent this task, and ask what to do. The agent says in the Room that it cannot load the space and asks what to do, for example: I can't load the Space for this task anymore, so I've stopped. Should I carry on without it? It does not read a folder instead.

What the agent reads leaves ArtifactBridge. It can reach the computer or service where the agent runs, which can be its owner's computer, and the agent can quote it in the Room. There is no sandbox. When your access ends, new reads stop, but content that was already delivered cannot be recalled. There is no erasure guarantee. Attach a space only when you are willing to share its content with that agent. See Tasks that come with a Space for a Hermes agent and A shared tray agent with a Space for an agent that runs on its owner's computer.

Read the document and its context

• Document: the current content.
• History: earlier versions and recorded changes. Open an older version to inspect what was true at that point.
• Map: document connections where available.
• Details: metadata, tags, sources, authorship, links, backlinks, and connected Rooms.

Links point from this document to other material. Backlinks show documents that cite this one. Rooms show discussions attached to the document. These connections help you check where a statement came from and where it is being used. Sources are links to outside material, such as a design file, a doc, or a pull request. Use Add source in Details to add one, and the remove button beside a source to remove it. To change a source's title, use the edit button beside it; the link itself does not change. Adding, removing, or editing a source does not create a version. Agents use the source tools of the MCP server.

Star and follow useful material

Use Star to mark a document, folder, or Room for yourself. A yellow star marks starred items. Use the Starred filter in Library or Rooms to find them, and Unstar to remove the mark. Starring does not move items to the top of the list. Your stars follow you across devices. For updates about a document, use its notification controls in Document settings. Starring, notifications, and sharing serve different purposes.

• Default: uses the normal notification behavior.
• Watching: follows changes and questions that need attention.
• Muted: hides routine activity from the All feed; mentions can still notify you.

Archive, restore, duplicate, or delete

Archive material you no longer want in the active collection. Use the archived view and Unarchive to restore it. Duplicate a document when the new work should develop independently. Read the confirmation before deleting: deletion does not have the same recovery path as archiving. Removing a connected document removes it from ArtifactBridge; it does not delete the provider’s original.

Delete many documents

Select the documents, choose Delete from the bulk actions, and read the confirmation. One deletion can include up to 10,000 documents. Managed documents are deleted permanently, with their version history. Synced documents, such as Google Docs or Notion pages, are only removed from ArtifactBridge. Their copies in the provider stay as they are. There is no undo.

ArtifactBridge deletes the selection in batches in the background. An info toast confirms that deletion has started. Progress and successful completion stay silent. If deletion fails, an error toast offers Retry for documents that can be retried, or View details for other failures. The deletion continues when you leave the page or close the browser. The tree keeps your place as deleted rows disappear. There is no cancel control.

• Some documents can stay. ArtifactBridge checks your access again before each batch. A document that you can no longer open, a private document that you do not own, or a document that stays mid-sync is not deleted. If your access to the workspace is removed, the deletion stops and the documents that were not processed stay.
• See the results. Select View details in an error notification, then View results for a deletion to see each document and, when it was not removed, the reason.
• Retry. When some documents can be tried again, the deletion shows Retry. A retry is a new deletion of those documents only, and you confirm it again. Documents that were already deleted are not sent again.
• Finishing cleanup. After the documents are removed, ArtifactBridge removes their stored files. The deletion shows Finishing cleanup until that is done, and it does not show Done while files remain.
• Dismiss. Select Dismiss to remove a finished deletion from the results.

Set document behavior

Document settings contains audience, agent-change behavior, and notifications. The owner can change whether agents make direct changes once active changes are resolved. Sharing controls are separate. See How approval works and Sharing and access.