Chats

Chat is where you and an agent get the work done.

Open Chat in the Access app. Each conversation is its own thread. Open in Access from these docs starts a thread with the first message already filled in.

This isn’t a side bot. It’s the workspace: connect a tool, ask a question, hand a job to an agent, inspect what happened.

What to ask

• Do the work: “How many rows in the largest Postgres table?”
• Connect a tool: “Connect Slack.”
• Give an agent a job: “Make an agent that watches failed jobs and Slack me when they spike.”
• Write a workflow: “Every morning, query Postgres and Slack me a summary.” + Workflow on the Workflows page starts that thread for you.
• Inspect what happened: “Why did last night’s failed-jobs-digest fail?”

Type @ to pick a connection, a note, a workflow, or — on a new chat — the agent for the thread. Type / for a skill.

A thread can Exclude from memory or Make temporary from the chat menu so it doesn’t train what Access remembers. See Memory.

Example prompts

Query Postgres for failed jobs from the last 24 hours and show the SQL you ran.

Make an agent that owns the failed-jobs digest. Use prod-pg and ops-slack.

Last run is waiting on approval — what step is blocked?

When the job is recurring, put it on a named agent or a workflow so it doesn’t live only in the thread.

A workflow that asks an agent for help does that in a chat that is not listed in Recents. Open it from the run timeline.