A shared workspace for AI workers

Give every worker saved memory, files, tools, credentials, and a cloud environment your team can inspect.

See how it works Create workspace
Launch review workspace Example workspace
Memory saved Tools scoped Review open

Onboarding review handoff

Research worker reopened saved files, browser tabs, and notes.

Workspace saved

Current task

Compare onboarding-v2.md against the launch checklist, flag gaps, and prepare a review note.

1 Started by teammate, continued by Research worker
onboarding-v2.mdopen
/pricing and /changelog tabssaved
Docs admin credentialread-only

Memory trail

1Audience: workspace admins evaluating worker handoff.
2Constraint: do not edit docs without teammate approval.
3Next review: summarize missing setup steps and source links.
Review state: draft ready, waiting on teammate approval before publishing changes.

Files

Briefs and source docs

Browser

Tabs saved with the task

Credentials

Scoped access only

Cloud

Runtime state saved

Workspace Workers Memory Tools

Saved state for every worker

Memory
Files
Browser
Credentials
Cloud
Tools
Team

Shared workspaces

Keep the work, not just the prompt

Put the task brief, source files, worker notes, tools, and review history in one place your team can inspect.

Learn more

Team context

Teammate startsBrief and files
Worker continuesNotes and tools
Team reviewsSaved handoff

Workspace state

Memory
Reusable task notes
Files
Shared source material
Tools
Revocable capabilities
Cloud
Saved runtime state

Persistent workers

Workers reopen the same job state

Stop restarting from blank chats. Give each recurring job a worker with its own files, notes, tabs, and review trail.

Learn more

Research worker

Reopened saved launch analysis

State loaded
1Yesterday
Compared competitor onboarding flows.
2Today
Opened onboarding-v2.md and saved browser tabs.
3Next
Prepared a review note with source links.

Scoped tools

Tools stay attached and revocable

Attach browser access, storage, APIs, and credentials to the right worker with clear limits the team can review.

Learn more
Browser

Saved tabs and current work state.

APIs

Connect only the services a worker can use.

Credentials

Scoped access with team visibility.

Storage

Files and artifacts stay attached.

Worker templates

Start from the jobs your company repeats

Explore worker templates

Research worker

Track competitor pages, summarize changes, and keep source links attached.

Support worker

Use product docs, known issues, and customer context to draft replies.

Finance worker

Review invoices, receipts, reconciliations, and recurring finance checklists.

Engineering worker

Reopen repo files, checks, reviews, and durable technical notes.

Operations worker

Coordinate vendors, forms, checklists, and repeatable admin flows.

Playbooks

Practical guides for persistent workers

Set up a workspace, attach scoped tools, and hand work between humans and workers with the source material still attached.

Guides Patterns

Set up your first worker

Create a workspace, name the job, and attach the context it needs.

Tools
Keys

Scope tool access safely

Give each worker the browser, APIs, storage, and credentials it needs.

Handoff

Hand off work as a team

Review what a worker did, see what changed, and return to the same state.

What stays attached to every worker

How a shared workspace keeps work moving

Canwoy keeps the brief, files, tools, saved browser state, and review log together for recurring company work.

1 A teammate starts the task They add the brief, files, expected outcome, and any constraints the worker needs.
2 The worker continues from saved state Notes, tools, browser tabs, credentials, and files stay attached to the workspace.
3 The team reviews the handoff People can inspect the work, approve the next step, or send it back to a worker.

Tool access is scoped to the job

Browser, repo, storage, APIs, files, and credentials can stay with the worker that uses them.

Browser tabs Repo files Storage APIs Source docs Forms Task brief Review note

Credential vault

Scope sensitive access to the right worker, make it revocable, and keep it visible to the team.

Support workerDocs read
Finance workerReceipts read
Research workerBrowser only

Activity log

See what a worker opened, changed, summarized, and handed back to the team.

09:12Loaded onboarding-v2.md and launch-checklist.csv.
09:18Used scoped browser access to reopen saved source tabs.
09:27Saved findings and next action for teammate review.

Saved cloud state

Workers can reopen the same repo, environment variables, browser tabs, and task files.

Saved
state

Create your first Canwoy workspace

Create workspace
✓Start with one workspace ✓Add one scoped worker