Quickstart
Start Access, connect one tool, and let an agent do real work against it.
1. Start Access
access serveOpen the address it prints. Chat is the home screen.
2. Connect a tool
Go to Resources → New. Pick Postgres, or the bundled SQLite demo.
Fill in host, database, user, and password. Leave it read-only until you trust the loop.
Access tests the connection and keeps the password. The agent never sees it.
Or just ask Chat:
Connect Postgres.
3. Let an agent do the work
Using my Postgres connection, how many rows are in the largest table?
The agent uses that connection, follows your rules, and shows what it ran. That’s the point — not an answer from memory, work against your stack.
You can also open a docs page with Open in Access — that starts Chat with the first message already filled in.
4. Give an agent a job to own
When the work should keep happening, don’t leave it in a thread:
Make an agent that queries Postgres for failed jobs and posts a Slack summary when they spike.
That’s an agent with a job, not a chatbot you re-brief every morning. See Agents.
If the steps are already known and you want them as code you can inspect and schedule:
Turn that into a daily workflow. Query Postgres and keep the result.
Access writes TypeScript — not a flowchart. See Workflows.
You’re done when
- The connection test succeeded
- An agent did real work against your data
- A job has an owner — a named agent, or a workflow, if it should keep happening