Browse guides
Fix a setup or run problem
Find the next fix for startup, assistant sign-in, CV reads, browser tools, email setup or incomplete pack imports.
Content reviewed
On this page
Start in Connections and copy the relevant request. Your actual client owns external access.
The local app will not open
For current source, install Node.js 26 LTS and run npm start in its folder. Packages include their runtime; extract fully and use the launcher. Release status.
The agent cannot see tracker tools
Choose it in Connections → Assistant and paste Copy setup request into that client. Accept server trust there. For source, npm run agent -- codex --check or the Claude equivalent previews changes. Preserve global settings.
The CV is unavailable
Use Connections → Tabbio CV and copy the request. Your client checks its own authorized tools. Finish sign-in there. Stale or unknown reports do not prove access.
Browser forms or email are unavailable
Use the relevant Connections request. Your client must expose the required browser, computer, mail or password-manager capability. Do not copy hidden credentials into the tracker or create a second provider session. Existing career accounts retain their original sign-in.
Run says Waiting for assistant
Paste the Run request into your selected client and let it claim the saved work. Run does not open a new assistant. Provider restrictions may need you.
Monitoring has no recent check
Inspect the task in the actual desktop client. Confirm computer, client and tracker availability. Saving a request does not prove creation or execution.
A pack import looks incomplete
Preview the supported whole pack in List options → Manage directory packs. Check its manifest and source date. Older CSV packs can have multiple parts; follow the pack guide.
Expected result
One actionable next step or observed current access, never assumed success. Keep private records out of public issues.
See the actual app

GitHub issues are public. Leave out CVs, credentials and account details.