TraceX in your terminal. A coding agent in your repo.
Ask TraceX about your production systems without leaving the terminal, and let it fix bugs in your repository, with your approval for every change.
One line. macOS and Linux.
The installer downloads the release for your system, checks its checksum, and puts tracex on your path. Windows builds are on the releases page.
curl -fsSL https://tracexpro.com/install | sh$ curl -fsSL https://tracexpro.com/install | sh✓ Installed tracex 0.2.0$ tracex loginOpening your browser to sign in…✓ Signed in$ tracex init✓ Linked to project payments-api
Everything in a few commands.
tracex loginSign in through your browser, with your usual SSO or two-factor sign-in. The CLI never sees a password.tracex initLink a git repository to its TraceX project, connecting it through the GitHub App if needed.tracex -cOpen a session and ask about your data, code and recent changes.tracex -c "question"Ask one question and print the answer; piped input works too.tracex usageSee how much of your plan's limits is left.tracex statusWho is signed in, and which project this folder uses.The same answers as the dashboard.
In a linked repository, TraceX answers from your databases, code and logs, and shows only the answer: no noise, just what it found.
- Shows what it's doing while it works
- Tables and code rendered in the terminal
- Every answer cites its sources
$ tracex -c "why are refunds stuck?"⠋ Checking database⠋ Checking codebase34 refunds are stuck in pending since Oct 21.Migration 0142 renamed the state; the workerstill filters on the old one. refunds.py:42
A coding agent that asks first.
In a repository that isn't linked to TraceX, the CLI becomes a coding agent: it searches and reads the code, edits files and runs your tests to do what you ask.
- Every edit shown as a diff, every command before it runs
- Yes, always or no, for each change
- Never reads or writes outside the repository
$ tracex -c› fix the refund worker filter Edit app/workers/refunds.py - state="pending" + state="awaiting_payout" Apply? (y/a/n) y Run pytest tests/test_refunds.py? (y/a/n) y ✓ 12 passed
Know what's left, from the terminal.
tracex usage shows your plan's limits and how much is left, the same numbers as the dashboard.
- Investigations, messages and AI allowance
- Only your input and visible output count
/usageinside a session too
$ tracex usageInvestigations ████████░░░░░░░░ 24 / 50Chat messages █████░░░░░░░░░░░ 140 / 500AI allowance ███░░░░░░░░░░░░░ 18%Resets in 9 days
CLI questions.
Which systems does the CLI run on?
macOS and Linux through the install script, and Windows from the releases page.
How does it sign in?
tracex login opens your browser, where you sign in as usual with SSO or two-factor. The CLI never sees your password, and the session can be revoked from the dashboard.
What can coding mode touch?
Only the repository it was started in. It asks before every edit and every command, and never reads or writes outside it.
Find the root cause.
Ship the fix.
TraceX is free during the private beta. Connect a database and a repository and ask your first question in minutes.