Support

One address: legcli@practicalsystems.io. It is read by the person who wrote Leg. You get a reply inside two working days.

Leg is sold by one person, not a company with a ticket queue, and the source repository is private, so there is no public issue tracker to check first. Mail is the whole support path. That also means nothing you send disappears into a triage system.

Refunds

Within 30 days of buying, reply to your receipt, or write to the address above with the email you bought under. We refund in full.

• No reason required, and we will not ask for one.
• You do not have to uninstall first, and you do not have to have stopped using it.
• The refund goes back to the card Stripe charged, usually visible in five to ten days depending on your bank.

There is no trial, because Leg does not pay off on a schedule. It pays off in the one moment a limit lands in the middle of something, which may be day two or day twenty. The guarantee is there so that waiting for that moment costs you nothing.

License keys

Your key arrives by email straight after checkout, from legcli@practicalsystems.io. Activate it with:

leg license activate <key>

Common problems, in the order they happen:

• The email has not arrived. Check spam, then write to us with the email address you paid with. Keys can be resent any number of times.
• The key is refused. Run leg license status and send us what it prints. Keys are Ed25519 tokens verified offline, so a refusal is a real signature or date problem, never a server being down.
• A new release stopped accepting a Personal key. A Personal license covers every release dated on or before the date printed in your key. The releases it already covers keep working; a newer one needs a renewal. leg license status prints the date.
• You changed machines. Personal is one named person on any number of machines, so activate the same key again on the new one. leg license deactivate exists if you want the old machine to stop carrying it.

Bug reports

Send these four things and most bugs need no follow-up questions:

1. leg --version and leg status, plus your OS.
2. Which agent CLI and version, for example claude --version.
3. What you expected, and what happened instead.
4. The part of ~/.leg/board.log around the time it happened. Leg redacts secrets from its own logs, but read it before sending.

Security reports

Email the same address with SECURITY in the subject. Please give a fix a reasonable window before publishing details. What is in scope and what is not is set out in the security policy shipped with the package, and the short version is: the board binding and its token seam, the environment stripping each adapter does, and the secret redaction are all in scope; the agent CLIs themselves are not, report those to their own maintainers.

What is supported

• Node 22 or newer. Windows, macOS and Linux; the test suite runs on all three on every commit.
• The latest minor release gets fixes. Upgrade with npm install -g legcli@latest.
• Agent CLIs: Claude Code, Codex and agy. Which readings are live against which version is printed in what Leg reads from each CLI, with the date each one was checked on a real machine.

Before you buy

Everything Leg does, what it edits, what it never edits, and what it reads from each agent is written out in the documentation, which is the same text that ships inside the package. Ask us anything that is not answered there, before paying rather than after.

Leg is commercial, source-available software by Wes Sander. The source you run ships in the npm package. Questions or a refund: legcli@practicalsystems.io.