Files
Knowledge is how agents work like someone who’s been here.
Drop in runbooks, skills, and files so an agent doesn’t rediscover your world every morning. Access also learns from the tools you connect — table names, cluster shape, the facts the system can see — and keeps that next to the notes you write.
Open Files in the app. That’s the library agents read from.
What lives here
- Notes and runbooks — how you do things, what “revenue” means, which table to trust
- Skills — a packaged procedure an agent can follow when the task matches
- Workspace files — drafts, exports, and working files an agent can read and write
- Workflow files — what a workflow wrote on a run. Open Files, or open the workflow → Files.
You can also connect a docs folder, a git repo, or a dbt project as a resource. Those are learn-only: agents read them, they don’t change them.
Memory is separate: that’s what Access kept from your chats, not a file you uploaded.
How to use it
Ask Chat:
Index the runbooks folder and use it when triaging outages.
Or add files yourself in Files. Mention a note by name when you want to be specific.
💡 Tip: Instructions on a named agent are house rules that job always follows. Files are the reference library. Skills are the repeatable procedure.
What agents do with it
They search before they guess. A question about refunds should hit the policy you uploaded, not a confident shrug. A workflow can read and write the files you allowed, so the next run can pick up where the last one left off.