1.8.1 Library: So the Agent Can Read Your Files
You have a contract to review, a quote to compare, a report to translate. The files exist — on your laptop, in an email attachment, in a SharePoint folder.
The problem: to the agent, none of them exist.
AOS Work can only work with files it can read. Being readable does not happen by itself — the file has to sit somewhere the agent can reach. That place is Library.
What Library Is
Library is a file-management page embedded in AOS Work and belongs to the App resource type. It manages your PDFs, images, video, and Office documents.
Its value is not that it stores files — any drive does that. Its value is that once a file is there, the agent can read it: cite it, read its content, and write results back.
The one line to keep
Library is not only where you put files; it is where you put files for the agent. That perspective drives everything that follows.
Enabling and Authorizing: Set Up Once, Use Long Term
For adding and authorizing the app, see the demo in AOS Work: Library.
Add Library from 【Explore】 and follow its detail page to authorize it. Library and Base are added separately and share authorization.
Step 1: Open the Apps Category
Open 【Explore】 → 【Apps】 in the left sidebar and find Library.
Step 2: Add Library
Open the Library card, read its details, click 【Add】, and check the 【Enabled】 switch.
Step 3: Complete the authorization as prompted
Follow the detail page to authorize the app. An existing Base authorization can be reused.
Step 4: Confirm the state
Check that the app is added, enabled, and authorized, then open 【Library】 in the left sidebar.
Prepare Files for the Task
| Purpose | Material to prepare |
|---|---|
| Produce content in the team's format | Templates, standard clauses, and brand guidelines |
| Translate, summarize, or rewrite | The source material for the current task |
| Reuse a body of knowledge | Shared reference documents and team guidance |
What Library Contains
- 【My Space】 — your personal file storage
- 【Team Space】 — shared team folders
- 【Recent】 / 【Shared with Me】 / 【Favorites】 — quick return to what you use
- Search and filters — enter keywords and narrow results by file type, configured tags, or metadata
Uploading and Finding
For file operations, see the AOS Studio demos in Upload and Organize and Search and Preview.
Upload: open the target folder in 【My Space】 or 【Team Space】, then click 【Upload】. Upload a batch of files or an entire folder.
Find: enter file-name keywords, then narrow results by file type or configured tag and metadata conditions.
Referencing a Library File in a Task
State the Library file name and folder path in the task. Ask the agent to locate it and check its version before processing. To upload a local copy, use 【Add context】 → 【Add files】.
Three ways to reference, depending on the situation:
Let the agent find it
Describe the file name, folder, or relevant keywords and ask the agent to list matching files first.
State the path
Write the full path, for example "read Library/Legal/standard-clauses.pdf and compare the differences".
List candidates first
When the exact file name is uncertain, have it list the matches and confirm before processing.
To keep a task output in Library, download it from 【Task Outputs】 and follow Upload and Organize to upload it.
Exercise: Find and Read a Specific Version
Add and authorize Library, then prepare two versions of a product brief in the practice folder named Tutorial Files: Product Brief v1.md and Product Brief v2.md. The labels v1 and v2 mean version one and version two; .md identifies a Markdown text file:
| File | File contents |
|---|---|
Product Brief v1.md | Version: 1 Audience: Internal reviewers Deliverables: Draft outline Open question: Scope to confirm |
Product Brief v2.md | Version: 2 Audience: Product team Deliverables: One-page brief and launch checklist Open question: Launch date to confirm |
Open 【New Chat】, enter the request below, select 【Library】 through 【Add context】 → 【Choose apps】, and send:
In the same conversation, enter the follow-up below, select 【Library】 again, and send it to read the full v2 path with its source and key information:
The result lists the source Library/Tutorial Files/Product Brief v2.md, audience Product team, deliverables One-page brief and launch checklist, and open question Launch date to confirm.
When Authorization Lapses or a File Is Missing
| Symptom | Cause | What to do |
|---|---|---|
| The card stays "Unauthorized" | The authorization flow was interrupted | Open Library's detail page in 【Explore】 → 【Apps】 and authorize it again |
| No Library entry in the sidebar | The app is not added, or authorization is incomplete | Check in 【Explore】 that it is added, enabled, and authorized |
| Library opens but a file is missing | Entry authorization and file permissions are separate layers | Ask the resource owner or administrator to confirm your access |
| The page asks for reauthorization | Authorization has expired | Reauthorize from the detail page, return to the task, and check its state; provide a follow-up instruction when needed |
Summary
Library solves whether the agent can see your material. Where a file lives matters less than whether a readable copy is where the agent can reach it.
With material in place, one kind of content fits better elsewhere — the tables you query repeatedly, write back to, and calculate on. The next lesson covers Base.
1.7 Connector: Reach External Systems and Authorize Access
Letting the agent read an inbox or book a meeting requires a channel to the outside system. This lesson covers how that channel is built and which authorization it needs.
1.8.2 Base: Data the Agent Can Query and Write Back
Some content is not a document but data — queried repeatedly, written back to, calculated on. That belongs in Base.