Sync, team and plans
The server holds a shared workspace. The agent pushes to it in the background; you can pull the whole thing back onto a new machine.
Connecting the agent
Take your key from Settings → Auth Key on qaclan.com — it stays readable there, so you can come back for it.
Paste it into the first screen the app shows you, or into Settings → Auth Key inside the app if you are changing an existing one. The key is checked against the server and stored in ~/.qaclan/config.json.
Disconnect on that same screen removes the stored key. Local data is untouched and the agent keeps working offline; only syncing stops.
Prefer the terminal?
qaclan loginqaclan login --key <auth_key>The bare form prompts for the key; --key is for scripts and unattended hosts. Add --server <url> to point at a different server.
qaclan logoutWhat syncs, and when
Sync is automatic and best-effort. Creating, updating or deleting anything queues it in the background; if the network or the server is unavailable, the command you ran still succeeds and the queue catches up later. Sync never blocks your work.
- Projects and features
- Scripts, including the script files themselves
- Suites and their ordered items
- Runs and their results
- API collections, folders, requests, saved examples and collection variables
- API run results, including negative-testing severities and schema-drift verdicts — see Negative testing and schema drift
- Environments and their variables
- The API reference generated from real traffic
Environment values sync too
Environments and their variables are part of the workspace, so a teammate with access can see them. Keep production credentials out of a shared workspace — see Environments and secrets.
Push and pull
Day-to-day you should not need either of these — syncing happens on its own. They exist for explicit, on-demand resyncs: a new machine, or a queue that got stuck.
Both are buttons at the top of the app. Pull downloads the workspace and merges it into the local database — projects, features, scripts (written into ~/.qaclan/scripts/), API collections, folders, requests and collection variables, environments and their variables, suites and suite items. Existing rows are updated in place; new ones are inserted.
Push re-queues everything for the active project and drains the queue immediately, rather than waiting for the background worker.
Pull restores the workspace, not browser run history
It brings back the things you built — projects, features, scripts, suites, environments and your API collections. Browser run history stays on the machine that produced it. Runs synced to the server remain visible in the cloud workspace at any time; they are simply not copied into a second machine's local database.
The printed summary names six things — projects, features, scripts, suites, environments and variables — but API collections, folders and requests come down with them.
Prefer the terminal?
qaclan pullqaclan pushqaclan push --all--all pushes every project rather than just the active one. pull prints a per-item log, then a summary.
Setting up a new machine
qaclan login --key <auth_key> && qaclan pullTwo commands and the machine has your projects, scripts, suites, collections and environments. This is the intended answer to onboarding a teammate or replacing a laptop.
Reports
The server derives six reports from synced run history:
| Report | Answers |
|---|---|
| Flakiness index | Which scripts pass and fail without anything changing |
| Pass-rate trend | Whether a suite is getting healthier or worse over time |
| Duration trends | Which scripts are slowing down before they start timing out |
| Failure points | The steps a suite dies at most often |
| Suite health | One view across every suite in the workspace |
| Time to green | How long a broken suite stays broken |
AI script analysis
On the Team plan you can request an analysis of a script: what its failures have looked like across history and where it is unreliable. It reads finished results after the run.
It does not modify tests. No step is rewritten, no selector is healed, and no model participates in execution — that boundary is deliberate, because a suite whose steps can change is not a regression suite.
Team, invites and seats
- Invite a teammate by email from the team page. The invitation link is valid for 48 hours.
- Billing is per seat. The seat count cannot drop below the number of members currently in the workspace — remove someone first, then reduce seats.
- Seat count is changed on the upgrade page, which Settings → Billing links to. Cancellation and past invoices live under Settings → Billing itself.
- Members are listed on the team page, where an admin can change a member’s role between admin and member, or remove them. An activity feed records what changed.
What the plan changes
The agent is identical on both plans: the same recording, imports, suites, runs and local reports, with no script limits. The Team plan adds the shared workspace, the reports above, AI analysis and additional seats. Cancelling returns the account to Community; the agent carries on unchanged.
There is no trial, because Community is free permanently rather than for a window. See pricing for the seat and billing detail.