Work on your own subscriptions

The idea

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.

The problem
Paying API prices for work a subscription already covers.
Why it matters
Owners use plans they already pay for, bounded by vendor limits.
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.

  • Own computer by default, one command

    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.

  • Bring your own model keys

    A person or org connects its own provider API keys after one free read-only check, and sign-in tokens or credential files are refused before anything is stored.

  • Own accounts, execution profiles and payers

    Hosted work uses API keys. A subscription runs only through the vendor's product or the person's own runner. Executor, model, host and payer inherit from the platform through org, role and worker.

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.