Skip to main content
A cowork agent picks up the work a team does by hand across its tools. Something lands in chat, and someone opens three other apps to act on it. They copy names, fill in a template, update a tracker and tell the team where everything is. The agent does the same, from the same message. Cowork is reads and writes over scattered context, chat, documents, spreadsheets and a project tool, and that is the work Mirage is built for. The agent reaches all of it from one terminal, with fewer tokens than calling the same services as MCP tools (VFS-Bench 1.0). Its scope is known up front, a few things to read and a few changes to make, which is where a managed terminal fits. Here it runs as an in-process terminal on a Mirage server, without a VM or sandbox.

Setup

Files

Slack at /slack and Google Drive at /gdrive, read-only. A Sheet or Doc is a JSON file.

CLIs

gws writes Docs and Sheets, ntn Notion and slack Slack.

Credentials

Five keys the Mirage server holds. The agent never sees them.
You need the mirage CLI, Slack, Google and Notion accounts, two files in Drive, and five keys.
Set up three accounts, and export five keys:In Google Drive, make a folder named Onboarding with two files:
  • Onboarding tracker, a Sheet with the columns Customer, Seats, Start, Account manager and Plan, and a row for each customer.
  • Onboarding plan template, a Doc with {{customer}}, {{seats}}, {{start}}, {{manager}}, {{goal}}, {{champion}} and {{kickoff}} where the values go:
workspace.yaml mounts Slack and Drive read-only, keeps /workspace in memory, and installs the three CLIs. Each credential is read from the server’s environment:
workspace.yaml
Export the keys and create the workspace:
The local server reads the keys when it starts, so mirage daemon restart stops a server that started without them.

Example

In this example, a deal closes and the CRM posts it to the #deals-won channel in Slack. The agent starts the onboarding. It picks an account manager from a tracker in Google Sheets, fills in a plan in Google Docs, adds the customer to the tracker, opens a project in Notion and replies to the team in Slack. The CRM posted this in Slack:
Deal won: Northwind Health · 120 seats · start 2026-12-01 · champion Priya Shah (priya@northwind.example) · goal: move clinic scheduling off spreadsheets
These are the commands the agent runs, in the terminal Setup created. Your agent sends each one with mirage shell, or through MCP, the HTTP API, RPC or SSH.
1

Read the deal from Slack

A Slack channel is a folder under /slack, with a folder for each day.
It finds Northwind Health, 120 seats, starting 2026-12-01.
2

Pick the account manager

The tracker Sheet is a JSON file under /gdrive, so jq adds up the seats each manager has.
Mei Chen has the fewest seats, so the deal goes to her.
3

Write the plan

gws copies the plan template Doc and fills in its placeholders.
The new plan sits next to the template in Drive.
4

Add the customer to the tracker

A new row with the customer, seats, start date, manager and plan link.
5

Open a project in Notion

The agent writes the page to a file, puts in the plan’s link, and ntn creates it.
A project page with a link to the plan and a kickoff checklist.
6

Tell the team

slack replies in the thread of the CRM’s message.
The team has the owner, the plan and the project in one reply.
Each line runs in the agent’s terminal with mirage shell, which keeps variables such as $plan from one call to the next.
The deal now has an owner, a plan, a row in the tracker and a project. The agent read every input as a file and made each change through the CLI for its service. For the commands and flags each CLI supports, see gws, ntn and slack. For the file layouts, see the Slack and Google Drive VFS.