@openchamber/web 2.0.4 → 2.1.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/assets/{CodeMirrorCommentWidgets-C_zL-eri.js → CodeMirrorCommentWidgets-qlshRzAf.js} +1 -1
- package/dist/assets/{DiffView-BeN2_YYF.js → DiffView-BI_YgdKl.js} +3 -3
- package/dist/assets/FilesView-B_NJFLBH.js +17 -0
- package/dist/assets/{GitView-DLDazOo1.js → GitView-BWKg6TNS.js} +4 -4
- package/dist/assets/{GuestAttachDialog-C0xe_Lyy.js → GuestAttachDialog-DO4x4vIR.js} +1 -1
- package/dist/assets/{GuestSurfacePane-BdaurnDr.js → GuestSurfacePane-4PY11vEP.js} +1 -1
- package/dist/assets/JsonTreeView-u4yx65zn.js +1 -0
- package/dist/assets/{LinearIssuesView-BryoAHow.js → LinearIssuesView-C4gGBhU8.js} +1 -1
- package/dist/assets/{MarkdownImageGallery-DfuEoaGq.js → MarkdownImageGallery-fqVRCTdC.js} +1 -1
- package/dist/assets/MarkdownRendererImpl-Cfb5fTnq.js +39 -0
- package/dist/assets/OnboardingScreen-CiTV2_OT.js +1 -0
- package/dist/assets/PatchDiff-BrjhzXDM.js +1 -0
- package/dist/assets/{PierreDiffViewer-BC950e3F.js → PierreDiffViewer-CVx2e1cx.js} +5 -5
- package/dist/assets/{PlanView-B7Xgihqk.js → PlanView-DP9DOnI-.js} +4 -4
- package/dist/assets/{PluginPane-2C71F8uF.js → PluginPane-rZvoMQSi.js} +3 -3
- package/dist/assets/SettingsView-Dp9jubRs.js +30 -0
- package/dist/assets/SettingsWindow-Dst0yiV7.js +1 -0
- package/dist/assets/{SubmoduleDiffSummary-BSA9gnIO.js → SubmoduleDiffSummary-CixkM4fI.js} +1 -1
- package/dist/assets/{ToolOutputDialog-DprkVKcj.js → ToolOutputDialog-f0cS2DIf.js} +6 -6
- package/dist/assets/ToolPartDiffPreview-CFFIAFFY.js +8 -0
- package/dist/assets/{VirtualizedFileDiff-Kp8hKJdT.js → VirtualizedFileDiff-B-U_aQwV.js} +4 -4
- package/dist/assets/{WalkthroughView-DGnTzqIU.js → WalkthroughView-C1uB3Pl3.js} +2 -2
- package/dist/assets/{appThemeRegistry-BdEHBA4s.js → appThemeRegistry-DU-UKEHq.js} +1 -1
- package/dist/assets/{commitAndPush-LwtVa2Oc.js → commitAndPush-CtWGqrtW.js} +1 -1
- package/dist/assets/{computeVirtualFileMetrics-6V1xNpO9.js → computeVirtualFileMetrics-BmhViPMt.js} +1 -1
- package/dist/assets/de-D4hpTCNY.js +10 -0
- package/dist/assets/es-Bw9m3H62.js +16 -0
- package/dist/assets/fileTreeStatus-CvPnAWSi.js +1 -0
- package/dist/assets/fr-Bhll42P0.js +14 -0
- package/dist/assets/index-Btd2mmYT.js +42 -0
- package/dist/assets/index-C-7hQnEc.css +1 -0
- package/dist/assets/{index-CmNPYddV.js → index-DwtCnbiK.js} +1 -1
- package/dist/assets/{isDiffPlainText-1bXcWCrw.js → isDiffPlainText-CPDhzF1K.js} +1 -1
- package/dist/assets/{isFilePlainText-CBAppvy1.js → isFilePlainText-n8k0lMTZ.js} +1 -1
- package/dist/assets/ja-CsHoT43d.js +16 -0
- package/dist/assets/ko-BBNdtFa4.js +16 -0
- package/dist/assets/{main-CzjTMTfW.js → main-D6rlXjug.js} +2 -2
- package/dist/assets/main-kYkr_urz.js +1000 -0
- package/dist/assets/markdownCore-CHm8ycaW.js +7 -0
- package/dist/assets/{miniChat-CP68IL8Q.js → miniChat-2JY8K3Qw.js} +2 -2
- package/dist/assets/mobile-CviaXnnU.js +2 -0
- package/dist/assets/nl-DszyktfH.js +16 -0
- package/dist/assets/openSessionFromRoute-BIlcJIf3.js +1 -0
- package/dist/assets/{web-components-ngpHPEDU.js → parseDiffFromFile-DeZzEah8.js} +5 -5
- package/dist/assets/{patchFileDiff-pqRSHLHI.js → patchFileDiff-BnEHIdM2.js} +2 -2
- package/dist/assets/pl-Bk9_mUXc.js +16 -0
- package/dist/assets/pt-BR-BIXmm3Gw.js +16 -0
- package/dist/assets/{renderElectronMiniChatApp-DKIilR7N.js → renderElectronMiniChatApp-DvUphkjj.js} +2 -2
- package/dist/assets/renderMobileApp-Cdc49X8Y.js +25 -0
- package/dist/assets/runtimeEndpointReset-Cu6RUve4.js +56 -0
- package/dist/assets/shikiHighlight-CcVzlYit.js +1 -0
- package/dist/assets/space-apply-CgJ5JYPK.js +1 -0
- package/dist/assets/space-close-C1tL-_0t.js +1 -0
- package/dist/assets/{textMateThemeFromAppTheme-BSUFChBY.js → textMateThemeFromAppTheme-CAOCeVjl.js} +1 -1
- package/dist/assets/tr-C_13w7CX.js +7 -0
- package/dist/assets/uk-BZTsG-q_.js +16 -0
- package/dist/assets/{useAppFontEffects-Dsl_sLrj.js → useAppFontEffects-CeMgbeVa.js} +185 -177
- package/dist/assets/{useInlineCommentController-d5vntsQ_.js → useInlineCommentController-U97JJifS.js} +2 -2
- package/dist/assets/useRootScrollLock-DMBY2aTT.js +2 -0
- package/dist/assets/{vendor-base-ui-DnNniUWp.js → vendor-base-ui-DWgyZK2k.js} +1 -1
- package/dist/assets/vendor-codemirror-autocomplete-DetzHhtC.js +1 -0
- package/dist/assets/{vendor-codemirror-commands-B7H_j0iU.js → vendor-codemirror-commands-ConqfjLn.js} +1 -1
- package/dist/assets/{vendor-codemirror-lang-angular-DEPs2M5t.js → vendor-codemirror-lang-angular-Dbpx8qe-.js} +1 -1
- package/dist/assets/{vendor-codemirror-lang-cpp-DhkseaMo.js → vendor-codemirror-lang-cpp-TRtQWrpl.js} +1 -1
- package/dist/assets/{vendor-codemirror-lang-css-O0cZX78y.js → vendor-codemirror-lang-css-DY4CGDG2.js} +1 -1
- package/dist/assets/{vendor-codemirror-lang-go-fMdQYcON.js → vendor-codemirror-lang-go-CLKXh6B8.js} +1 -1
- package/dist/assets/{vendor-codemirror-lang-html-CfgK872x.js → vendor-codemirror-lang-html-CQnNjmg9.js} +1 -1
- package/dist/assets/{vendor-codemirror-lang-java-CQj4S3zl.js → vendor-codemirror-lang-java-CokZKqls.js} +1 -1
- package/dist/assets/{vendor-codemirror-lang-javascript-Cc2ZYbgX.js → vendor-codemirror-lang-javascript-Kgp6fZRE.js} +1 -1
- package/dist/assets/{vendor-codemirror-lang-jinja-BmZZv8g-.js → vendor-codemirror-lang-jinja-DZchyrN1.js} +1 -1
- package/dist/assets/{vendor-codemirror-lang-json-CMBS2tG9.js → vendor-codemirror-lang-json-CkdBRvqj.js} +1 -1
- package/dist/assets/{vendor-codemirror-lang-less-C6Eo8hVS.js → vendor-codemirror-lang-less-_k-GKz0A.js} +1 -1
- package/dist/assets/{vendor-codemirror-lang-liquid-DSTR47-H.js → vendor-codemirror-lang-liquid-DuHUMKoh.js} +1 -1
- package/dist/assets/{vendor-codemirror-lang-markdown-BPGOH9ye.js → vendor-codemirror-lang-markdown-CdG1RXm1.js} +1 -1
- package/dist/assets/{vendor-codemirror-lang-php-DD9udfPH.js → vendor-codemirror-lang-php-Ca15KQSA.js} +1 -1
- package/dist/assets/{vendor-codemirror-lang-python-HahnQaAS.js → vendor-codemirror-lang-python-B4MRHRva.js} +1 -1
- package/dist/assets/{vendor-codemirror-lang-rust-nLTovbjv.js → vendor-codemirror-lang-rust-8fLJdxQA.js} +1 -1
- package/dist/assets/{vendor-codemirror-lang-sass-pL2Yc72v.js → vendor-codemirror-lang-sass-CASr_yQ1.js} +1 -1
- package/dist/assets/{vendor-codemirror-lang-sql-BVBnan19.js → vendor-codemirror-lang-sql-Dc4ER-re.js} +1 -1
- package/dist/assets/{vendor-codemirror-lang-vue-BqGzJVm1.js → vendor-codemirror-lang-vue-fu2BqdK2.js} +1 -1
- package/dist/assets/{vendor-codemirror-lang-wast-B0_m5DqU.js → vendor-codemirror-lang-wast-BkCOgSpV.js} +1 -1
- package/dist/assets/{vendor-codemirror-lang-xml-Dj3voadT.js → vendor-codemirror-lang-xml-7e-kPepH.js} +1 -1
- package/dist/assets/{vendor-codemirror-lang-yaml-yu-9Z5u7.js → vendor-codemirror-lang-yaml-Cq3p_9DI.js} +1 -1
- package/dist/assets/vendor-codemirror-language-CZcLdzDM.js +3 -0
- package/dist/assets/{vendor-codemirror-language-data-B1EetJur.js → vendor-codemirror-language-data-B8HKnqZy.js} +2 -2
- package/dist/assets/vendor-codemirror-search-BZNojiZO.js +2 -0
- package/dist/assets/{vendor-codemirror-state-C9awkmn-.js → vendor-codemirror-state--21VQleR.js} +1 -1
- package/dist/assets/vendor-codemirror-view-8PpN-8l4.js +4 -0
- package/dist/assets/vendor-opencode-client-Byb4ZSqI.js +12 -0
- package/dist/assets/vendor-remend-DcBOpbSu.js +24 -0
- package/dist/assets/{vendor-replit-codemirror-vim-B2DJlAhT.js → vendor-replit-codemirror-vim-EX7OnecQ.js} +1 -1
- package/dist/assets/zh-CN-C62wm2Tg.js +16 -0
- package/dist/assets/zh-TW-BgGTiQA6.js +16 -0
- package/dist/index.html +4 -4
- package/dist/mini-chat.html +4 -4
- package/dist/mobile.html +4 -4
- package/package.json +4 -4
- package/server/index.js +58 -1
- package/server/lib/browser-control/DOCUMENTATION.md +8 -1
- package/server/lib/dev-tunnel/DOCUMENTATION.md +6 -0
- package/server/lib/dev-tunnel/runtime.js +94 -38
- package/server/lib/dev-tunnel/tunnel.test.js +16 -2
- package/server/lib/dictation/DOCUMENTATION.md +23 -10
- package/server/lib/dictation/audio.js +28 -0
- package/server/lib/dictation/local/sherpa-recognizer.js +33 -7
- package/server/lib/dictation/local/sherpa-recognizer.test.js +94 -0
- package/server/lib/dictation/local/worker-client.js +28 -10
- package/server/lib/dictation/local/worker-process.js +25 -1
- package/server/lib/dictation/stream-manager.js +160 -53
- package/server/lib/dictation/stream-manager.test.js +108 -7
- package/server/lib/enterprise-mode.d.ts +2 -0
- package/server/lib/enterprise-mode.js +84 -9
- package/server/lib/enterprise-mode.test.js +115 -0
- package/server/lib/fs/DOCUMENTATION.md +3 -2
- package/server/lib/fs/routes.js +28 -1
- package/server/lib/fs/routes.test.js +31 -5
- package/server/lib/git/DOCUMENTATION.md +1 -1
- package/server/lib/git/service.js +61 -2
- package/server/lib/git/service.test.js +141 -0
- package/server/lib/github/DOCUMENTATION.md +18 -0
- package/server/lib/github/checks-summary.js +76 -0
- package/server/lib/github/pr-summaries.js +282 -0
- package/server/lib/github/pr-summaries.test.js +209 -0
- package/server/lib/github/routes.js +42 -77
- package/server/lib/github/routes.test.js +77 -0
- package/server/lib/inherited-env.js +51 -0
- package/server/lib/inherited-env.test.js +59 -0
- package/server/lib/message-search/DOCUMENTATION.md +83 -0
- package/server/lib/message-search/indexer.js +336 -0
- package/server/lib/message-search/indexer.test.js +341 -0
- package/server/lib/message-search/routes.js +92 -0
- package/server/lib/message-search/runtime.js +234 -0
- package/server/lib/message-search/runtime.test.js +108 -0
- package/server/lib/message-search/sqlite.js +74 -0
- package/server/lib/message-search/store.js +289 -0
- package/server/lib/openchamber-control/DOCUMENTATION.md +6 -1
- package/server/lib/openchamber-control/actions.js +1 -1
- package/server/lib/openchamber-control/service.js +21 -2
- package/server/lib/openchamber-control/service.test.js +50 -0
- package/server/lib/openchamber-sessions/routes.js +15 -0
- package/server/lib/openchamber-sessions/routes.test.js +31 -0
- package/server/lib/opencode/DOCUMENTATION.md +43 -38
- package/server/lib/opencode/auth.d.ts +24 -0
- package/server/lib/opencode/auth.js +130 -66
- package/server/lib/opencode/auth.test.js +114 -70
- package/server/lib/opencode/compatibility.js +4 -3
- package/server/lib/opencode/compatibility.test.js +10 -10
- package/server/lib/opencode/feature-routes-runtime.js +3 -0
- package/server/lib/opencode/lifecycle.js +21 -12
- package/server/lib/opencode/lifecycle.test.js +38 -5
- package/server/lib/opencode/provider-source-route.test.js +55 -2
- package/server/lib/opencode/routes.js +17 -4
- package/server/lib/opencode/settings-helpers.js +6 -0
- package/server/lib/opencode/settings-helpers.test.js +1 -1
- package/server/lib/opencode/settings-registry.json +16 -0
- package/server/lib/opencode/settings-runtime.js +9 -0
- package/server/lib/opencode/shutdown-runtime.js +2 -0
- package/server/lib/opencode/v1-migration-topup.js +13 -3
- package/server/lib/opencode/v2-install.test.js +13 -13
- package/server/lib/quota/DOCUMENTATION.md +11 -5
- package/server/lib/quota/providers/claude/auth.js +19 -6
- package/server/lib/quota/providers/claude/auth.test.js +22 -9
- package/server/lib/quota/providers/claude/index.js +3 -3
- package/server/lib/quota/providers/claude/index.test.js +3 -2
- package/server/lib/quota/providers/cline-pass.js +4 -4
- package/server/lib/quota/providers/codex.js +3 -4
- package/server/lib/quota/providers/codex.test.js +1 -1
- package/server/lib/quota/providers/copilot.js +4 -5
- package/server/lib/quota/providers/copilot.test.js +1 -1
- package/server/lib/quota/providers/deepseek.js +3 -4
- package/server/lib/quota/providers/deepseek.test.js +1 -1
- package/server/lib/quota/providers/google/auth.js +1 -3
- package/server/lib/quota/providers/google/index.js +3 -2
- package/server/lib/quota/providers/hyper.js +4 -4
- package/server/lib/quota/providers/index.js +9 -2
- package/server/lib/quota/providers/index.test.js +5 -3
- package/server/lib/quota/providers/kimi.js +16 -11
- package/server/lib/quota/providers/kimi.test.js +81 -38
- package/server/lib/quota/providers/minimax-shared.js +3 -4
- package/server/lib/quota/providers/nanogpt.js +3 -4
- package/server/lib/quota/providers/neuralwatt.js +3 -4
- package/server/lib/quota/providers/neuralwatt.test.js +1 -1
- package/server/lib/quota/providers/openai.js +2 -8
- package/server/lib/quota/providers/opencode-go.js +5 -5
- package/server/lib/quota/providers/opencode-go.test.js +1 -1
- package/server/lib/quota/providers/openrouter.js +30 -6
- package/server/lib/quota/providers/openrouter.test.js +122 -1
- package/server/lib/quota/providers/wafer.js +3 -4
- package/server/lib/quota/providers/xai.js +12 -12
- package/server/lib/quota/providers/zai.js +3 -4
- package/server/lib/quota/providers/zai.test.js +1 -1
- package/server/lib/quota/providers/zhipuai-coding-plan.js +5 -6
- package/server/lib/quota/providers/zhipuai-coding-plan.test.js +1 -1
- package/server/lib/quota/routes.js +1 -1
- package/server/lib/routing/DOCUMENTATION.md +4 -0
- package/server/lib/routing/runtime.js +45 -4
- package/server/lib/routing/runtime.test.js +35 -6
- package/server/lib/scheduled-tasks/DOCUMENTATION.md +27 -0
- package/server/lib/scheduled-tasks/chats-scope.js +50 -0
- package/server/lib/scheduled-tasks/runtime.js +57 -23
- package/server/lib/scheduled-tasks/runtime.test.js +103 -1
- package/server/lib/scheduled-tasks/service.js +37 -29
- package/server/lib/scheduled-tasks/service.test.js +39 -0
- package/server/lib/spaces/DOCUMENTATION.md +54 -9
- package/server/lib/spaces/host.js +24 -3
- package/server/lib/spaces/journey.js +111 -11
- package/server/lib/spaces/journey.test.js +189 -8
- package/server/lib/spaces/places/docker-disk.js +151 -0
- package/server/lib/spaces/places/docker-disk.test.js +167 -0
- package/server/lib/spaces/places/docker-tools.js +11 -1
- package/server/lib/spaces/places/docker.js +4 -2
- package/server/lib/spaces/places/fake-docker.js +36 -2
- package/server/lib/spaces/routes.js +21 -4
- package/server/lib/spaces/routes.test.js +6 -2
- package/server/lib/spaces/space-archive.js +275 -0
- package/server/lib/spaces/space-archive.test.js +194 -0
- package/server/lib/spaces/space-opencode.js +139 -6
- package/server/lib/spaces/space-opencode.test.js +82 -1
- package/server/lib/spaces/space-records.js +3 -0
- package/server/lib/spaces/space-setup.js +10 -5
- package/server/lib/spaces/space-setup.test.js +8 -2
- package/server/lib/terminal/DOCUMENTATION.md +1 -0
- package/server/lib/terminal/runtime.js +6 -1
- package/server/lib/terminal/runtime.test.js +19 -0
- package/server/lib/tts/routes.js +2 -2
- package/server/lib/tts/service.js +8 -8
- package/dist/assets/FilesView-CN34wm_N.js +0 -17
- package/dist/assets/JsonTreeView-B1Xq-k2t.js +0 -1
- package/dist/assets/MarkdownRendererImpl-B_ZcWOvX.js +0 -12
- package/dist/assets/OnboardingScreen-C22bGmnP.js +0 -1
- package/dist/assets/PatchDiff-0xd6UeFB.js +0 -1
- package/dist/assets/SettingsView-m_zoFiaT.js +0 -30
- package/dist/assets/SettingsWindow-CofS020b.js +0 -1
- package/dist/assets/ToolPartDiffPreview-Dq0go_fX.js +0 -8
- package/dist/assets/de-DlgBHUAI.js +0 -10
- package/dist/assets/es-BC8G41U8.js +0 -16
- package/dist/assets/fr-I0z3vVjy.js +0 -14
- package/dist/assets/index-CgR5rJq_.js +0 -41
- package/dist/assets/index-adyy_sEk.css +0 -1
- package/dist/assets/ja-BIElEsY8.js +0 -16
- package/dist/assets/ko-DRnnHetA.js +0 -16
- package/dist/assets/main-DVX34beR.js +0 -886
- package/dist/assets/markdownCore-Cxbkn5NR.js +0 -7
- package/dist/assets/mobile-BrlBrNfZ.js +0 -2
- package/dist/assets/nl-DzUV-kwp.js +0 -16
- package/dist/assets/pl-Bb-cb7k7.js +0 -16
- package/dist/assets/pt-BR-CyIWrTcE.js +0 -16
- package/dist/assets/renderMobileApp-B0z6-x58.js +0 -25
- package/dist/assets/runtimeEndpointReset-uu1DBwLL.js +0 -52
- package/dist/assets/scheduledTasksApi-BuzWT445.js +0 -1
- package/dist/assets/shikiHighlight-BWGrY5YU.js +0 -1
- package/dist/assets/tr-DXEDSoYO.js +0 -7
- package/dist/assets/uk-C8hN--q_.js +0 -16
- package/dist/assets/useRootScrollLock-2rd5Y6gR.js +0 -2
- package/dist/assets/vendor-codemirror-autocomplete-DzPz9Wgq.js +0 -1
- package/dist/assets/vendor-codemirror-language-BgPj_McA.js +0 -3
- package/dist/assets/vendor-codemirror-search-BmS-GmcX.js +0 -2
- package/dist/assets/vendor-codemirror-view-CiLROUVV.js +0 -4
- package/dist/assets/vendor-opencode-client-DSZl7jSi.js +0 -12
- package/dist/assets/vendor-remend-BWYYytN3.js +0 -22
- package/dist/assets/zh-CN-CtzXdjMZ.js +0 -16
- package/dist/assets/zh-TW-Ds0CADSz.js +0 -16
- package/server/lib/opencode/credential-db.js +0 -144
- package/server/lib/opencode/credential-db.test.js +0 -104
|
@@ -25,10 +25,12 @@ Creating, finding, stopping, starting, and removing isolated spaces on a place,
|
|
|
25
25
|
- `host.js`: `createSpacesHost({ dataDir, dockerPath, gitPath, hostEnvironment, listProjectDirectories })`. What `server/index.js` builds when the switch is on: the owner id, the Docker place, the registry, the manager, the dispatcher, the gatekeeper channel, code in and code out on one host git, the records and the journey, with the hooks the rest of the server takes from it.
|
|
26
26
|
- `journey.js`: `createSpaceJourney({ manager, place, gatekeeper, codeIn, codeOut, records, serverInside, restartOpenCodeInside, listProjectDirectories, announce, onSpacesChanged })`. The journey of a space as the host drives it, written once on top of those: create in the background with progress, list with state and what is broken, start with the network said again, stop, the two restarts of the repair, remove with the refs and the record, stop all for the switch, the journal, the apply preview and the apply. See "The journey".
|
|
27
27
|
- `routes.js`: `registerSpaceRoutes(app, { getJourney, getPlaces, readSwitch, setSwitch })`, the HTTP of the journey under `/api/openchamber/spaces`, which translates and nothing else; and `createSwitchController({ getHost, setHost, buildHost, startHost, persist })`, the switch as `index.js` runs it, one change at a time.
|
|
28
|
+
- `space-archive.js`: `createSpaceArchive({ dataDir, hostOpenCode })`. Since 5e-2, the chats of a deleted space: saved into the host's OpenCode before the space goes, listed for the Archive page, and kept read-only by `guard`. See "Chat archive" under "The journey".
|
|
28
29
|
- `space-records.js`: `createSpaceRecords({ dataDir })`. What the host remembers about a space beside the labels: the network choice, the repository, the space path, the base of the history and whether the history arrived. One file per space under `spaces/records/`, no secret in it.
|
|
29
30
|
- `places/registry.js`: place registry, same pattern as the tunnel provider registry. Sealed after boot.
|
|
30
31
|
- `places/docker.js`: the local Docker place. `createDockerPlace({ runCommand, dockerPath, owner, toolsSource, wait, now })`. `wait` is the pause used by rollbacks and by the readiness wait. `now` stamps the tools labels and is the clock of the readiness wait. Both are injectable so tests do not sleep.
|
|
31
32
|
- `places/docker-tools.js`: the tools volume of the Docker place. Ensure, fill, fill rollback, pruning.
|
|
33
|
+
- `places/docker-disk.js`: since 5e-4, the disk the Docker place's spaces take and its clean-up. See "Places page" under "The journey".
|
|
32
34
|
- `places/docker-engine.js`: how both of them call the docker CLI. Run, inspect, find by label, remove.
|
|
33
35
|
- `hardening.js`: the `docker create` argv for a space and for its gatekeeper, the argv for both networks and for the three one-shot containers, and the pure checkers that compare `docker inspect` output with them.
|
|
34
36
|
- `labels.js`: label keys, resource names, space ids, tools keys, label parsing.
|
|
@@ -62,6 +64,8 @@ Stage 3a added three more and changed none. The argv from `execArgv` runs a comm
|
|
|
62
64
|
|
|
63
65
|
A new place is done when `runPlaceContractSuite` and `runEscapeSuite` pass against it.
|
|
64
66
|
|
|
67
|
+
Since 5e-4 the Docker place also has `readDisk()` and `cleanUpDisk()`, for the places page in Settings. They are not in the contract and not in the registry's required list: what a place keeps on disk, and what it can make again, is its own. The journey calls them on its one place; a later place brings its own or the page has nothing to say for it.
|
|
68
|
+
|
|
65
69
|
## Labels
|
|
66
70
|
|
|
67
71
|
Labels are the only record of a space. Every container, network, and volume carries all of them. Since stage 2 that includes the gatekeeper container and the outer network.
|
|
@@ -503,7 +507,7 @@ The merged list and the rules for it live in `space-sessions.js`, pure; `host.js
|
|
|
503
507
|
- A space's list and events are read whenever the switch is on, one `docker ps` every fifteen seconds and one event connection per space, whether or not a client is looking. That is the cost of live status for sessions nobody has opened yet.
|
|
504
508
|
- The relay path of the new sockets, a phone reaching a space's terminal through the private relay, has not been exercised on a device: the three allowlists carry the shapes and the unit tests prove each list, and nothing more.
|
|
505
509
|
- A space's event connection that is still being made cannot be aborted: the host's close waits for the server inside to answer or the stream to die. One request per space at most.
|
|
506
|
-
- The mark names a space's project only while that project is registered on this host under the very path the space was made for: the label holds a hash of that path, and the host compares it with its registered projects' paths as they are. A project removed or re-added under another spelling leaves the space with no project, and the sidebar shows nothing of it
|
|
510
|
+
- The mark names a space's project only while that project is registered on this host under the very path the space was made for: the label holds a hash of that path, and the host compares it with its registered projects' paths as they are. A project removed or re-added under another spelling leaves the space with no project, and the sidebar shows nothing of it; since 5e-3 Settings lists it among the spaces without a project, see "Spaces page" under "The journey".
|
|
507
511
|
- The empty-cwd terminal listing that the sidebar's action badges read is the host's alone; a space's terminals are listed per directory, through the prefix, when the terminal panel of that directory asks.
|
|
508
512
|
|
|
509
513
|
## The journey
|
|
@@ -518,20 +522,23 @@ All under `/api/openchamber/spaces`, a namespace of the host's beside `/api/open
|
|
|
518
522
|
|---|---|
|
|
519
523
|
| `GET /switch`, `PUT /switch` | The switch, see "The switch" above. |
|
|
520
524
|
| `GET /places` | Every place asked `check()` now, because the user is looking: `{ places: [{ id, available, version, os, arch, hostIsolation }] }`, or `{ id, available: false, code, message }`. |
|
|
521
|
-
| `GET /` | `{ spaces }`: the place's list with what the host remembers about each, the creations under way in their place, and the failed ones after it. |
|
|
525
|
+
| `GET /` | `{ spaces }`: the place's list with what the host remembers about each, the creations under way in their place, and the failed ones after it. Since 5e-3 each names `projectFolder`, `{ path, found }`: the folder it was made for, from the record, and whether that is a folder on the host now, `found` null while a creation is under way. |
|
|
522
526
|
| `POST /` | `{ projectDirectory, name, start, network, setupCommands }`. Answers 202 at once with the entry the list carries; the steps follow as events. |
|
|
523
527
|
| `POST /<id>/start`, `POST /<id>/stop` | The place's start and stop; start says the network again. Answers the listed entry, start with `networkRestored`. |
|
|
524
528
|
| `POST /<id>/restart-opencode` | Since 5d-2: asks the server inside a running space to restart its OpenCode, and answers the listed entry once it is ready again. See "Repair". |
|
|
525
529
|
| `POST /<id>/restart` | Since 5d-2: restarts the container of a running space with a fresh token, then says the network and the grants again as a start does. Answers as start does. See "Repair". |
|
|
526
|
-
| `DELETE /<id>` |
|
|
530
|
+
| `DELETE /<id>` | Saves the space's chats to the archive, then removes the containers, networks and volumes, the service refs in the user's repository and the record; forgets a failed creation. `{ id, removed, refsRemoved, failures, chats }`. 409 `chats_not_saved` when the chats cannot all be saved, and `?unsavedChats=delete` deletes anyway. See "Chat archive". |
|
|
531
|
+
| `GET /places/<place>/disk` | Since 5e-4: `{ imageBytes, toolsBytes, spacesBytes, freeBytes, freesImage }`, the disk the place's spaces take and what a clean-up would free now. See "Places page". |
|
|
532
|
+
| `POST /places/<place>/clean-up` | Since 5e-4: removes what OpenChamber can make again; `{ freedBytes, kept: [{ kind, reason }], disk }`. 409 `space_preparing` while a space is being made. See "Places page". |
|
|
533
|
+
| `GET /archives` | Since 5e-2: `{ archives: [{ spaceId, name, projectDirectory, directory, archivedAt }] }`, which directory holds which deleted space's chats. Reachable with the switch off too, see "Chat archive". |
|
|
527
534
|
| `POST /<id>/setup` | Since 5d-4: `{ commands }`. Runs the project's setup commands again in a running space; answers the listed entry once the run began. See "Setup commands". |
|
|
528
535
|
| `GET /<id>/setup` | Since 5d-4: `{ setup, output }`, the setup as the list carries it and the end of the failed command's output, or null. |
|
|
529
536
|
| `GET /idle-stop`, `PUT /idle-stop` | Since 5d-3: the idle stop setting, `{ enabled, hours }`, kept in the host's settings and told to every running space. See "Idle stop". |
|
|
530
537
|
| `POST /<id>/grants` | Since 5b: `{ kind: 'model', provider, upstream, secret: { kind: 'typed', value } \| { kind: 'env', name } }` or `{ kind: 'domain', upstream }`. Answers `{ grant }`, the grant as the list carries it, with its window URL and never a value. See "Grants". |
|
|
531
538
|
| `POST /<id>/network/domains` | Since 5d: `{ domain }`. Adds a name to a running space's allowlist, live, then to the record, so every later start says it again. Answers `{ network }`. See "Grants". |
|
|
532
539
|
| `GET /<id>/journal` | The gatekeeper's journal, `{ records, dropped, since }`; 409 `space_not_running` for a stopped space, because the journal is gone with it. |
|
|
533
|
-
| `GET /<id>/apply` | Brings the work out and describes what an apply would do, writing nothing of the user's: `bringCodeOut`'s answer and `describeApplyState`'s in one object. |
|
|
534
|
-
| `POST /<id>/apply` | `{ as: 'branch', branch, removeAfterwards }` or `{ as: 'changes', removeAfterwards }`. Brings the work out once more and applies it; what is applied is what this call fetched. `{ brought, applied, removal }`, `removal` null unless the space was removed. |
|
|
540
|
+
| `GET /<id>/apply` | Brings the work out and describes what an apply would do, writing nothing of the user's: `bringCodeOut`'s answer and `describeApplyState`'s in one object. A running space only: a stopped one answers `space_not_running` before anything reaches into it, so the apply dialog can offer Start. |
|
|
541
|
+
| `POST /<id>/apply` | `{ as: 'branch', branch, removeAfterwards }` or `{ as: 'changes', removeAfterwards }`. Brings the work out once more and applies it; what is applied is what this call fetched. `{ brought, applied, removal, kept }`, `removal` null unless the space was removed, and `kept` the `chats_not_saved` failure when `removeAfterwards` left the space because its chats could not be saved. A running space only, as the preview. Since 5e-1 the apply dialog of the UI calls both, see "Apply dialog". |
|
|
535
542
|
|
|
536
543
|
A failure is one JSON answer, `{ code, message, details }`, with the status `routes.js` gives that code: 400 for a bad request, 404 for a space or place that does not exist, 409 for a refusal that the user resolves, `space_preparing`, `space_not_running`, `branch_exists`, every refusal of an apply and `place_cannot_restrict_network` among them, and 502 for a failure of the place or the space; anything that is not a `SpaceError` is 500 with `space_journey_failed`. No stack travels.
|
|
537
544
|
|
|
@@ -555,6 +562,39 @@ DESIGN.md, user journey step 8 and decision 10; built in 5d-2. The group of a sp
|
|
|
555
562
|
- **What is broken.** The list carries `damage` for a damaged space: `gatekeeper_gone` when its gatekeeper container no longer exists, and `repairable` for everything else, a gatekeeper that stopped while the space runs among them, which the next start brings back. The place's list names the gatekeeper as missing in both cases, so for such a space alone the journey asks the place's `verify`, whose `gatekeeper_missing` violation tells them apart; a `verify` that cannot answer leaves it `repairable`, so the user is offered a restart and not told on a guess that the space is lost. A gatekeeper that is gone is never made again (see "Lifecycle"), so the screen says in plain words that the space has to be deleted and made again, and a start of it answers `gatekeeper_missing` with status 409.
|
|
556
563
|
- A state that is not listed but seen: a running space whose server did not answer the host's last read of its sessions is "not answering" on the screen, from the session list's mark, and the screen offers the restart of the container.
|
|
557
564
|
|
|
565
|
+
### Apply dialog
|
|
566
|
+
|
|
567
|
+
DESIGN.md, decisions 7 and 8, journey step 6; built in 5e-1, UI only on top of the two routes above. The maintainer's calls of 2026-09-29: "Apply changes…" is the first item of the group's menu and of the phone's sheet, and a button in the desktop session header; the branch is chosen by default, named after the space; "Delete the space afterwards" is on, and off by default when a session of the space is working as the dialog opens, which the dialog says; a refusal that closes the way of uncommitted changes (`changes_do_not_apply`, `changes_route_closed`, `changes_blocked_by_link`, `changes_undecided`, `changes_partly_applied`) turns the dialog to the branch and leaves the next press to the user; the other refusals keep the choice. The user is told once, at the refusal, so the cases whose next step differs keep a sentence of their own: part of the last apply thrown away, with the files still there, which stand in the way of merging the branch; a file git ignores that was there before; a file a filter such as Git LFS keeps; and a read-back that ran out of time, which a preview's `newPathsUndecided` also announces under the choice. A stopped space whose gatekeeper is gone offers no apply, because it never starts again. The dialog shows the counts of the preview, never a file list, and the paths of `nestedRepositories` and `unmerged`; the diff is the space's own git panel. The delete confirmation offers "Apply first". Discard is the delete, with no action of its own. Paths from the space are shown as text only.
|
|
568
|
+
|
|
569
|
+
### Chat archive
|
|
570
|
+
|
|
571
|
+
DESIGN.md, decision 9 and journey step 7; built in 5e-2, `space-archive.js`, the export in `space-opencode.js`. The maintainer's calls of 2026-09-30: the chats of a deleted space go to the Archive page, one group per space under its name, with no Restore; the chat says the space was deleted and is read-only; the page's own bins delete a chat or the whole group; when the chats cannot be saved the space is not deleted and the confirmation asks again with "Delete anyway"; at most 1000 chats of 256 MB each.
|
|
572
|
+
|
|
573
|
+
- **Out.** Before `DELETE /<id>`, and before the removal of an apply with `removeAfterwards`, the journey starts a stopped space, lists its sessions over the dispatcher's `requestInside` and asks the server inside for each one's `GET /api/experimental/session/<id>/export`, read up to 256 MB and within five minutes, however slowly the space sends; all of them within thirty minutes, the rest counted as not saved, so a space cannot hold its own delete. A space started only for this, whose chats could not be saved, is stopped again; its gatekeeper allows nothing meanwhile, because the network is not said again for a delete. Each is written to a folder of the archive first, so memory holds one chat at a time and a refusal leaves the host's OpenCode untouched. The export holds only settled messages: a turn still running when the space goes is not in it.
|
|
574
|
+
- **What the host takes.** The record of each chat is rebuilt from its id, title, times, cost, tokens and outcome; its permissions, metadata, agent, model and revert are dropped, because an archive is read and never run. It gets one permission rule instead, `{ action: '*', resource: '*', effect: 'deny' }`: OpenCode takes the last rule that matches and a session's rules come after the agent's, so no tool runs in an archived chat whoever starts a turn there. That matters because the chat lives in the host's OpenCode, which VS Code, the OpenCode CLI and OpenChamber's own control route reach without the guard below. Measured on 2026-09-30 with OpenCode 2.0.16 and a real model: asked to run `touch` through its shell tool, the agent in an archived chat answered that no shell tool was available and no file appeared; the same request in an ordinary chat of the same directory made the file. Permission evaluation is the same in 2.0.16 and 2.0.20. `parentID` is kept only when the parent is in the same archive, so a space cannot hang a chat under a session of the host's. The messages go whole to the host's OpenCode, whose import checks each against its schema.
|
|
575
|
+
- **In.** `POST /api/experimental/session/import` of the host's OpenCode, through `@opencode/client`, parents first, at `<data dir>/spaces/archive/<space id>/`, with `time.archived` set, so the chat shows on the Archive page and in no project's list. It keeps its id: a chat whose id the host already has is refused with 409 and counts as not saved, unless an earlier delete of the same space saved it there. That happens when a delete saved the chats and then could not remove the space: the next delete keeps the chats saved before, adds the new ones, and on a refusal takes back only what it added, so a chat once archived never leaves the archive's file or the guard. `<data dir>/spaces/archive/<space id>.json` names the space, its project and its chats.
|
|
576
|
+
- **All or nothing.** A chat that cannot be listed, taken out or imported, one over 256 MB, or more than 1000 chats, fails the delete with `chats_not_saved` before anything is deleted, with the titles of the chats too large in `details.tooLarge` and the others counted in `details.failed`; chats already imported are deleted from the host's OpenCode again. With `?unsavedChats=delete` what can be saved is saved and the space goes. For an apply with `removeAfterwards` the work stays applied and the space stays, `kept` says why.
|
|
577
|
+
- **Read-only.** An imported chat is a live session of the host's OpenCode: measured on 2026-09-30, a shell sent to one ran on the host. So besides the rule above, `guard`, mounted before every route that acts on a session, refuses with 409 `archived_chat_read_only` any request other than a read that names an archived chat in `/api/session/<id>`, `/api/experimental/session/<id>/...`, `/api/openchamber/sessions/<id>/...`, `/api/message-queue/sessions/<id>`, `/api/goals/objective/<id>` or `/api/permission-auto-accept/sessions/<id>`; `DELETE /api/session/<id>` passes, which is how the user deletes one. The id is compared decoded, as the route behind it decodes it. It reads the archive's files at start and runs nothing, so it and `GET /archives` exist with the switch on or off: turning the feature off does not make an archived chat runnable.
|
|
578
|
+
- **Not a boundary against the agent.** By the time a chat is archived the space is gone. What a space wrote into its chats is shown as any chat of the space was shown while it lived.
|
|
579
|
+
|
|
580
|
+
### Spaces page
|
|
581
|
+
|
|
582
|
+
DESIGN.md, journey step 9 and decision 12; built in 5e-3, UI only on top of `GET /`. The maintainer's calls of 2026-09-30:
|
|
583
|
+
|
|
584
|
+
- "Manage isolated spaces" in the project menu, under "Manage worktrees", opens the project's spaces page, laid out as the worktrees page: "New isolated space" on top, which opens the create dialog of the new-session picker, and a row per space with its name, its network, the status line of its group in the sidebar, the key of the grant dialog and the group's menu. Spaces of the Archive page are not listed. The phone has it as a section of its project editor, under the worktrees, with no create button.
|
|
585
|
+
- A space whose project is no longer registered is listed in Settings, on the "Isolated spaces" page since 5e-4, as a space without a project, only when there is one, with the folder it was made for; one whose container is gone is listed under its place instead, see "Places page"; "Apply changes…" is not offered when `projectFolder.found` is false, because the work has nowhere to go. Deleting such a space counts as done even though its service refs cannot be removed: they went with the folder, wherever it is now, and the host logs that they stay there.
|
|
586
|
+
- Closing a project stops its running spaces, found by the folder they were made for, except one where a session is busy, because closing is one click with no confirmation; a notice says how many stopped. Files are kept, as with any stop, and the idle stop takes the rest. The client that closes the project does this, `lib/spaces/space-close.ts` in the UI, reading which sessions are busy from its own live status; a project removed any other way, by editing the settings file, stops nothing.
|
|
587
|
+
|
|
588
|
+
### Places page
|
|
589
|
+
|
|
590
|
+
DESIGN.md, journey step 9 and decision 12; built in 5e-4, `places/docker-disk.js` behind the two routes above. The maintainer's calls of 2026-09-30: Settings has a page of its own, "Isolated spaces" in the Workspace group, which holds the switch, the idle stop, the places and the spaces without a project, and the phone lists it among its Settings pages; a place shows its Docker version, how many spaces run and stand stopped, the disk, the spaces whose container is gone with their "Delete", and "Clean up…" with one confirmation that says what it frees and, when the image goes, that it downloads again; a place that cannot be reached says what to do and lists the spaces this window last saw, never a count of zero, and nothing polls.
|
|
591
|
+
|
|
592
|
+
- **What it measures.** `docker system df --verbose` for the volumes, read by name for this owner's tools volumes and space volumes, which are found by label and checked again on the inspect result; `docker image inspect` for the pinned image. Docker prints volume sizes rounded to three digits in decimal units, so the page's numbers are Docker's, as `docker system df` shows them. `freeBytes` counts the old tools volumes no container mounts and the image when no container at all, anyone's, was made from it.
|
|
593
|
+
- **What a clean-up removes.** This owner's tools volumes other than the current one, this owner's tools one-shot containers, and the space image by its pinned reference. Each goes without force, one by one. Docker refuses a volume a container mounts, a stopped one included, an image any container was made from, and a running container; that refusal is the guard, and whatever it keeps is reported as `in_use`. Nothing here keeps its own account of what is in use. The current tools volume, anything without this owner's labels, the spaces' own volumes and a space whose container is gone are never asked to go: a space's volumes may hold work that was never applied, so they go only with that space's own "Delete".
|
|
594
|
+
- **The image is the exception to the labels.** It is a public image, pulled and never labelled, and the only resource a clean-up removes without our labels. It is named by the pinned digest and removed without force, so any container made from it keeps it. Measured on Docker 29.2.1 with the containerd image store: removing an image by its digest reference removes it whole, a tag the user gave the same image included. A user who pulled the same `node` image for their own use pulls it again.
|
|
595
|
+
- **Colima.** Space freed inside the Colima machine does not return to the Mac until the machine trims its disk. After a clean-up that removed anything, when `docker info` names the machine `colima` or `colima-<profile>`, the place runs `colima ssh --profile <profile> -- sudo -n fstrim --all`, found with the host's augmented PATH beside `docker`, within two minutes. Any failure, a missing CLI, a stopped machine or a `sudo` that wants a password among them, is logged and never fails the clean-up. Measured: about a second on a 40 GiB machine. Docker Desktop, Linux and Windows run nothing.
|
|
596
|
+
- A clean-up is refused while a space is being made, because the creation pulls the image and fills the tools before any container holds them. A start of a stopped space needs no such refusal: its containers hold the image and its tools.
|
|
597
|
+
|
|
558
598
|
### Idle stop
|
|
559
599
|
|
|
560
600
|
DESIGN.md, decision 11 and the last line of "Dispatcher, sessions, events"; built in 5d-3. `idle-stop.js` holds both sides.
|
|
@@ -573,9 +613,9 @@ DESIGN.md, "Code in and out", and STAGES.md, row 5; built in 5d-4. `space-setup.
|
|
|
573
613
|
- **Which commands.** The ones OpenChamber runs for a new worktree of the project, chosen by the client the same way: the shared ones from `.openchamber/project.json` in the repository only after the trust prompt, the personal ones always. The trust prompt and its memory are the host's, unchanged, and like the host's they are the client's: the route runs what it is given, as `POST /api/git/worktrees` does. The maintainer's call of 2026-09-28: the same prompt inside a space, because it is also about the user knowing what runs. At most 100 commands of 4000 characters, the host's own limits of 50 shared and 50 personal ones; blank ones are dropped.
|
|
574
614
|
- **When.** At a creation, right after `ready`, in the background, so the agent can start while dependencies install (DESIGN.md, journey step 2); and again when the user asks, `POST /<id>/setup`, with the commands as the project has them then. One run per space at a time, `space_setup_running` otherwise. The waiting first message goes at `ready`, unless the project's "wait for setup commands" setting is on: then the client holds it until the run ended, passed or not.
|
|
575
615
|
- **How.** One `exec` per command, as the space user, `timeout -k 10 3600 /bin/sh -c 'cd -- "$1" || exit 1; exec /bin/bash -c "$2" 2>&1'` with the project path inside and the command as arguments; `$ROOT_PROJECT_PATH` and `$ROOT_WORKTREE_PATH` become the project path inside, where the space's copy of the project is. The command gets the space's own environment, the corridor's proxy variables and PATH among them, so it reaches what the agent reaches. They run one after the other and stop at the first that fails, as the host's `&&` chain does. `timeout` ends a command after an hour with everything it started, which a kill of the host's `docker exec` would not, and answers 124; the host waits a minute longer. The `exec` runs with `killTree`, so a host that quits takes it along; the command inside then goes on to its end or its hour.
|
|
576
|
-
- **What is kept.** A creation that will run commands is listed with `{ state: 'queued', total }` until its code arrived, so the client knows to wait for them; a host before 5d-4 lists none. While a run goes, this process knows which command runs; the list says `{ state: 'running', index, total, command }`, and each step is announced as `openchamber:space-setup` so the clients read the list again. The record keeps `running` when a run begins, then `done`, or `failed` with the command, its exit code, whether the hour ended it,
|
|
616
|
+
- **What is kept.** A creation that will run commands is listed with `{ state: 'queued', total }` until its code arrived, so the client knows to wait for them; a host before 5d-4 lists none. While a run goes, this process knows which command runs; the list says `{ state: 'running', index, total, command }`, and each step is announced as `openchamber:space-setup` so the clients read the list again. The record keeps `running` when a run begins, then `done`, or `failed` with the command, its exit code, whether the hour ended it, the end of its output, and when the run began and ended. The list carries the failed run's `startedAt` and `finishedAt`, `startedAt` null for a record from before it was kept, so the output window can show the domains the gatekeeper refused during the run. Exit code 124 counts as the hour only when an hour passed, because a command of the project's own can answer 124 too. A record that says `running` with no run in this process is listed as `interrupted`: the host did not live to see the run end.
|
|
577
617
|
- **The output is data.** The host reads a window of the last 256 KiB, turns a line a progress bar rewrote into what it said last, takes out the terminal's sequences whole, a link's text among them, every other control character but a tab and a line break, the C1 controls and the marks that turn text direction, and keeps the last 200 lines and 32 KiB. The record's schema refuses more. The client shows it as plain text in a monospace block.
|
|
578
|
-
- **Not a boundary.** A command is code of the project running in the space, like anything the agent runs. The network filter decides what it reaches; an `npm install` in a space that reaches only the addresses the user allowed fails, and the output window
|
|
618
|
+
- **Not a boundary.** A command is code of the project running in the space, like anything the agent runs. The network filter decides what it reaches; an `npm install` in a space that reaches only the addresses the user allowed fails, and the output window lists the domains the journal shows refused between the run's start and its failure, each with Allow. The journal does not say which process asked, so an attempt of the agent's in that span is listed too.
|
|
579
619
|
|
|
580
620
|
### Grants
|
|
581
621
|
|
|
@@ -594,7 +634,10 @@ DESIGN.md, "Words" and "Gatekeeper", and decisions 4, 5 and 13. Stage 5b takes t
|
|
|
594
634
|
- A creation is one process's memory: a host that restarts in the middle of one leaves the space where the step got to, listed from the labels with whatever the record holds; a space whose code never arrived has an empty `spacePath` in its record and its apply fails on the project path. Removing such a space is the way out.
|
|
595
635
|
- The history transfer is not retried on its own; a start of the space retries it while the record says `pending` or `failed`.
|
|
596
636
|
- The lock on a space is one process's memory, like code out's turns: two OpenChamber processes on one Docker daemon are not coordinated.
|
|
597
|
-
-
|
|
637
|
+
- The chat archive keeps what the export holds: a turn still running when the space is deleted is not in it, and a chat created in the space after its list was read goes with the space.
|
|
638
|
+
- A chat created on the host with an archived chat as its parent is not refused; nothing in the app makes one.
|
|
639
|
+
- VS Code has no guard and no list of archives, since the feature has no entry point there (decision 16), and it mounts no Archive page, so it does not show these chats. A turn that any other OpenCode client, the CLI among them, sends to one reaches the model and runs no tool, because of the permission rule.
|
|
640
|
+
- The phone's layout has no Archive page at all, for any archived chat; the notice after a delete has no "Open" there.
|
|
598
641
|
- A run of the setup commands is one process's memory: a host that restarts in the middle lists it as interrupted, while the command inside may still go on to its end or its hour. A second run started then may run beside it.
|
|
599
642
|
- Whether OpenCode inside takes a provider granted after the instance of the space's project started, without a restart, is what the live file of 5b measures; see the pull request of 5b for the outcome. The restart action of the repair stage is the lever if it does not.
|
|
600
643
|
- A grant for a provider the host's catalog does not know is written inside all the same; OpenCode inside then has no `npm` package for it and the turn fails with a provider error. The grant dialog offers the host's catalog, so this is a request nothing in the app makes.
|
|
@@ -965,7 +1008,7 @@ Not built: moving a space when the agent finishes its turn. That needs session a
|
|
|
965
1008
|
|
|
966
1009
|
The name check sits outside the rollback on purpose. If the id is taken, the resources belong to an existing space and must survive the failed call.
|
|
967
1010
|
|
|
968
|
-
After an interrupted step (`command_timeout`, `command_killed`, or `command_output_too_large`) the daemon may still finish the step whose CLI died. `create` then sweeps, waits two seconds, and sweeps again. The second sweep also inspects the seven names directly and removes the ones that exist, labelled or not. This covers a late `docker run` or `docker create`: it makes a missing `src=` volume again, and that volume has no labels. This by-name removal,
|
|
1011
|
+
After an interrupted step (`command_timeout`, `command_killed`, or `command_output_too_large`) the daemon may still finish the step whose CLI died. `create` then sweeps, waits two seconds, and sweeps again. The second sweep also inspects the seven names directly and removes the ones that exist, labelled or not. This covers a late `docker run` or `docker create`: it makes a missing `src=` volume again, and that volume has no labels. This by-name removal, the two for a tools volume described in "Fill rollback", and the space image a clean-up of the places page asks Docker to remove without force (see "Places page"), are the only places in the module where a resource without our labels can be deleted. It is safe because the same call confirmed all seven names absent moments earlier, and the names hold a random 48-bit id, so nobody else makes them in between. The error carries `details.uncertain: true`, so the caller can tell the user to look at the spaces list.
|
|
969
1012
|
|
|
970
1013
|
The manager verifies again after `create` and removes a space that reports violations or cannot be inspected. For the Docker place this repeats a check that already passed. It stays because the guarantee must hold for every place, including a place whose `create` forgets to verify.
|
|
971
1014
|
|
|
@@ -983,6 +1026,8 @@ Since 3b the fetches of code out use `killTree` as well, and so does every git c
|
|
|
983
1026
|
|
|
984
1027
|
`stdin` is a string or a Buffer. A Buffer reaches the child byte for byte, which is how the tarballs of a development build reach the filler. `cwd` sets the working directory and is used by `tools-pack.js` only. `env` replaces the child's environment and is used by host git only.
|
|
985
1028
|
|
|
1029
|
+
Since 5e-4 one command runs another CLI than docker: the `colima ssh` of a clean-up on a Colima machine, through the same `runCommand`, with a timeout and never a shell. See "Places page".
|
|
1030
|
+
|
|
986
1031
|
`check()` says the CLI is missing only for `ENOENT`. Any other spawn error names its errno. `check()` also reads `docker info --format '{{json .SecurityOptions}}'` and reports the place unavailable when the engine has no builtin seccomp profile. Older engines name that profile `default`.
|
|
987
1032
|
|
|
988
1033
|
## Verified and not verified
|
|
@@ -110,23 +110,27 @@ export function readOrCreateOwner(dataDir) {
|
|
|
110
110
|
}
|
|
111
111
|
|
|
112
112
|
/**
|
|
113
|
-
* `dataDir` is the host's data directory, `dockerPath` the docker CLI to run
|
|
113
|
+
* `dataDir` is the host's data directory, `dockerPath` the docker CLI to run, `colimaPath` the
|
|
114
|
+
* colima CLI or null, used only after a disk clean-up on a Colima machine, and `gitPath` the
|
|
114
115
|
* host git that moves code in and out, with `hostEnvironment` as its environment: git starts
|
|
115
116
|
* `docker exec` itself, so the PATH in it must find docker. `place` replaces the Docker place,
|
|
116
117
|
* for the tests; `runCommand` and `openCommandStream` are the two ways this module starts a
|
|
117
118
|
* process, injectable for the same reason. `listProjectDirectories` answers the host's registered
|
|
118
119
|
* project paths, so a space's project label can be resolved to the project it was made for;
|
|
119
120
|
* without it every space is marked as of an unknown project. `readIdleStop` and `saveIdleStop`
|
|
120
|
-
* read and keep the user's idle stop setting in the host's settings.
|
|
121
|
+
* read and keep the user's idle stop setting in the host's settings. `archive` is the chat archive
|
|
122
|
+
* of `space-archive.js`, which a delete saves the space's chats to; without it they go with it.
|
|
121
123
|
*/
|
|
122
124
|
export function createSpacesHost({
|
|
123
125
|
dataDir,
|
|
124
126
|
dockerPath = 'docker',
|
|
127
|
+
colimaPath = null,
|
|
125
128
|
gitPath = 'git',
|
|
126
129
|
hostEnvironment = process.env,
|
|
127
130
|
listProjectDirectories = async () => [],
|
|
128
131
|
readIdleStop,
|
|
129
132
|
saveIdleStop,
|
|
133
|
+
archive = null,
|
|
130
134
|
runCommand = runCommandProcess,
|
|
131
135
|
openCommandStream = openCommandStreamProcess,
|
|
132
136
|
place = null,
|
|
@@ -139,6 +143,7 @@ export function createSpacesHost({
|
|
|
139
143
|
runCommand,
|
|
140
144
|
openCommandStream,
|
|
141
145
|
dockerPath,
|
|
146
|
+
colimaPath,
|
|
142
147
|
owner: readOrCreateOwner(dataDir),
|
|
143
148
|
toolsSource: createRegistryToolsSource(readHostToolVersions()),
|
|
144
149
|
});
|
|
@@ -151,7 +156,6 @@ export function createSpacesHost({
|
|
|
151
156
|
const codeIn = createCodeIn({ git, place: dockerPlace });
|
|
152
157
|
const codeOut = createCodeOut({ git, place: dockerPlace });
|
|
153
158
|
const records = createSpaceRecords({ dataDir, logger });
|
|
154
|
-
const spaceOpenCode = createSpaceOpenCode({ exec: dockerPlace.exec });
|
|
155
159
|
|
|
156
160
|
const listSpaces = () => manager.listSpaces({ placeId: dockerPlace.id });
|
|
157
161
|
const dispatcher = createSpaceDispatcher({
|
|
@@ -163,6 +167,8 @@ export function createSpacesHost({
|
|
|
163
167
|
},
|
|
164
168
|
});
|
|
165
169
|
|
|
170
|
+
const spaceOpenCode = createSpaceOpenCode({ exec: dockerPlace.exec, requestInside: dispatcher.requestInside });
|
|
171
|
+
|
|
166
172
|
const index = createSpaceSessionIndex({ logger });
|
|
167
173
|
let events = null;
|
|
168
174
|
let unsubscribeHostEvents = null;
|
|
@@ -241,6 +247,21 @@ export function createSpacesHost({
|
|
|
241
247
|
serverInside,
|
|
242
248
|
restartOpenCodeInside: (spaceId) => restartOpenCodeInside(dispatcher.requestInside, spaceId),
|
|
243
249
|
listProjectDirectories,
|
|
250
|
+
archiveChats: archive ? ({ spaceId, name, projectDirectory, running, allowUnsaved }) => archive.saveChats({
|
|
251
|
+
spaceId,
|
|
252
|
+
name,
|
|
253
|
+
projectDirectory,
|
|
254
|
+
allowUnsaved,
|
|
255
|
+
source: {
|
|
256
|
+
// The space's own list, read whole; a stopped space that did not start has none to give.
|
|
257
|
+
listChats: async () => {
|
|
258
|
+
if (!running) throw new SpaceError('space_not_running', 'The space is not running');
|
|
259
|
+
const { records: chats, complete } = await readSpaceSessions(spaceId);
|
|
260
|
+
return { chats: chats.map((chat) => ({ id: chat?.id, title: chat?.title })), complete };
|
|
261
|
+
},
|
|
262
|
+
exportChat: (chatId) => spaceOpenCode.exportChat(spaceId, chatId),
|
|
263
|
+
},
|
|
264
|
+
}) : null,
|
|
244
265
|
// A key named by an environment variable is read from the host's own environment, now, and
|
|
245
266
|
// its value is kept nowhere (decision 5).
|
|
246
267
|
readHostSecret: (name) => hostEnvironment[name],
|
|
@@ -26,8 +26,13 @@
|
|
|
26
26
|
//
|
|
27
27
|
// Setup commands, since 5d-4 (DESIGN.md, "Code in and out"): the project's worktree setup commands
|
|
28
28
|
// run inside the space once its code arrived, in the background, and again when the user asks.
|
|
29
|
+
//
|
|
30
|
+
// The chat archive, since 5e-2 (decision 9, journey step 7): a delete takes the space's chats to
|
|
31
|
+
// the host's archive first, starting a stopped space for it, and deletes nothing when they cannot
|
|
32
|
+
// all be saved, unless the user said to delete anyway. See `space-archive.js`.
|
|
29
33
|
|
|
30
34
|
import crypto from 'node:crypto';
|
|
35
|
+
import fsPromises from 'node:fs/promises';
|
|
31
36
|
|
|
32
37
|
import { z } from 'zod';
|
|
33
38
|
|
|
@@ -111,6 +116,10 @@ const failureOf = (error) => ({
|
|
|
111
116
|
* starts, and `restartOpenCodeInside(spaceId)` asks the server inside to restart its OpenCode.
|
|
112
117
|
* `readIdleStop()` and `saveIdleStop(setting)` read and keep the user's idle stop setting, and
|
|
113
118
|
* `serverInside.writeIdleStop(spaceId, setting)` tells it to the server inside.
|
|
119
|
+
* `archiveChats({ spaceId, name, projectDirectory, running, allowUnsaved })` saves a space's chats
|
|
120
|
+
* to the host's archive before it goes, see `space-archive.js`; without it the chats go with it.
|
|
121
|
+
* `folderExists(directory)` says whether the project folder a space was made for is still a
|
|
122
|
+
* folder on the host, for the list.
|
|
114
123
|
*/
|
|
115
124
|
export function createSpaceJourney({
|
|
116
125
|
manager,
|
|
@@ -123,9 +132,11 @@ export function createSpaceJourney({
|
|
|
123
132
|
serverInside,
|
|
124
133
|
restartOpenCodeInside,
|
|
125
134
|
listProjectDirectories,
|
|
135
|
+
archiveChats = null,
|
|
126
136
|
readHostSecret = () => undefined,
|
|
127
137
|
readIdleStop = async () => ({ ...DEFAULT_IDLE_STOP }),
|
|
128
138
|
saveIdleStop = async () => {},
|
|
139
|
+
folderExists = async (directory) => (await fsPromises.stat(directory).catch(() => null))?.isDirectory() === true,
|
|
129
140
|
announce = () => {},
|
|
130
141
|
onSpacesChanged = () => {},
|
|
131
142
|
logger = console,
|
|
@@ -207,7 +218,13 @@ export function createSpaceJourney({
|
|
|
207
218
|
outcome.refsRemoved = true;
|
|
208
219
|
} catch (error) {
|
|
209
220
|
outcome.refsRemoved = false;
|
|
210
|
-
|
|
221
|
+
// A project folder that is gone, moved or deleted, took its refs with it: they cannot be
|
|
222
|
+
// found from here, and nothing of the space is left to remove, so the delete went through.
|
|
223
|
+
if (error instanceof SpaceError && error.code === 'project_folder_missing') {
|
|
224
|
+
logger.warn?.(`[spaces] the service refs of space ${spaceId} stay in its project folder, which is no longer at its path`);
|
|
225
|
+
} else {
|
|
226
|
+
outcome.failures.push(failureOf(error));
|
|
227
|
+
}
|
|
211
228
|
}
|
|
212
229
|
}
|
|
213
230
|
records.remove(spaceId);
|
|
@@ -412,6 +429,7 @@ export function createSpaceJourney({
|
|
|
412
429
|
placeId: entry.placeId,
|
|
413
430
|
projectDirectory: entry.projectDirectory,
|
|
414
431
|
directory: entry.directory,
|
|
432
|
+
projectFolder: { path: entry.projectDirectory, found: null },
|
|
415
433
|
created: entry.created,
|
|
416
434
|
state: entry.state,
|
|
417
435
|
stoppedIdle: false,
|
|
@@ -436,6 +454,10 @@ export function createSpaceJourney({
|
|
|
436
454
|
* which the UI must show as "unknown" and never as "open". With `access` each running space
|
|
437
455
|
* with grants is asked what its gatekeeper holds, one request per such space, so the list can
|
|
438
456
|
* say "needs access"; without it `access` stays null.
|
|
457
|
+
*
|
|
458
|
+
* `projectFolder` names the folder the space was made for, from the record, so a space whose
|
|
459
|
+
* project is no longer registered can still say where it came from; `found` says whether that
|
|
460
|
+
* folder is there now, and is null while a creation is under way or when nothing names it.
|
|
439
461
|
*/
|
|
440
462
|
const listSpaces = async ({ access = false } = {}) => {
|
|
441
463
|
const [spaces, projects] = await Promise.all([manager.listSpaces({ placeId: place.id }), registeredProjects()]);
|
|
@@ -443,12 +465,14 @@ export function createSpaceJourney({
|
|
|
443
465
|
const projectDirectory = projects.get(space.project) ?? null;
|
|
444
466
|
const { record } = records.read(space.id);
|
|
445
467
|
const grants = record?.grants ?? [];
|
|
468
|
+
const projectPath = record?.repository ?? projectDirectory;
|
|
446
469
|
return {
|
|
447
470
|
id: space.id,
|
|
448
471
|
name: space.name,
|
|
449
472
|
placeId: space.placeId,
|
|
450
473
|
projectDirectory,
|
|
451
474
|
directory: projectDirectory === null ? null : spaceProjectPath(space.id, projectDirectory),
|
|
475
|
+
projectFolder: { path: projectPath, found: projectPath === null ? null : await folderExists(projectPath) },
|
|
452
476
|
created: space.created,
|
|
453
477
|
state: space.state,
|
|
454
478
|
stoppedIdle: space.stoppedIdle === true,
|
|
@@ -667,12 +691,45 @@ export function createSpaceJourney({
|
|
|
667
691
|
return requireListed(spaceId);
|
|
668
692
|
});
|
|
669
693
|
|
|
694
|
+
/**
|
|
695
|
+
* Saves the space's chats to the archive, starting a stopped one for it; a space that does not
|
|
696
|
+
* start has no chats to give, which the archive reports as not saved. A space started only for
|
|
697
|
+
* this, whose chats could not be saved, is stopped again, so the refused delete leaves it as it
|
|
698
|
+
* was. Its gatekeeper allows nothing meanwhile: the network is not said again for a delete.
|
|
699
|
+
* Null without an archive.
|
|
700
|
+
*/
|
|
701
|
+
const saveChatsOf = async (space, allowUnsaved) => {
|
|
702
|
+
if (!archiveChats) return null;
|
|
703
|
+
let running = space.state === 'running';
|
|
704
|
+
let started = false;
|
|
705
|
+
if (!running && space.state === 'exited') {
|
|
706
|
+
try {
|
|
707
|
+
await manager.startSpace({ placeId: place.id, spaceId: space.id });
|
|
708
|
+
running = true;
|
|
709
|
+
started = true;
|
|
710
|
+
} catch (error) {
|
|
711
|
+
logger.warn?.(`[spaces] space ${space.id} did not start to give its chats: ${error?.code ?? error?.message ?? error}`);
|
|
712
|
+
}
|
|
713
|
+
}
|
|
714
|
+
try {
|
|
715
|
+
return await archiveChats({ spaceId: space.id, name: space.name, projectDirectory: space.projectDirectory ?? null, running, allowUnsaved });
|
|
716
|
+
} catch (error) {
|
|
717
|
+
if (started) {
|
|
718
|
+
await manager.stopSpace({ placeId: place.id, spaceId: space.id }).catch((stopError) => {
|
|
719
|
+
logger.warn?.(`[spaces] space ${space.id} started for its chats is still running: ${stopError?.code ?? stopError?.message ?? stopError}`);
|
|
720
|
+
});
|
|
721
|
+
}
|
|
722
|
+
throw error;
|
|
723
|
+
}
|
|
724
|
+
};
|
|
725
|
+
|
|
670
726
|
/**
|
|
671
727
|
* Removes a space and everything the host kept for it: the containers, networks and volumes,
|
|
672
728
|
* the service refs in the user's repository and the record. A failed creation is forgotten here.
|
|
673
|
-
*
|
|
729
|
+
* Its chats go to the archive first (decision 9); when they cannot all be saved the space stays
|
|
730
|
+
* and the answer is `chats_not_saved`, unless `allowUnsaved` says to save what can be and go on.
|
|
674
731
|
*/
|
|
675
|
-
const removeUnlocked = async (spaceId) => {
|
|
732
|
+
const removeUnlocked = async (spaceId, { allowUnsaved = false } = {}) => {
|
|
676
733
|
const waiting = pending.get(spaceId);
|
|
677
734
|
if (waiting) {
|
|
678
735
|
if (waiting.state !== 'failed') throw new SpaceError('space_preparing', 'This space is still being made. Wait for it, then remove it.');
|
|
@@ -680,16 +737,17 @@ export function createSpaceJourney({
|
|
|
680
737
|
// A failed creation whose clean-up failed still has containers; those go now, or the space
|
|
681
738
|
// comes back in the list as damaged. One that was cleaned up has nothing left to remove.
|
|
682
739
|
const still = (await manager.listSpaces({ placeId: place.id })).some((space) => space.id === spaceId);
|
|
683
|
-
if (!still) return { id: spaceId, removed: true, refsRemoved: null, failures: [] };
|
|
684
|
-
return { id: spaceId, ...(await removeEverything(spaceId, waiting.projectDirectory)) };
|
|
740
|
+
if (!still) return { id: spaceId, removed: true, refsRemoved: null, failures: [], chats: null };
|
|
741
|
+
return { id: spaceId, ...(await removeEverything(spaceId, waiting.projectDirectory)), chats: null };
|
|
685
742
|
}
|
|
686
743
|
const space = await requireListed(spaceId);
|
|
744
|
+
const chats = await saveChatsOf(space, allowUnsaved);
|
|
687
745
|
const { record } = records.read(spaceId);
|
|
688
746
|
const outcome = await removeEverything(spaceId, record?.repository ?? space.projectDirectory);
|
|
689
747
|
onSpacesChanged();
|
|
690
|
-
return { id: spaceId, ...outcome };
|
|
748
|
+
return { id: spaceId, ...outcome, chats };
|
|
691
749
|
};
|
|
692
|
-
const removeSpace = (spaceId) => exclusive(spaceId, () => removeUnlocked(spaceId));
|
|
750
|
+
const removeSpace = (spaceId, options) => exclusive(spaceId, () => removeUnlocked(spaceId, options));
|
|
693
751
|
|
|
694
752
|
/**
|
|
695
753
|
* Stops every running space, for the switch being turned off. Each space is tried on its own:
|
|
@@ -751,6 +809,35 @@ export function createSpaceJourney({
|
|
|
751
809
|
return change;
|
|
752
810
|
};
|
|
753
811
|
|
|
812
|
+
const requirePlace = (placeId) => {
|
|
813
|
+
if (placeId !== place.id) throw new SpaceError('place_not_found', `There is no place ${placeId}`);
|
|
814
|
+
};
|
|
815
|
+
|
|
816
|
+
/** The disk the spaces take on a place, and what a clean-up would free now (journey step 9). */
|
|
817
|
+
const readDisk = async (placeId) => {
|
|
818
|
+
requirePlace(placeId);
|
|
819
|
+
return place.readDisk();
|
|
820
|
+
};
|
|
821
|
+
|
|
822
|
+
/**
|
|
823
|
+
* Removes what OpenChamber can make again on a place, see `places/docker-disk.js`; Docker keeps
|
|
824
|
+
* whatever is in use. Refused while a space is being made, which pulls the image and fills the
|
|
825
|
+
* tools before any container holds them. Answers what was freed, what Docker kept, and the disk after.
|
|
826
|
+
*/
|
|
827
|
+
const cleanUpDisk = async (placeId) => {
|
|
828
|
+
requirePlace(placeId);
|
|
829
|
+
if (Array.from(pending.values()).some((entry) => entry.state === 'preparing')) {
|
|
830
|
+
throw new SpaceError('space_preparing', 'A space is being made. Clean up when it is ready.');
|
|
831
|
+
}
|
|
832
|
+
const { freedBytes, kept, machine } = await place.cleanUpDisk();
|
|
833
|
+
for (const item of kept.filter((entry) => entry.reason === 'failed')) {
|
|
834
|
+
logger.warn?.(`[spaces] clean-up could not remove ${item.kind} ${item.name}: ${item.message}`);
|
|
835
|
+
}
|
|
836
|
+
if (machine.state === 'failed') logger.warn?.(`[spaces] the Colima machine did not trim its disk: ${machine.message}`);
|
|
837
|
+
if (machine.state === 'trimmed') logger.info?.('[spaces] the Colima machine trimmed its disk after a clean-up');
|
|
838
|
+
return { freedBytes, kept: kept.map(({ kind, reason }) => ({ kind, reason })), disk: await place.readDisk() };
|
|
839
|
+
};
|
|
840
|
+
|
|
754
841
|
/** For a turn-off that did not go through after the spaces were stopped: creations are taken again. */
|
|
755
842
|
const reopen = () => { closing = false; };
|
|
756
843
|
|
|
@@ -769,6 +856,9 @@ export function createSpaceJourney({
|
|
|
769
856
|
const { record } = records.read(spaceId);
|
|
770
857
|
const repository = record?.repository ?? space.projectDirectory;
|
|
771
858
|
if (!repository) throw new SpaceError('project_not_registered', 'The project this space was made for is no longer registered, so its work has nowhere to go.');
|
|
859
|
+
// Code out reaches into the space, so a stopped one would fail there as a generic failure of
|
|
860
|
+
// the place; the dialog needs to know it can offer a start instead.
|
|
861
|
+
if (space.state !== 'running') throw new SpaceError('space_not_running', 'The space is stopped. Start it to apply its work.');
|
|
772
862
|
return { space, repository, spacePath: record?.spacePath ?? space.directory };
|
|
773
863
|
};
|
|
774
864
|
|
|
@@ -783,7 +873,8 @@ export function createSpaceJourney({
|
|
|
783
873
|
/**
|
|
784
874
|
* Brings the work out once more and applies it as a branch or as uncommitted changes. What is
|
|
785
875
|
* applied is what this call fetched, whatever a preview showed. With `removeAfterwards` the
|
|
786
|
-
* space goes once the apply went through, and only then
|
|
876
|
+
* space goes once the apply went through, and only then; when its chats cannot all be saved it
|
|
877
|
+
* stays, and `kept` says why, because the work is applied either way.
|
|
787
878
|
*/
|
|
788
879
|
const applySpace = (spaceId, request) => exclusive(spaceId, async () => {
|
|
789
880
|
const parsed = applyRequestSchema.safeParse(request ?? {});
|
|
@@ -795,9 +886,18 @@ export function createSpaceJourney({
|
|
|
795
886
|
const applied = as === 'branch'
|
|
796
887
|
? { status: 'applied', ...(await codeOut.applyAsBranch({ repository, spaceId, branch })) }
|
|
797
888
|
: await codeOut.applyAsChanges({ repository, spaceId });
|
|
798
|
-
|
|
799
|
-
|
|
889
|
+
let removal = null;
|
|
890
|
+
let kept = null;
|
|
891
|
+
if (removeAfterwards && applied.status === 'applied') {
|
|
892
|
+
try {
|
|
893
|
+
removal = await removeUnlocked(spaceId);
|
|
894
|
+
} catch (error) {
|
|
895
|
+
if (error?.code !== 'chats_not_saved') throw error;
|
|
896
|
+
kept = failureOf(error);
|
|
897
|
+
}
|
|
898
|
+
}
|
|
899
|
+
return { brought, applied, removal, kept };
|
|
800
900
|
});
|
|
801
901
|
|
|
802
|
-
return { createSpace, listSpaces, startSpace, stopSpace, restartSpace, restartOpenCode, removeSpace, stopAllSpaces, reopen, grantAccess, openDomain, readJournal, previewApply, applySpace, readIdleStopSetting, changeIdleStop, runSetup, readSetup };
|
|
902
|
+
return { createSpace, listSpaces, startSpace, stopSpace, restartSpace, restartOpenCode, removeSpace, stopAllSpaces, reopen, grantAccess, openDomain, readJournal, previewApply, applySpace, readIdleStopSetting, changeIdleStop, runSetup, readSetup, readDisk, cleanUpDisk };
|
|
803
903
|
}
|