How to give an agent read or write access to your library

An agent is only as useful as what it can see. Give it access to the right parts of your library, and it can search, read, and — if you allow it — edit your artifacts as it works. Here's how to grant that access, from either side.

one-chat.app — it builds things
Turn that into a budget I can play with.
Done — live budget on the right. Drag any number.
Japan · Aprillive
Flights$1,840
Hotels$1,310
Food + fun$900
Total $4,050 · under budget 

Option A: from the library

1. Open /app/library and find the artifact or folder you want to share.
2. Open its Manage access controls.
3. Pick the agent to grant access to.
4. Choose the permission level: read lets the agent search and reference the content; read-write lets it edit the artifact directly, the same way you would.
5. If you're granting a folder, remember the access cascades — the agent gets everything inside it, including subfolders, without you granting each item individually.

Option B: from the agent

1. Open the agent's workspace page and go to its Config tab.
2. Find the section for granted artifacts and folders.
3. Add the artifact or folder you want it to have access to.
4. Set read or read-write the same way — and again, granting a folder here cascades to everything nested inside it.

Both routes end at the same grant — use whichever is closer at hand. Sharing from the library is faster when you're already looking at the artifact you want to hand over; sharing from Config is faster when you're setting an agent up and want to see everything it has access to in one place.

Read vs. read-write — which to choose

Default to read for anything the agent should reference but not change — source material, records, anything you want to stay exactly as you left it. Reserve read-write for artifacts you actually want the agent maintaining on your behalf — a tracker it updates, a doc it keeps current. Because every edit creates a new version, a read-write grant doesn't put the original at risk — you can always see what changed.

Folders scale better than files

If you're granting access to more than a couple of artifacts, put them in a folder first and grant the folder instead of each file. New artifacts you drop into that folder later inherit the same access automatically — you won't need to remember to re-grant anything as the folder grows.

That's the whole mechanism: one grant, a permission level, and a cascade that keeps working as your library does.