Appearance
Uploading from your machine
Developers upload with a personal login rather than a project token; each run records its uploader.
Sign in
bash
easytrace login- The CLI prints a code and opens
…/app/cli/authorize?code=…(--no-browserprints the link only). - Sign in if needed, check the code matches your terminal, then click Authorize. Never approve an unexpected code.
- The terminal prints
Signed in as @you on <api>.
The code expires after 10 minutes. easytrace login refuses to run in CI (CI=true) — CI uses a project token.
bash
easytrace whoami # @you on https://api.easytrace.dev (or "Not signed in.")
easytrace logout # revokes this machine's session and forgets itWhich project
A login can upload to any project you can access. Choose it with project in easytrace.config.json or --project <id>.
If you are removed from the project's organization, uploads stop with project … not found — access is checked on every upload.
Local runs in the dashboard
Runs uploaded with a login are labelled Local and show who uploaded them (hover the chip). The Runs page has a Source filter: CI and local, CI only, Local only.
A run is also Local when it was uploaded with a project token but no CI was detected (e.g. a token used on a laptop).
Uploading the default branch
Local runs count like CI runs: a local run on the project's default branch (main) can become the new failure baseline. If it has coverage, it can also become the coverage baseline. The CLI warns before such an upload:
text
EasyTrace: uploading main from your machine — this run becomes the baseline for new failures on main.and uploads anyway. Work on a branch, or set EASYTRACE_BRANCH=local/<you> to keep a local run out of the baseline.
Sessions
- A session lasts 90 days after its last use; using it extends it.
- You can have 20 signed-in machines; signing in on a 21st revokes the one used longest ago.
- CLI sessions in the dashboard (account menu, top right) lists your machines with their last use. Revoke one you lost or no longer use; its uploads stop immediately.
- Signing in again on the same machine replaces its previous session.
The token is stored in ~/.config/easytrace/credentials.json ($XDG_CONFIG_HOME if set, %APPDATA%\easytrace\ on Windows), readable only by you (0600), one entry per API URL.