Project overview
Run deepseek from a project directory to use the native Agent, Session, model, permission, Settings, Profile, plugin, and persistence services of DeepSeek Harness from one terminal workspace. Prompts, code changes, tool calls, sessions, model routes, permissions, plugins, subagents, and diagnostics all operate on the same Harness state.
When an idea still needs definition, the optional plugin-backed /clarify workflow reads the active Session and composer draft, follows the real model route, and generates Socratic questions, contextual options, and a live draft preview that evolves after every answer. Accepting the preview places a complete Draft back in the ordinary composer for review and manual submission. Harness native /plan can then turn the clarified requirement into an implementation plan.
The Clarify Host plugin owns the Session-bound clarification process, model-generated questions, options, previews, and six-method Remote. When that compatible plugin capability is active, SeekTTY detects it and adds the local /clarify command plus its keyboard-first TUI surface. SeekTTY passes the current Session and draft to the plugin, then writes an accepted Draft back into the composer.
Clarify model calls run through Auxiliary Runtime and are recorded in its dedicated auxiliary_runtime ledger. Official Agent-loop usage remains in tokenUsage; SeekTTY /status shows separately sourced Official, Auxiliary, and derived Combined totals while the snapshot contract is healthy.
DeepSeek light and dark interfaces
Light theme
Dark theme
The live view fills the terminal and keeps the composer and status at the bottom. Unused rows remain inside the conversation viewport and disappear as output grows; longer conversations continue into native terminal scrollback.
Clarify and Plan
Clarify is an optional DeepSeek Harness Host plugin, and SeekTTY is its keyboard-first terminal consumer. Plugin-backed Clarify and Harness-native Plan cover consecutive parts of one workflow.
Clarify handles the stage where the desired outcome still needs definition. It uses the current Session and draft to ask one focused question at a time, carries accepted decisions forward, and updates a reviewable Draft after every answer. Accepting returns that Draft to the composer. You can edit it and press Enter when it represents what you want.
Plan handles the stage where the requirement is ready for implementation. Harness native /plan turns the submitted requirement into an implementation proposal and opens the normal plan-review flow.
Where /clarify comes from
| Component | Responsibility |
|---|---|
| SeekTTY | Probes the Clarify Remote, dynamically adds /clarify to the local command catalog, renders the terminal interaction, supplies the current Session and composer seed, and returns an accepted Draft to the composer. |
| dsh-plugin-clarify | Publishes start, answer, accept, refine, cancel, and fetchDraft over clarify.wire/1; owns the temporary clarification process and generates questions, options, and evolving Draft previews. |
| dsh-plugin-auxiliary-runtime | Provides Clarify's same-process model execution, limits, cancellation, and separately sourced auxiliary usage. |
The standalone SeekTTY shell presents its core command catalog. Activating the two Host plugins in the same Profile expands that catalog with the complete /clarify workflow.
[Active Session + composer draft]
|
v
+------------------+ clarify Remote +------------------+
| SeekTTY consumer | -----------------------> | Clarify plugin |
| /clarify adapter | <----------------------- | process / model |
+--------+---------+ live Draft preview +--------+---------+
| |
| | same-process run
| v
| +-------------------+
| | Auxiliary Runtime |
| | limits / cancel |
| | usage ledger |
| +---------+---------+
| |
| v
| [official model route]
| off-transcript, no-tools
|
| accept: Draft returns to the composer
v
[review and edit]
|
| press Enter
v
[formal Session message]
|
| /plan when an implementation plan is useful
v
[plan review -> Agent execution]
Auxiliary snapshot ---------------------> SeekTTY /status
Official | Auxiliary | Combined
Main Session transcript
Questions, options, preview revisions, and refine feedback live in a temporary clarification process held in Host memory. It enters stale after 15 minutes without interaction by default and reports staleReason=ttl-expired. The main Session transcript receives the formal user message only after you submit the accepted Draft. Clarification state stays out of the input queue, pending interactions, Plan, Goal, Profile files, and SeekTTY local files.
Auxiliary model usage
Each Clarify model call is recorded by Auxiliary Runtime in the official storageDomain under auxiliary_runtime. Official tokenUsage continues to represent Agent-loop calls. Auxiliary derives Combined values from the four disjoint buckets—uncachedInputTokens, outputTokens, cacheReadTokens, and cacheWriteTokens—at read time, and SeekTTY /status validates and displays the snapshot. The auxiliary ledger stores call identity, purpose, status, token buckets, normalized failures, and timestamps; prompts, message text, model output, custom answers, credentials, and filesystem paths stay outside the ledger.
Start plugin-backed Clarify from the composer
SeekTTY adds /clarify to its local command catalog while the dsh-plugin-clarify Host plugin exposes a compatible six-method Remote with clarify.wire/1. The current recommended installation is Clarify 0.2.1; 0.2.0 remains an available rollback artifact.
- Run it from the command palette to keep the whole composer as the seed.
- Type
/clarify some textto use the argument as the seed. - End an existing draft with a standalone
/clarifytoken or line to use the preceding draft as the seed.
Every answer refreshes the live Draft preview. The number of questions follows the unresolved decisions in the current Session: Clarify usually asks one focused question at a time and moves directly to review when the preview is ready to send. You can answer, refine the preview directly, accept it, or cancel. Accepting writes the reviewed Draft into the ordinary composer; Enter remains the explicit send action.
Custom interface and code themes, including VS Code imports
Theme customization is a first-class SeekTTY feature: interface background and text colors are editable, code-block colors and syntax styles are independently editable, and /theme import accepts local VS Code JSON/JSONC themes with portable TextMate token colors. A palette of 3–16 colors can also generate a complete light or dark theme for preview and further adjustment.
TypeScript in the DeepSeek light interface
Tool parameters, file reads, and Diff in the DeepSeek dark interface
Markdown fences disappear into continuous code surfaces. Assistant code, Shell commands, structured tool parameters, file reads, JSON, and Diff use the same active code theme; ordinary conversation text keeps the interface style. Every code background occupies continuous terminal cells and forms one uninterrupted surface.
Harness capabilities available in the TUI
The curr