Turtle
2464d6169f
Squashes feat/personal-config-dsh-home: personal config.yaml and .env move from ~/.config/dsh to the Harness home (~/.dsh), plus the module-graph, lockfile, and i18n pairing regeneration that followed.
@deepseek-ai/dsh
The dsh command-line entry, following the apps/ assembly tier proposed by the dsh web PR (#443): apps/* are product assemblies over packages/* libraries. This branch ships one surface — plain dsh [config.yml] boots the interactive TUI coding agent — and reserves the web and -p/--prompt subcommands for that PR so the dispatch merges as a union.
The TUI surface:
- boots the shipped default config (
examples/tui-agent/cordis.yml) or an explicit config argument, throughdsh-app-boot; - resumes a persisted session with
dsh --resume <session-id>— the form the TUI prints on exit and lists under/resume; the flag setsRESUME_SESSION_IDbefore boot so the shipped config rehydrates that session, and a missing or unreadable id fails loud and exits nonzero; - treats the invoking directory as the workspace — sessions, relative paths, and workspace instructions resolve from the cwd;
- tells the agent where its own source lives: after boot it adds a prompt section naming this harness checkout, resolved from the launcher's real path so it holds under a PATH symlink and an arbitrary cwd, so the self-referential
cordistoolset can read and modify it; - applies the personal overlay from
~/.dsh(see app-boot's Personal config):.envfills environment gaps (ambient > project.env> personal.env),config.yamlpatches the booted tree.
Install (developer machine)
Symlink the source-running launcher onto your PATH; it resolves the checkout through its own real path, so code changes apply on the next launch with no build step:
ln -sf "$(pwd)/bin/dsh" ~/.local/bin/dsh
pnpm run demo:tui runs the same entry from the repo root. The built form (lib/bin.js, via pnpm run build) needs node --expose-internals for the shipped config's HMR entry, exactly like the demo bins.