Public interactive shell and operator-facing UI patterns for uDOS v2.
- uCODE interactive shell
- command palette
- workspace panels
- ThinGUI and browser handoff
- reusable shell interaction patterns
- canonical runtime semantics
- provider and network ownership
- API budgeting and autonomy policy
src/ucode/src/palette/src/panels/src/thingui/src/tui/docs/tests/scripts/config/examples/
Keep package installs explicit and avoid embedding runtime caches into the repo.
Use scripts/run-shell-checks.sh as the default local validation entrypoint.
The current shell has two active lanes:
npm run devfor the legacy TypeScript starter previewnpm run go:runfor the new Go Bubble Tea bootstrap TUInpm run first-runfor one-command local install-and-launch bootstrap
docs/activation.mdQUICKSTART.mddocs/v2.0.1-shell-foundation.mddocs/v2.0.3-go-bootstrap.mddocs/v2.1-core-mcp-consumption.mddocs/tui-keybindings.mddocs/tui-viewport-contract.mdexamples/basic-ucode-session.mdscripts/run-shell-checks.sh
Shell presents Core semantics to operators and hands network-backed work to Wizard.
Current family alignment:
- active family version-round:
v2.3 - local shell traction can use fractional notation such as
v2.0.3+0.0.5 - the family source of truth is
uDOS-dev/@dev/notes/roadmap/v2-roadmap-status.md
For the active workflow-backed operating model:
- Shell is the local operator entrypoint for workflow and automation inspection
- scheduled work remains bounded evidence refresh, not hidden promotion logic
- binder progression rules live in
uDOS-dev/docs/workflow-schedule-operations.md
Current startup/demo surfaces:
npm run first-runhelpcommandswizardteststatusroutesdoctorhealth startupsetup storydemo listdemo ux(visual ASCII UX fixtures; seedemo/screens/,bash scripts/demo-ux-walk.sh)demo run thinui-c64demo run thinui-nes-sonicdemo run thinui-teletext