1.8.2 Base: Data the Agent Can Query and Write Back
The previous lesson put files in Library. But work also holds a second kind of content: inventory tables, order records, customer lists, sales detail.
Those can live as Excel files in Library too. But then the agent can only read them, not act on them — adding a record, changing a status, filtering ten rows to a condition all need a different carrier.
Base is built for that kind of content.
What Base Is
Base is a structured-data page embedded in AOS Work and belongs to the App resource type. It manages tables, records, and fields, and the agent can both query it and write back to it.
The test
Does this content need to be queried, filtered, and written back? Then Base. If it only needs to be read, Library is enough.
How It Divides the Job With a Spreadsheet
| Dimension | Spreadsheet file (in Library) | Base |
|---|---|---|
| What the agent can do | Read the content | Query, filter, write, update |
| Multi-person work | Depends on file versions | One dataset, several people at once |
| Presentation | A single sheet | Table, Assets, Gallery, and Kanban views |
| Permissions | File level | Role level |
They are not substitutes: a one-off analysis is more direct in a file; data that is maintained, queried, and written over time belongs in Base.
Two Ways to Use It
Query: one sentence instead of scrolling a sheet
The agent queries the table, returns the result, and embeds a live preview in the conversation. That preview is read-only; open Base from the sidebar for the full page.
Write: land the result in the table
The reason a flow like "read the email → extract fields → write to a table" can run end to end is that Base accepts writes.
Enabling It: The Same Flow as Library
For adding and authorizing the app, see AOS Work: Base. To prepare an exercise table and check written records, see the AOS Studio demos in Tables and Records.
Base and Library are both embedded Apps, so the path is identical:
- Open 【Explore】 → 【Apps】.
- Find Base, click 【Add】, and enable it.
- Follow the authorization prompt; an existing Library authorization can be reused.
The apps are added separately and share authorization. Once complete, a Base entry appears in the left sidebar.
Exercise: Query, Update and Read Back
After adding and authorizing Base, prepare a Base named Tutorial Inventory and create its Products table. Add SKU (text, product code), Stock (number, inventory quantity), and Status (text, handling status). Enter the three records below. Open means not yet handled; the later Reorder status means replenishment is needed:
| SKU | Stock | Status |
|---|---|---|
| DEMO-101 | 120 | Open |
| DEMO-102 | 260 | Open |
| DEMO-103 | 80 | Open |
Open 【New Chat】, enter the request below, select 【Base】 through 【Add context】 → 【Choose apps】, and send:
Only DEMO-101 and DEMO-103 should match. In the same conversation, enter the follow-up below, select 【Base】 again, and send it to update their status by SKU:
Then enter the follow-up below, select 【Base】, and send it to read every record again:
Acceptance: there are still 3 records. DEMO-101 and DEMO-103 have Status set to Reorder; DEMO-102 remains Open. Stock stays at 120, 260, and 80 respectively. You can also open Base from the sidebar and compare the saved values in Products.
Permission Roles
| Role | What it can do |
|---|---|
| Owner | Full control, including permission settings |
| Admin | Read, edit, and manage the data in Base |
| Reader | Read-only access |
Permissions are assigned by role, so the same data can be shared with a team for reading or collaborative editing while the boundary stays clear.
When Base, When Library
| Scenario | Library | Base |
|---|---|---|
| Read a contract and compare versions | Yes | — |
| Read a PDF and translate it | Yes | — |
| Extract fields from email into a table | — | Yes |
| Count stock and find slow-moving SKUs | — | Yes |
In one line: Library handles reading; Base handles querying and writing. They usually work together — files in Library, the structured result in Base.
Summary
Base makes data something you can act on, not just look at.
That completes the four resource types. The next lesson returns to the two context mechanisms: Memory and the workspace.
1.8.1 Library: So the Agent Can Read Your Files
Your files sit on your laptop, in your inbox, in SharePoint — and the agent can see none of them. Library fixes that.
1.9 Memory and the Workspace: Two Kinds of Continuity
Resources decide what the agent can do. Two mechanisms decide what it remembers: Memory remembers you, the workspace remembers the work.