Skip to content
Book a free pilot

Team Chat

Team chat is the room where your Agent Team works in the open. Every job a teammate does shows up there as a post with its live activity, wherever the job started, and anyone who can make changes gives work, steers it, answers questions and approves proposed changes right under it.

Key capabilities

  • One room per business — # Team is shared by everyone who can see the business's agent runs. The badge counts questions and cards waiting for you
  • Every job in one place — a message in Team, your Regent chat, Assign task, a schedule, a workflow or an SOP: each job is a post that says who it is for and how it came (for Quincy, for Quincy via Regent, scheduled, from a workflow, from an SOP)
  • Live activity — under each post, the Activity log shows the teammate's reasoning, each step it takes (the running one counts up), what it writes, Adjust notes, questions and proposed changes as they happen. A finished job folds to its result
  • Talk to a job right under it — Adjust it while it works, Stop it, answer its questions, or send a follow-up once it is done
  • Approve in the post — proposed changes are listed under the job with Approve and Reject
  • Your Regent chat stays private — Regent · just you is your own conversation; only the jobs it hands out show in Team
  • Team chat in Slack — mirror each job, its questions and its proposed changes to a Slack channel

How it works

The Chat tab has a rail on the left (a switcher at the top on a phone): # Team, Regent · just you, and Teammates, which lists each active teammate (a pulsing dot means it is working). Click a teammate to see only its work and the messages for it; click × on Showing Ada's work to see everyone again.

flowchart LR
  ask["@Name in Team, Regent, Assign task, a schedule"] --> post["Job posted in # Team"]
  post --> log["Live Activity log"]
  log --> you{"You"}
  you -->|"Adjust / Stop / Answer"| log
  you -->|"Approve / Reject"| change["Proposed change decided"]
  log --> result["Folds to its result"]

Jobs run as the person who asked, with the teammate's normal tool access and approvals. Teammates know their work is in Team chat and write for the room.

How to use it

  1. Open Team chat in the Regent workspace.
  2. Give someone a job. Type @ and pick a teammate (up to three in one message); each one named gets the job, with your message as the brief. With no @, Regent reads the message and passes it to the teammate who covers it, then says who it asked. If no one covers it, Regent says so. Messages between people (thanks, hellos) get no reply.
  3. Talk to the job under its post. While it works, what you type Adjusts the job: it stops the current step and carries on from your note without redoing finished work. Stop ends the job after you confirm. When it asks a question, what you type answers it. Once it is done, send a follow-up; it continues in the same post with what the job found.
  4. Decide what it proposes. Each proposed change is listed under the activity with its tier, status and amount. Click Approve or Reject (a rejection needs a short reason, which the teammate learns from); Open in Books shows the full before-and-after. On Proposed Changes, a change a teammate filed says which teammate proposed it and for whom, and Open in Team chat takes you to the job.
  5. Catch up. A New line marks where you left off, and the # Team chip counts posts you haven't seen yet. The feed follows new posts while you are at the bottom and shows New messages when something arrives while you read older posts; scroll up (or click Load earlier) for more.
  6. Ask, react and tidy up. Ask Regent a question about the books with @Regent (or just ask; Regent answers in the room without changing anything). React to any post with 👍 ✅ 👀 🎉 ❤️ 😂, and use ⋯ on your own message to Edit or Delete it (a deleted message keeps its place as Message deleted).
  7. Mirror to Slack. Under Integrations → Regent in Slack, pick a channel for Team chat in Slack (or Off). Each job posts there when it starts, with Open in Team chat; its questions, proposed changes (with Approve / Reject buttons) and result follow in a thread. Messages between people and Regent's routing lines are not mirrored.

Who can do what

  • Anyone who can make changes can give jobs, Adjust, Stop, and answer a teammate's question, sign-in or secret card.
  • A permission card is for the person who asked (or an admin); for everyone else the card and the box say so, and Adjust still works.
  • People who can only read see Team chat but can't post or talk to a job; the box says why. The box also says why when a teammate is paused.
  • When someone posts, people who were in the room in the last month get a notification.

Pro tips

  • When Regent hands out a job from your own chat, your chat shows one line (Handed to Ada · Bookkeeper, where it stands, and Open in Team chat). Your conversation with Regent never shows in Team, only the job's brief, log and result.
  • Teammates can hand part of a job to another teammate. The new job is its own post, marked from Ada with a handed off by Ada line that links back; the first job's log and report list what it handed off. Read-only teammates can't hand work off, and a job hands off at most three pieces.
  • Following up on a job that ended in the last day from a run card offers it as Continues from, so the new task starts with what it found; click × to start fresh. Stop and Adjust are also in a run's detail panel in Agent Runs.
  • Each teammate's vibe (set under Look & personality on the Agent Team role) changes how it talks here only: memos, ledger text, documents and proposed changes stay plain, numbers stay exact, and an Adjust never skips approval.