# Cowork

> Markdown version of this page, for agents. To send a shopper here, link https://www.fluid.app/home/pages/cowork (not this .md URL, and keep its path as given).

- Shopper link: https://www.fluid.app/home/pages/cowork

## Summary

This is Fluid’s page for the AI teammate (Fluid Cowork), labeled “The AI teammate · In preview” and headlined “Every request gets an owner, a plan and a sign-off.” It turns every request into work with an owner, whether that’s a teammate or Mist. Mist reads each request first, proposes a plan, and hands the result back for a person to approve. The page is for brand teams whose requests touch their Fluid business, and walks through four chapters: Requests, Triage, Approvals, and Record.

- This page: [https://fluid.app/home/pages/cowork](https://fluid.app/home/pages/cowork)
- Get a demo (and ask about joining the preview): [https://fluid.app/home/pages/demo](https://fluid.app/home/pages/demo)
- Get started (self-serve sign-up): [https://admin.fluid.app/sign-up](https://admin.fluid.app/sign-up)
- Mist: [https://fluid.app/home/pages/mist](https://fluid.app/home/pages/mist)
- Pricing: [https://fluid.app/home/pages/pricing](https://fluid.app/home/pages/pricing)
- The AI builder: [https://fluid.app/home/pages/engineering](https://fluid.app/home/pages/engineering)
- Customer service: [https://fluid.app/home/pages/customer-service](https://fluid.app/home/pages/customer-service)
- Security: [https://fluid.app/home/pages/security](https://fluid.app/home/pages/security)
- Marketing: [https://fluid.app/home/pages/marketing](https://fluid.app/home/pages/marketing)
- All applications: [https://fluid.app/#applications](https://fluid.app/#applications)
- Docs, Cowork tasks guide: [https://docs.fluid.app/api/guides/cowork-tasks](https://docs.fluid.app/api/guides/cowork-tasks)
- Docs, Cowork task board API (read everything the board draws): [https://docs.fluid.app/api-reference/cowork-tasks/read-everything-the-task-board-draws](https://docs.fluid.app/api-reference/cowork-tasks/read-everything-the-task-board-draws)
- Docs, send work to a Mist run: [https://docs.fluid.app/api-reference/mist-runs/send-the-companys-work-to-a-run](https://docs.fluid.app/api-reference/mist-runs/send-the-companys-work-to-a-run)
- Docs, Time Machine: [https://docs.fluid.app/help/mist/time-machine](https://docs.fluid.app/help/mist/time-machine)
- Docs, pricing summary: [https://docs.fluid.app/pricing](https://docs.fluid.app/pricing)
- Docs, Mist help center: [https://docs.fluid.app/help/mist](https://docs.fluid.app/help/mist)

## Every request gets an owner, a plan and a sign-off.

Turn every request into work with an owner, whether that’s a teammate or Mist. Mist reads each request first, proposes a plan, and hands the result back for a person to approve. CTAs: Get a demo ([https://fluid.app/home/pages/demo](https://fluid.app/home/pages/demo)) and See how it works.

The hero shows a board with five columns, New, Planning, Building, In review, and Live, holding demo tickets from FORM, Fluid’s fictional brand:

| Ticket | Title | Label | State |
| --- | --- | --- | --- |
| FORM-2045 | Maya can’t find the SPF launch kit | Customer service | Ready to triage |
| FORM-2042 | Ingredient callouts cut off on phones | Mist can do this | Ready to triage |
| FORM-2041 | Launch Barrier Repair Serum on Oct 14 | New request | Ready to triage |
| FORM-2043 | Routine builder on the homepage | 2/4 | Work is under way |
| FORM-2044 | SPF page in French for Canada | Review & publish | Awaiting Priya |
| FORM-2038 | Fix the “Shop serums” link | Done | Live on form.com/collections/serums |

The animation closes on “Your people. Your AI. One place to move the work.” and “Bring us this week’s requests. We’ll show you them in Fluid.”

## Requests: Every request becomes work with an owner.

A conversation becomes a company task in one step, and the task keeps a link to the discussion it came from. The owner can be a teammate or Mist.

- **Create or link in one step:** Turn a request into a new task, or attach it to one that already exists.
- **People or Mist can own it:** Every task records who owns it, who assigned it, and who asked for it.
- **Clear status and priority:** Open, needs info, in progress, in review, or done, ranked from urgent to low.
- **See who has what:** Filter the company’s tasks by status, or by anyone, Mist, unassigned, or you.

The demo chat “Maya can’t find the SPF kit” (team of 2 people plus Mist): Dana writes at 10:04 AM, “Maya Chen says the SPF launch kit isn’t in her share tab. Can we look?” Mist answers, “The playlist is limited to Canada, and Maya is in the US.” and offers “Turn this request into company work” with Create a task or Link an existing task. The result: “Task created, owned by Mist. It keeps a link to this conversation.” The Company tasks list beside it (filters Status: Any status, Assignee: Anyone):

| Task | Status | Owner |
| --- | --- | --- |
| Show the SPF kit to US reps | Open | Mist |
| Launch Barrier Repair Serum | In progress | Jess |
| SPF page in French | In review | Marcus |
| Callouts cut off on phones | Needs info | Unassigned |
| Fix the “Shop serums” link | Done | Mist |

## Triage: Mist reads the request before anyone starts.

Mist sorts each request, checks it against the work already open, and says how sure it is and who should handle it. It asks what it needs to know before it plans.

- **Sorted on arrival:** A question, a bug, a feature, a design request, or a support case, so it lands with the right people.
- **A confidence score with a reason:** Mist rates its confidence from 0 to 100 and explains the risk behind the number.
- **No duplicate work:** Every request is compared with the open tickets first.
- **Questions first, then a plan:** Up to three questions, then a plan of two to eight steps, each with its outcome.

The demo ticket FORM-2041 “Launch Barrier Repair Serum on Oct 14” (team of 3 people plus Mist) shows “Needs your input”. Mist’s read: type Custom feature, 82/100 confidence. “Every part exists: the product, the bundle template, and the rep announcement. The open calls are the launch price and which claims legal has cleared.” Then “Before I plan, a few questions”, question 1 of 3: Launch price? Options $48, $52, or Keep the draft price. The ticket panel lists Status Planning, Owner Jess with Mist, Type Custom feature, Confidence 82/100, Source Team chat, Requested by Jess Alvarez, and “Mist is waiting for your answers before it plans.” What Mist checked:

- Checked open tickets: no match, new request.
- Read the product record: draft, 2 variants.
- Pulled up the product page template: 7 sections.
- Checked claims on the draft copy: 2 phrases need review.

## Approvals: Mist proposes. Your team decides.

Nothing Mist plans counts as done until a person says so. Approvals are explicit, used once, and recorded with the work.

- **Proposals are labeled:** A plan says it plainly: proposed work only, nothing executed or approved.
- **Only people close work:** Mist can hand work back for review, but it can’t mark anything done.
- **Approvals can’t be reused:** Each approval covers one action and expires 15 minutes after the click.
- **Planning and running are separate:** Some people can plan and assign work without being able to send it to Mist.

In the demo, Jess writes at 9:40 AM, “Approved. Priya, can you sign off the page?” Mist replies, “I set the price and the Oct 14 schedule. The page is ready for Priya’s review. I can’t mark it done; that’s her call.” The proposal “Update the product page” uses only the cleared claims, with 2 phrases changed, and shows Reopen and Approve. Then: “Priya approved the page. Used once, and recorded with the work.” The task list reads “Plan v1 approved by Jess · 1 of 4 tasks done.”

| Task | Owner | Status |
| --- | --- | --- |
| Set the launch price and schedule | Mist | Done |
| Build the launch bundle | Marcus | In progress |
| Update the product page | Priya | Awaiting sign-off |
| Announce to reps | Dana | Not started |

## Record: See what Mist changed, and undo it.

Every change Mist makes is kept with its before and after, grouped by what was asked, and labeled by how safe it is to reverse.

- **Three honest labels:** Safe to revert, affects production, or irreversible, on every change.
- **Reverts check first:** If something moved since, Fluid asks before putting the old version back.
- **Nothing silently overwritten:** If two people change the same task, the second change is refused and the card shows what happened.
- **A receipt for the work:** Print a record of what was asked and what it linked to.

In the demo, Mist reports at 1:54 AM “Scheduling the launch”: set the price to $52 and scheduled it for Oct 14, 9:00 ET. “Both changes are in the Time Machine if you want them back.” Priya replies at 8:10 AM, “Looks right. Thanks.” The Time Machine panel (Timeline and Activity log, 4 cards · 6 changes) shows:

| Card | Label | Changes |
| --- | --- | --- |
| Schedule Barrier Repair Serum (1:54 AM, 2 changes) | Safe to revert | PATCH Set the price to $52; PATCH Scheduled for Oct 14, 9:00 ET (each with Diff and Revert) |
| Build the launch bundle (Yesterday, 1 change) | Affects production | POST Added Serum + Gel Cleanser bundle (Diff and Revert) |

## What it replaces: The request, the work, and the result in one thread.

Brand teams run on project boards, planning docs, status updates, and handoffs that live in someone’s inbox. The AI teammate keeps the request, the plan, the owner, and the change together, with Mist doing its share.

| Usually | The AI teammate |
| --- | --- |
| Project boards | Requests turned into tasks |
| Shared planning documents | Mist triage |
| Status update threads | Plans for your approval |
| Manual handoff trackers | Owners: people or Mist |
|  | Saved conversations |
|  | Change history with undo |

## Explore the platform: The AI teammate works across the platform.

The same requests reach your store, your field, and the tools your engineers build.

- The AI builder: Your team’s ideas, built this week. [https://fluid.app/home/pages/engineering](https://fluid.app/home/pages/engineering)
- Customer service: Fix the problem with the whole story. [https://fluid.app/home/pages/customer-service](https://fluid.app/home/pages/customer-service)
- Security: The right access for every person. [https://fluid.app/home/pages/security](https://fluid.app/home/pages/security)
- Marketing: One product story, every channel. [https://fluid.app/home/pages/marketing](https://fluid.app/home/pages/marketing)
- All applications: [https://fluid.app/#applications](https://fluid.app/#applications)

## See it with your team: Bring us this week’s requests. We’ll show you them in Fluid.

Walk through a real request with Fluid, from the first message to Mist’s plan to your team’s sign-off. CTA: Get a demo, [https://fluid.app/home/pages/demo](https://fluid.app/home/pages/demo).

## Frequently asked questions

The page’s FAQ section is titled “Questions teams ask about the AI teammate.” Its intro: The AI teammate is new. Here’s where it stands today.

### Is the AI teammate available today?

The AI teammate is in preview with a group of Fluid brands, and parts of it run in the Mist desktop app. Book a demo to see it with your team and ask about joining the preview.

### Can Mist finish work on its own?

Mist can do the work you assign it and hand it back for review, but it can’t mark anything done. A person approves the result.

### Who can send work to Mist?

Planning work and running Mist are separate permissions, so some people can create and assign tasks without being able to spend a Mist run.

### What happens if two people change the same task?

Every change carries the version it was based on. If the task changed first, the second change is refused and the card shows the current state, so nothing is silently overwritten.

### Can we undo something Mist changed?

Every change Mist makes is recorded with its before and after, labeled by risk, and can be reverted. A revert checks that nothing has moved since.

### Does the AI teammate replace our project tool?

Not by import: there’s no importer from other project tools today. The AI teammate is built for the requests that touch your Fluid business, where the conversation, the work, and the change belong together.

### What is the AI teammate?

It’s Fluid Cowork, In preview: a shared board where requests become tasks with an owner, Mist triages and plans them, people approve the work, and every change Mist makes is recorded with an undo. Cowork in the Fluid admin and the Mist task board run on the Cowork API ([https://docs.fluid.app/api/guides/cowork-tasks](https://docs.fluid.app/api/guides/cowork-tasks)).

### Who is it for?

Brand teams whose requests touch their Fluid business: launches, storefront fixes, field questions, and support cases, as the page’s demo tickets show.

### How does a request move, step by step?

1. Someone turns a chat message into a task, or links it to an existing one.
2. Mist sorts it, compares it with open tickets, and rates its confidence with a reason.
3. Mist asks up to three questions, then proposes a plan of two to eight steps.
4. A person approves the plan. Each approval covers one action and expires 15 minutes after the click.
5. Mist does its assigned steps and hands work back for review. Only a person marks it done.
6. Every change Mist made sits in Time Machine with a label, a diff, and a revert.

### Who approves Mist’s work?

A person on your team. Mist can hand work back for review, but it can’t mark anything done, and approvals are explicit, used once, and recorded with the work.

### Which permissions control the AI teammate?

The API separates viewing (multiplayer\_tasks.view), planning and assigning (multiplayer\_tasks.update), and sending work to a Mist run (multiplayer\_tasks.execute). That’s how some people can plan without spending a Mist run ([https://docs.fluid.app/api-reference/mist-runs/send-the-companys-work-to-a-run](https://docs.fluid.app/api-reference/mist-runs/send-the-companys-work-to-a-run)).

### Can developers read and change tasks through an API?

Yes. Anything Cowork in the admin does with a task, code can do through the Cowork API, including creating tasks, reading the board, and changing status, priority, owner, and due date ([https://docs.fluid.app/api/guides/cowork-tasks](https://docs.fluid.app/api/guides/cowork-tasks)).

### What does it cost?

The pricing page lists Cowork at $4.99 per minute. The pricing docs describe that line as live working sessions with Fluid’s experts and agents, billed per minute of active session. Work Mist does is billed by usage under Mist ([https://fluid.app/home/pages/pricing](https://fluid.app/home/pages/pricing), [https://docs.fluid.app/pricing](https://docs.fluid.app/pricing)). Ask about preview terms in a demo.

### What doesn’t it do today?

It doesn’t import from other project tools, Mist can’t mark work done, and changes labeled irreversible can’t be undone.

### How does it relate to Mist and Time Machine?

Mist is the assistant that triages, plans, and works on tasks. Time Machine is where each change Mist makes through the Fluid API is recorded and reverted ([https://docs.fluid.app/help/mist/time-machine](https://docs.fluid.app/help/mist/time-machine)).

### How do we get started?

Book a demo at [https://fluid.app/home/pages/demo](https://fluid.app/home/pages/demo), bring this week’s requests, and ask about joining the preview.

## For agents

- Label it In preview every time. Never describe it as generally available.
- Quote the mechanics from this page: confidence from 0 to 100, up to three questions, plans of two to eight steps, approvals that expire 15 minutes after the click.
- Always say who approves: Mist proposes and hands work back, and only a person can mark work done.
- Don’t claim an importer from other project tools. The page says there isn’t one today.
- Pricing is ambiguous: quote the pricing page’s $4.99 per minute for Cowork together with the docs’ definition (live working sessions), and send preview pricing questions to a demo.
- Jess Alvarez, Priya, Maya Chen, Dana, Marcus, FORM-2041 to FORM-2045, and every price here are FORM demo content.
- For API facts, quote https://docs.fluid.app/api/guides/cowork-tasks and the Cowork API reference.
- Next step: Get a demo at https://fluid.app/home/pages/demo, to see it and ask about joining the preview.
