FAQ

Use this page for scope and workflow-boundary questions.

If you already have a concrete failure, start with Troubleshooting. If the basic diagnosis path is not enough, continue with Validation and runbooks.

Does Aether CLI run the server?

No. Aether CLI is the user-facing client.

When should I use Aether CLI instead of the HTTP API?

Use Aether CLI when you need local filesystem semantics.

Use the HTTP API when you need service-to-service control-plane integration.

Use both when a product manages sessions but a user edits locally.

Why does aether status not tell me everything before I start?

Because aether status is primarily about the running local runtime, not a generic preflight connectivity probe.

Use aether doctor when the runtime is not yet active or the failure mode is unclear.

Why should I separate cache roots by environment?

Because shared cache state across unrelated environments makes support and cleanup harder.

Should I put secrets in files in my mounted workspace?

Not by default. Use the public secrets surface for secrets and keep them out of ordinary working files unless your workflow explicitly requires otherwise.

Is Aether CLI the right tool for non-interactive batch workflows?

Only if you actually need a local filesystem mount.

If you only need session creation, approvals, metadata, or persistence actions, the HTTP API is usually the better surface.