Log in

Agent Workspace

The desktop surface where prepared work, reviews, and Shared Conversations all converge. One place for the team's AI work.

The Agent Workspace is where AI use stops being "open a chat window and start typing" and starts being team work. It's the desktop app that holds the team's Shared Skills, Knowledge Graph, and Shared Conversations — and shows you the work that's already prepared for your call.

The Pattern

Every meaningful piece of work in the workspace follows the same three beats:

1. Prepared, not prompted

A trigger fires — a Slack thread, a new ticket, a calendar event, an inbound email. The agent arrives in your Inbox with a draft already done, sources cited, the right context loaded. You didn't ask. The trigger asked.

This is the inversion of standard AI use. You're not the one prompting; the team's Connectors and Skills prompted on your behalf, before you knew you needed it.

2. Review in one place

Open the item: conversation and the actual work product are right there, side by side. Read the agent's reasoning. Read the draft. Compare the two. Look at the cited sources without leaving the surface.

Then pick: Approve, Edit, or Send back. The owner of the area sets the bar. Nothing ships without that pick.

3. Becomes the team's standard

What worked once gets codified. Promote a successful pattern into a Shared Skill. Promote a draft's reasoning into the Knowledge Graph. The next teammate doing the same kind of work starts where this conversation ended — same connections, same review gates, same audit trail.

Inbox, Outbox, Skills

The workspace surfaces three first-class views in the left rail:

  • Inbox — Items that need your attention. Triggered drafts, hand-offs from teammates, reviews assigned to you.
  • Outbox — Outbound drafts queued under your authority. Emails, comments, doc edits, CRM updates. Nothing sends until you approve.
  • Skills — The team's Shared Skill library. Author, version, test, publish.

A Shared Conversation can move between Inbox and Outbox as it progresses, and can be handed off to another teammate at any point.

Personal vs Shared

The workspace runs in two scopes side by side:

  • Personal — Drafts, scratch conversations, and Skills you're authoring or experimenting with. Only you see them.
  • Shared — Team and org-level Skills, governed Conversations, and tasks routed to you by a Connector or another teammate.

Shared scope writes through Governance. Personal scope doesn't — it's your space to think.

Owner-Direct Writes

When the workspace acts on shared data — sending an email, posting a comment, editing a doc — it never does so without an explicit owner. Each Skill declares who owns its outputs. Drafts assemble under their authority and only ship when they (or their delegate) confirm.

The agent prepares. The owner ships.

How It Connects to Everything Else

The workspace is the surface, but most of its content arrives from elsewhere:

  • From Connectors — Slack, Drive, Confluence, Jira, Notion, Salesforce, HubSpot, Gmail, Loom. External events become Inbox items.
  • From Shared Skills — Versioned, reviewed workflows define how a draft assembles, what review it needs, who owns the output.
  • From the Knowledge Graph — The context Skills pull from at runtime.
  • Into the Output Ledger — Every accepted, edited, or discarded draft becomes a row.
  • Under Governance — Protection rules decide who can publish what, who has to approve, what the audit trail looks like.

When to Use It

The workspace is the right surface when:

  • The work is repetitive enough that a Skill exists (or should)
  • An external event should trigger drafting before a human has to ask
  • The output needs a review trail
  • Multiple people in the org would benefit from the same Skill

It is not the right surface for one-off, free-form chat with a model — that lives in your runtime of choice (Claude, Copilot, ChatGPT) and Headways stays out of the way.