# FAQ and troubleshooting

A workspace only admits its owner, the person chosen when it was provisioned. A 403 after a successful sign-in means you signed in with a different account. Sign in as the owner, or ask whoever manages your company's subscriptions to provision a workspace for you. See Provision Phoeniqs AI Build.

No. Each workspace has exactly one owner, and only that person can open it. This also keeps identities apart: the Git credentials and tool logins stored in a workspace act as its owner. Provision one workspace per developer.

Commits carry the commit name and e-mail of the Git credential for the repository's host. Correct them under Settings → Credentials → Repository credentials, or mark the right credential as Default.

Yes. Closing the browser tab, reloading the page or shutting your laptop ends nothing: your terminals keep running in the workspace, and the agent carries on with its task. The next time you open the workspace, they are listed under Terminals. Only Disconnect ends a terminal.

The agent picks the interrupted task up again after the restart, with the note "The server restarted while you were working". Open terminals end with the restart, so reopen the conversation from Sessions → Continue last session. See Workspace data and restarts.

That is the safety net in your company settings. The PHOENIQS template makes the agent ask before it edits a file or runs a shell command, while read-only Git commands run without asking. Whoever maintains your company's settings repository can change it. See Settings → Company.

Tools from the company settings apply at once, but agents, rules and skills take effect the next time the workspace starts. Workspaces restart during platform updates. If you need them sooner, contact support.

The Terminal shows the agent and model in use under the prompt. By default it is a model from the PHOENIQS AI Model Service, used through your Base LLM API. To start new sessions with a different one, set the Default model under Settings → Providers & Models.

Sessions only lists the conversations of the selected Project directory, so check you have the right one selected. Conversations are kept on the workspace volume and survive restarts. If the list is empty after an import, the import replaced your history with an older export; see Workspace data and restarts.

Open Settings → Projects → Jobs and read the failed job's Log. The usual cause is a missing or wrong credential for the repository's host: the Repositories list shows which credential each repository uses, and Test checks the connection. For the PHOENIQS Git service, use an access token, not your password. See Settings → Projects.

The forgejo tool needs a Git credential for git.kvant.cloud. Add one under Settings → Credentials, and the tool uses it automatically. To give it a separate token, use Use a dedicated token instead under MCP authorizations.

Projects with a CodeGraph index are refreshed after every pull and checkout, and every 30 minutes. A project without an index is not refreshed at all: use Build CodeGraph for it in Settings → Projects. For an immediate refresh, use Rebuild CodeGraph. See CodeGraph.

The Preview only shows a server on port 8080. Start your dev server on that port, listening on 127.0.0.1, for example npm run dev -- --host 127.0.0.1 --port 8080. The tab checks again every 5 seconds and shows your app as soon as it is up. See Preview.

The browser stays black until the agent opens a page in it. If the view freezes or shows Disconnected, press Reload at the top right. See Browser.

This is expected: the workspace runs under a fixed numeric user. Your Git identity and credentials are not affected; they come from Settings → Credentials.

Your workspace runs on PHOENIQS infrastructure in Switzerland, and your repositories, conversations and credentials stay on its volume. The agent's model calls go to the PHOENIQS AI Model Service, also hosted in Switzerland, and your code and prompts are not used to train models.

The exception is a model provider you add yourself, or the OpenCode provider: those receive what the agent sends them. See Settings → Providers & Models.

Only /workspace is kept across restarts. Tools installed globally, with npm install -g or pip install --user, disappear. Install what a project needs inside the project folder instead. See Installing tools so they last.

5 GiB to start with. Run df -h /workspace in a terminal to see how much is in use, and contact support to expand it.

No. Expect a short restart. Everything under /workspace carries over, and a task the agent was working on resumes by itself. Reopen your terminals from Sessions.

Not into files in your repositories. Use Settings → Credentials: Repository credentials for Git and SVN, Provider API keys for model providers, MCP authorizations for tools, and Personal environment for anything else your command-line tools need. All are stored encrypted and kept across restarts.

Open terminals keep their view of the workspace from before the import. Restart them with Restart in the Terminal tab.

Note the version shown in the Server panel under Settings → General and contact support.