dimcode 0.0.17-beta.4 → 0.0.17-beta.6

package/README.md

@@ -233,6 +233,55 @@ Inside the app, `/codexlogin` opens the same login flow.
 
 Settings and local session data are stored in `~/.dimcode/dimcode/` by default.
 
+### Active Session Runtime
+
+Dimcode also publishes a small runtime record that external tools can read for live context handoff (for example voice input tools, desktop automations, or editor helpers).
+
+By default the files live under:
+
+```text
+~/.dimcode/dimcode/runtime/
+```
+
+The main files are:
+
+- `active-session.json` - the single live runtime record for the current Dimcode context
+
+The runtime record includes fields such as:
+
+- `sessionId`
+- `cwd`
+- `title`
+- `mode`
+- `providerId`
+- `providerName`
+- `modelId`
+- `focused`
+- `visibility`
+- `updatedAt`
+
+The file is updated in-place as focus changes:
+
+- `focused` - Dimcode is the active terminal and the record contains the current chat session
+- `blurred` / `suspended` - Dimcode keeps the last session context, but it is not the active terminal
+- `inactive` - no chat session should be treated as active (for example on the home page)
+
+Current behavior:
+
+- Home screen clears the active session record so external tools do not pick up stale chat context
+- Chat screen publishes the current session and workspace
+- Terminal focus reporting is used when the terminal emulator supports xterm focus events
+- Suspend / resume (`Ctrl+Z` / `fg`) also updates visibility
+
+Dimcode also mirrors the core active context into process env for child-process integrations:
+
+- `DIMCODE_ACTIVE_SESSION_ID`
+- `DIMCODE_ACTIVE_SESSION_FOLDER`
+- `GOATCHAIN_ACTIVE_SESSION_ID`
+- `GOATCHAIN_ACTIVE_SESSION_FOLDER`
+
+These env vars are best for Dimcode-spawned tools and hooks. For cross-app integrations, prefer reading the runtime JSON files.
+
 ### Skills Directory
 
 Dimcode automatically discovers skills from both global and project-local directories: