apex-code 0.0.1-alpha.6 → 0.0.1-alpha.7

package/CHANGELOG.md

@@ -1,5 +1,21 @@
 # Apex Code changelog
 
+## [0.0.1-alpha.7] - 2026-08-21
+
+- The permission mode is now switchable from `/settings` instead of only at launch through
+  `--permission-mode`. Every mode already existed and worked; there was simply no way to
+  reach one from a running session, so `bypassPermissions` in particular was documented but
+  effectively unreachable for anyone who had already started typing. The row writes to user
+  scope (`~/.apex-code/agent/permissions.json`) and applies to the next tool call, because
+  the gate re-reads the store on every decision. Choosing `bypassPermissions` takes a
+  confirm step first, since the row is arrow-cyclable like every other setting and
+  "allow every tool call" should not be one stray keypress away. `--permission-mode`,
+  `.apex-code/permissions.json`, and `permissions.local.json` all still outrank a user-scope
+  write, so when one of them is in force the setting reports what actually applies rather
+  than appearing to save and doing nothing. Any mode other than `default` is now named in
+  the footer: `bypassPermissions` and `plan` both look like the agent misbehaving rather
+  than a mode being on. Shift+Tab still cycles the thinking level and is unchanged.
+
 ## [0.0.1-alpha.6] - 2026-08-21
 
 - Fixed skills being invisible in every sandboxed session. The OS sandbox hides the host

package/dist/core/agent-session.d.ts

@@ -20,6 +20,8 @@ import { type ContextUsage, type ExtensionCommandContextActions, type ExtensionE
 import type { CustomMessage } from "./messages.ts";
 import type { ModelRuntime } from "./model-runtime.ts";
 import { type PermissionGateOptions } from "./permissions/gate.ts";
+import { type EffectiveModeResolution } from "./permissions/startup.ts";
+import type { PermissionMode } from "./permissions/store.ts";
 import { type PromptTemplate } from "./prompt-templates.ts";
 import type { ResourceLoader } from "./resource-loader.ts";
 import type { BranchSummaryEntry, SessionEntry, SessionManager } from "./session-manager.ts";
@@ -494,6 +496,21 @@ export declare class AgentSession {
     abort(): Promise<void>;
     waitForIdle(): Promise<void>;
     private _emitModelSelect;
+    /** True when this session runs behind a permission gate at all. */
+    get hasPermissionGate(): boolean;
+    /**
+     * The mode in force right now, and which source won. `getMode` in the gate
+     * config re-reads the store on every decision, so a mode written here applies
+     * to the next tool call with no restart.
+     */
+    getPermissionMode(): Promise<EffectiveModeResolution | undefined>;
+    /**
+     * Persist a permission mode to user scope (`~/.apex-code/agent/permissions.json`).
+     * Returns the resolution that is actually in force afterwards, which is *not*
+     * necessarily `mode`: `flag`, `local`, and `project` all outrank `user`, so the
+     * caller has to be able to tell the user their choice was recorded but shadowed.
+     */
+    setPermissionMode(mode: PermissionMode): Promise<EffectiveModeResolution | undefined>;
     /**
      * Set model directly.
      * Validates that auth is configured, saves to session and settings.