Quick reference
A short map of the workspace. For the full story, start with Introduction.
The workspace
| Piece | One line |
|---|---|
| Agent | A teammate with a job. Default Access agent, or a named one you save. |
| Resource | A named connection. Access keeps the password. Every agent uses it. |
| Files | Notes, skills, and a workspace so agents don’t start from zero. |
| Memory | Facts Access kept from chats — yours in Settings, or a named agent’s. |
| Workflow | Recurring work as code — not a flowchart. Schedule, Chat, or Run. |
| Chat | Where you and an agent get the work done. |
| Your agents | Cursor, Claude, or anything that speaks MCP — one server, your whole stack. |
How to start Access
access serveThat opens the workspace. Chat, Agents, Resources, Files, Workflows, and Settings (Connect, Memory, Runs) are all there.
To point Cursor or Claude at Access without opening the app:
access mcpaccess --helpHow a workflow run can look
Queued → running → completed, failed, cancelled, timed out, or Waiting on approval.
Waiting on approval means a connection step needs you. Approve or deny that step, then continue. Finished steps are reused so they don’t run twice.
Workflows start on a schedule you set, with Run, or from Chat. No webhook start yet.
Defaults worth keeping
- Read-only connections until a write is the job
- Give recurring work an owner — a named agent, or a workflow
- List every connection a workflow may use — Access does not guess from the rest of the file
- Prefer a new version over editing history
- Exclude a chat from memory when it shouldn’t train what Access remembers