0 Fork 0

Files

T

creatixchu f57a4a044a fix(gui): address ds-review-bot findings on image attachments

- dsh web gains --provider/--model: a non-deepseek provider mounts the
  matching pi-ai catalog route (ambient credentials), making image input
  reachable from the shipped Web assembly; requires an explicit --model
- attachment-local syncs the publication directories after the hard-link
  publish so a reported durable reference survives a crash (POSIX; Windows
  relies on filesystem metadata journaling)
- the attachment seam gains storage-free validateImage; the host validates a
  complete multi-image prompt before persisting any member, so one malformed
  image cannot strand valid members as unreferenced objects
- startSession sends before navigating: a rejected first send keeps the empty
  state, its error strip, and the complete draft mounted
- the webserver rejects an undeclared-length body the moment it crosses the
  configured limit instead of draining a potentially endless stream to EOF

2026-07-24 20:55:25 +08:00

2.6 KiB

Raw Blame History

`@deepseek-ai/dsh`

The dsh command-line entry follows the apps/ assembly tier: apps/* are product assemblies over packages/* libraries. Plain dsh [config.yml] boots the interactive TUI coding agent, dsh -p "task" runs one headless turn, and dsh web serves the browser UI.

The TUI surface:

boots the shipped default config (examples/tui-agent/cordis.yml) or an explicit config argument, through dsh-app-boot;
resumes a persisted session with dsh --resume <session-id> and, when the Node host exposes process.execve, supplies the TUI's in-place handoff host: after selector preflight and current-session flush, the host disposes the app and replaces the process with a normalized resume flag; runtimes without process replacement keep the displayed command fallback, the flag still sets RESUME_SESSION_ID before boot, and a missing or unreadable id fails loud instead of creating a fresh session;
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 cordis toolset can read and modify it;
applies the personal overlay from ~/.dsh (see app-boot's Personal config): .env fills environment gaps (ambient > project .env > personal .env), config.yaml patches the booted tree.

The Web surface treats its invoking directory as the default project, loads applicable AGENTS.md/CLAUDE.md instructions into each agent-loop request prefix with a 65,536-byte render budget, and opts into first-message model titles. dsh web --provider <name> --model <id> selects the default agent route; a non-deepseek provider additionally mounts that pi-ai catalog route with the provider's ambient credentials (e.g. ANTHROPIC_API_KEY), which is how image input reaches a visual-capable model, and requires an explicit --model. The headless surface retains deterministic fallback titles without making the auxiliary title-model request.

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) boots the same config under plain Node.

2.6 KiB Raw Blame History

@deepseek-ai/dsh

Install (developer machine)

2.6 KiB

Raw Blame History

`@deepseek-ai/dsh`