Own computer by default, one command

The idea

A person connects their own computer with one pre-approved command; the official Claude Code and Codex CLIs run there under the person's own login, which the platform never opens.

The problem
Hosted execution and pasted tokens make setup slow and risky.
Why it matters
People bring their own machines and subscriptions in one step.
Where it stands
In production as of

A step-by-step replay of this idea is not published yet. The library adds one when a recorded run shows it.

  • Work on your own subscriptions

    An owner's Claude or Codex subscription serves their requests and the org's own work through any employee, never another person's request, and its turns do not count against the dollar budget.

  • Timeline collector service

    A separate collector reads GitHub and Jira through a person's own signed-in tools with read calls only. It can preview without sending, sends when the person runs a send or installs the service, and runs as a background service that survives restarts without copies.

    Recorded walkthrough

  • Guided setup and launch readiness

    Sign-up walks the owner through readiness, preferences and connections, pairs their computer and subscription, names the CEO and reports what blocks the first task.

  • Runner sandbox and egress proxy

    On the person's machine, a slice's CLI runs under sandbox-exec or bubblewrap, which deny by default. It writes only its task folder, and its only network is a proxy that reaches the vendor.

Turn the numbers into shipped work.

Crewshal runs these choices for you: a persistent AI worker with memory and rules, on your Claude and Codex subscriptions.