Basic Usage

Daily workflow#

• Open the project folder you want to change and run dash from it.
• Type a request, press Enter to send, Ctrl+Enter for a new line.
• Review tool rows: reads, edits, searches, and commands in progress are shown as they run.
• When Dash asks a question with options (ask_user), reply with the number or the option text.

cd my-app
dash
> Refactor src/utils/date.js to use the shared helper and keep the tests green

Task checklist#

For multi-step work Dash maintains a task checklist (todo_write) with statuses not-started, in-progress, and completed. A sticky checklist popup mirrors the current plan while Dash works.

Sessions#

/new starts a fresh chat. /sessions lists previous conversations; open one to continue where you left off. Sessions are stored in ~/.dash/sessions.json, and Dash can recall recent activity from past sessions via read_session_activity when a task needs prior context.

Checkpoints#

Before editing your files, Dash records a snapshot under .dash/checkpoints/ in the project. If a change goes wrong, ask Dash to roll back — the undo_checkpoint tool restores the last recorded state. The .dash folder is excluded from its own file tools, so snapshots are not treated as project files.

Memory#

Dash keeps a small private memory file at ~/.dash/memory.md (up to 32 KB) for your preferences and facts across sessions. Updates are proposals: write_memory requires your approval before anything is written.

Sub-agents#

Self-contained sub-tasks can be delegated with spawn_subagent. The sub-agent returns a result to the main conversation; the details of its inner execution are not presented as session history.