An agent says it isn't signed in, but you just logged in
OAuth tokens for some CLIs expire after about eight days. Go to Settings › Agents and click Check again; if it stays red, click Connect to reopen the vendor's sign-in flow.
Most problems sit in the CLI or in permissions on your machine, not in Altor. Start with self-diagnosis; if that doesn't settle it, send us a report with logs.
OAuth tokens for some CLIs expire after about eight days. Go to Settings › Agents and click Check again; if it stays red, click Connect to reopen the vendor's sign-in flow.
Usually the CLI is waiting for a permission prompt with nowhere to show it. Check the Runs › Raw log tab. If you see a line waiting on permission, reset the permission mode for that adapter in Settings.
That's a warning, not a block. Altor runs a smoke test when it meets an unknown version. If the parser breaks, roll back to the version in the manifest or send us logs so we can update it.
Altor never uses --force on its own. Common causes: a child process is still alive, there are uncommitted files, or there are files outside gitignore. Open the Storage panel to see the specific reason for each worktree.
Turn on lockfile-based caching in the worktree config. With pnpm the store is shared, so it takes only seconds; with npm or yarn, Altor creates a junction to the root folder.
The app must be open. If the machine sleeps, the schedule won't catch up on its own; when you reopen Altor it asks whether to run what was missed. Also check the budget cap: at 100% schedules turn off and must be re-enabled by hand.
If the datasource goes through a tunnel, check the tunnel status first: it's the prime suspect. Altor only spawns the MCP server after the tunnel passes its health check.
No. Sign-in happens on the provider's official page, handled by the CLI, which stores the token itself. Each process gets only the environment variables it needs, so one agent can't see another agent's keys.
Prompts, transcripts, diffs, code, and run, event, usage, score and rule data live in SQLite on your machine; datasource passwords live in the operating system's secure store (DPAPI/Keychain) and can't be read back into the UI. Altor's servers store your account, devices, sign-in security logs, session metadata (title, project name, summary, model, estimated cost), discussion content you choose to share, notifications and billing data; they don't store prompts, transcripts, diffs or source code. Content between your computer and phone goes through an end-to-end encrypted relay. Details at /privacy.
Each run works in its own git worktree. Read-only repos are mounted read-only and writes are blocked at the permission layer. You accept changes file by file before they reach the main branch.
There's an offline mode: it turns off update checks and model list refreshes. Agents themselves still need a network, since they have to reach the model provider.
No. Altor ships a manifest of verified versions and calls the CLIs you've installed. If you uninstall Altor, those CLIs keep working exactly as before.
Team leaderboards, centralized policy, SSO and a self-hosted edition are on the roadmap. Altor doesn't measure individual working hours and never will.