Troubleshooting

Each entry states the symptom, the cause, and the fix.

The app says to close Admiral before signing in

Symptom. admiral login or admiral logout asks you to stop the engine.

Cause. The storage mode is fixed when the engine starts. Sign-in changes the mode, so it must happen between runs.

Fix. Close the Admiral app, run the command, then start the app again.

I signed in, but my old sessions are not on my other device

Cause. This is by design. Signing in never moves existing sessions.

Fix. Sessions sync from the moment they belong to a signed-in device. For old work, keep using the device that holds it, or reopen the work in a project on the host you want. See Where your data lives.

The composer shows Queue instead of Send

Cause. Queue is the correct action when the message carries an attachment, when the session runs a legacy agent, or when the agent is parked on a question.

Fix. None needed. Queue delivers the message as soon as the host can. See Steer and queue.

Settings says OpenCode needs setup

Cause. The machine has no supported OpenCode release, or the runtime failed a check.

Fix. Open the Providers settings page and select retry on the OpenCode card. Admiral provides and manages the runtime itself.

A session is red

Cause. The run failed: the agent hit an error, or the run was interrupted in a way it could not recover from.

Fix. Read the end of the transcript. Then send a follow-up message in the same session; the agent resumes with full context. Nothing you queued is lost.

A terminal tab disappeared

Cause. A tab whose shell exited is kept for 30 minutes, then removed. Admiral keeps at most 32 terminal tabs per session.

Fix. Open a new tab. Use history in the new shell to find recent commands.

A theme edit broke my theme

Cause. The edited theme file no longer parses.

Fix. Nothing to do in a hurry: the theme keeps its last known good appearance. Fix the file and reload the theme. See Themes.

Gemini will not sign in on my second machine

Cause. Gemini sign-in completes on the device where you start it and is local to that device.

Fix. Sign in on each device that needs Gemini, from the Providers settings page.

My machine stayed awake all night

Cause. Power management is set to auto or on, and an agent run was active. Auto holds system sleep while an agent works.

Fix. Set power management to off if you want the machine to sleep on its normal schedule.

The agent does not see my simulators or emulators

Cause. The injected admiral tools are off for that device, or no simulator is booted.

Fix. Boot the simulator or emulator first. Then check the tools switch in Settings, under Connections. See Drive mobile simulators.

Sign-in shows AUTH-009, Account not invited

Cause. Admiral accounts are invite-only. The address you signed in with is not on the tester list.

Fix. Request an invite at admiral.standardmethod.us. After the approval mail arrives, sign in again with the same address. Admiral keeps working on this device without an account. See The tester program.

Admiral shows AUTH-010, Access removed

Cause. The account is no longer in the tester program.

Fix. Sign out to keep working in the local profile. Your local sessions stay on your machines. Write to admiral@standardmethod.us if you think this is a mistake.

An update shows UPD-002, Update signature not valid

Cause. The downloaded update did not pass the code signature check. Admiral kept the installed app.

Fix. Do not install this update. Download Admiral again from the link in your approval mail.