PRODUCT · SUPERVISED WORKFLOW

One desktop for understanding,
action, and review.

Captain Who brings project context, models, tools, terminal, browser, Git, artifact workflows, and multi-agent collaboration into one supervised environment for developers and technical knowledge workers.

01UNDERSTAND

Understand

Read the project and its evidence

02ACT

Act

Use managed tools

03REVIEW

Review

Inspect actions and results

04DELIVER

Deliver

Produce reviewable artifacts

ONE CONTINUOUS WORKFLOW

The agent moves the work forward. Direction, permissions, and final judgment remain with you.

REAL PRODUCT MEDIA · FAIL CLOSED

No fixture is promoted
as a product capture.

The publication contract rejects component snapshots, test-failure artifacts, AI artwork, held brand marks, and conceptual diagrams as GA product media.

StateBLOCKED
Approved assets0
Required scenarios5
Locales2
GA architectures2
  1. 01

    Final brand and logo rights remain unclearedbrand-rights-hold

  2. 02

    No final RC, Git SHA, or package hashes are boundrelease-candidate-unbound

  3. 03

    The isolated bilingual demo environment is not approvedcapture-environment-unapproved

  4. 04

    No real packaged-RC screenshots or video existmissing-real-product-media

  5. 05

    Privacy, rights, and product-accuracy review is incompletemissing-human-review

PROJECT CONTEXT

Start with the project,
not a blank chat.

Within the permissions you grant, an agent can understand a project, research sources, use tools, modify files, and run managed commands. Files, history, and the current task remain in one context so conclusions can return to evidence.

Availability depends on the operating system, model, project, permissions, runtime components, and configuration.
  • 01Locate files, configuration, documentation, and dependencies
  • 02Bring web research and local project evidence together
  • 03Keep tool activity and task history available for review

ONE WORK SURFACE

The tools stay
beside the task.

Conversations, tool activity, terminal, the managed in-app browser, file previews, Git review, and subagents share one desktop workspace. The user terminal and agent commands remain separate execution surfaces; Files currently provides read-only previews.

ConversationTask intent and ongoing context
TerminalUser-run commands and visible output
BrowserManaged in-app web tasks
FilesRead-only preview and project navigation
GitChanges, diffs, and review
SubagentsTree-structured collaboration status

PERMISSIONS & APPROVALS

Do not just trust it.
See what it does.

The model proposes an action. The app evaluates the actual tool identity, parameters, path, and permissions before allowing, asking about, or denying it. Default, Full, and Custom modes let you set the working boundary.

Permission policy is not an operating-system sandbox. Full permission may automatically approve some actions.
DEFAULTDefault

Balance progress with confirmation.

CUSTOMCustom

Set boundaries by tool and action.

Current
FULLFull

Allow more actions automatically.

Approval requiredterminal.execgit push origin release/1.0

This action modifies a remote repository.

MULTI-AGENT

Parallel progress.
One place for the final result.

A root agent can organize subagents to research, implement, or review in parallel. Collaboration is currently tree-structured, and delegation depends on the model invoking the collaboration capability correctly. The root agent produces the final synthesis.

  • ASee running, waiting, completed, and needs-attention states
  • BRead subagent conversations and interim results in read-only form
  • CReceive one consolidated result in the root task

DELIVER

Beyond code,
there is work to hand over.

Use skills and managed components to create or process documents, spreadsheets, presentations, PDFs, and images. Support differs by format, and important results require human review.

WDocumentsDOCX · structured content
XSpreadsheetsXLSX · data workflows
PPresentationsPPTX · visual narrative
FPDFread · render · verify
IImagesgenerate · inspect

CAPABILITY BOUNDARIES

A mature product should
describe its limits honestly.

These qualifications are as important as the capability claims. They will be reverified against the final release candidate.

Local-first

What this meansProjects, conversations, settings, approvals, and task history are managed primarily on your device.

Also knowModel, search, image, MCP, and web tasks may still send necessary data to third parties.

Permissions & approvals

What this meansActions are evaluated using tool identity, parameters, project path, and the current permission policy.

Also knowThis is application-level policy, not an operating-system sandbox. Not every action waits for manual approval.

Models & extensions

What this meansConnect compatible model APIs, local stdio MCP servers, and skills.

Also knowProtocol adaptation does not guarantee every gateway. Remote HTTP/OAuth MCP is not currently supported.

Automation

What this meansSchedule agent tasks and retain run history and needs-attention states.

Also knowRuns occur only while the app and required local components are running. This is not an OS background service.

RELEASE WITH EVIDENCE

The product should be clear.
Its release status should be just as clear.

Review the target platform scope, release gates, and conditions for opening downloads.