Tools and permissions
Gaionix Coder runs workspace tools locally, uses explicit access policies, and preserves unresolved side-effect evidence before recovery.
Local workspace tools
- Read files, list directories, search text, and inspect Git status/diffs.
- Write or edit files and apply reviewed changes.
- Run shell commands with the configured access policy.
- Request approval or user input when the workflow requires it.
Tools operate locally in the selected workspace. Generated code and commands need review. Plan mode permits the runtime’s read-only tool set rather than granting edit or shell-write access.
Approval is explicit
The default access mode is ask-for-approval. VS Code and the TUI can present approval dialogs. Noninteractive run rejects approval requests. Choose --access-mode allow-all-actions only when intentionally granting unrestricted actions; it is never enabled automatically by this documentation.
Interrupted tools
A tool start with no reliable completion record can represent an uncertain side effect. Continue and Retry retain that evidence and refuse unsafe replay. Inspect the workspace and external effects before making a separate decision. Empty Queue state does not prove an earlier action never executed.
Credentials and privacy
Credentials belong in SecretStorage or a protected environment, not command arguments, prompts, normal configuration files, logs, or session data. Prompts and selected source context are sent to your chosen provider. Local sessions may contain private workspace content; treat the session directory as sensitive.
Cost controls
You choose the provider and model. Inference, summaries, continuation, and retries can be billed by the provider. The runtime preserves its central admission and compaction cost guards. Changing controls does not authorize a model switch, hidden retry, or additional provider request.