Skip to content
Local-first agent workspace

Move from intent to finished work.

Charles turns an objective into a visible plan, works inside the project you choose, and stays with it through verification and handoff.

Request access Download the desktop

Linux, macOS, and Windows · Hosted models, supported CLI agents, or your provider · No silent model fallback

Workspace ready
Local project
▽□·↗

Launch workspace

Prepare the public release

Audit the release, fix anything risky, and leave me a clear handoff.
▽Charles

I mapped the work into four verifiable steps. I’ll pause before the production mutation.

  1. Review release identityComplete
  2. Run security and tenant testsComplete
  3. 3Build signed artifactsRunning
  4. Prepare staged rolloutWaiting
Ask Charles or change the plan…↑
Local-first Model choice Verifiable tools

Visible

Plans and approvals

Bounded

Scoped tools and data

Flexible

Managed or BYOK

Verifiable

Evidence before done

The product

One calm place for the whole run.

A chat window is easy. Coordinating a real project—context, files, tools, approvals, cost, and proof—is the actual product.

01▽

Plan

Turns a broad objective into ordered, reviewable work.

02□

Build

Uses scoped tools in the workspace you selected.

03·

Verify

Runs the checks that prove the result, not just the attempt.

04◇

Remember

Keeps durable project context under your control.

The workflow

Understand it before you trust it.

The interface explains what Charles is doing, why the step exists, what it can touch, and what still requires you.

  1. 01
    Step 01

    Describe the outcome

    Start in plain language. Charles asks only for decisions that actually change the work.

  2. 02
    Step 02

    See the plan

    Every meaningful step, tool boundary, cost, and approval is visible before it matters.

  3. 03
    Step 03

    Receive verified work

    The run ends with evidence, changed files, and a handoff you can understand.

Model choice

Choice without ambiguity.

Charles treats the model as an explicit execution route—not a mystery label. Availability, billing ownership, and the exact route remain separate and visible.

Charles Native

Qualification-gated

Our model lane appears only after the exact artifact passes sealed quality, safety, runtime, and tool-use gates.

No silent fallback

Hosted models

Charles billed

Choose from the current server-published catalog. Routes and prices are explicit—never inferred from a model name.

No silent fallback

Your agents and providers

Provider billed

Use a supported CLI you already signed into, or connect a provider you control. Charles keeps the project boundary visible; that provider bills its own usage.

No silent fallback

Built for real work

Give Charles an outcome. Keep control of the work.

Start locally, connect the model route that fits, and see every important decision before it becomes an action.

Request access Why we built Charles