This article is derived from the plugin's already-indexed fields (wiki / faq / compatibility_json / readme), not freshly generated by AI. Source field is noted at the end of each section.

Quick start

odai (dsh/plugin)

— source: plugin_wiki.wiki_content

Install & verify

dsh plugin --profile web add odai-dsh-plugin

Run the command above in your DSH Web Profile. Then enable the plugin in the plugin list.

— source: plugins.install

Key points

• ask only when the missing answer would change the goal, scope, authorization, acceptance, risk, or stop line
• verify what it can verify from files, commands, logs, tests, or project context before asking you
• keep lightweight tasks lightweight instead of turning every request into ceremony
• avoid claiming that something was tested, delegated, reviewed, or verified when it was not
• combine specialist skills and domain guidance only when the task needs them, instead of stuffing every rule into every turn

— source: plugin_wiki.readme_en (fallback readme_raw)

FAQ

Is it necessary to restart the DSH session after installation for it to take effect?

Yes. Plugin is a profile-level bundle; after installation you must restart the DSH process and open a new session with the corresponding profile; before restarting, the current session still runs according to the host's default behavior.

Will every simple question be slowed down by the process after installation?

No. By default, routing.mode=auto, tasks with clear results, actions, and authorization and low risk are left to execute directly in the current controller; only when complexity, ambiguity, risk, or domain gaps appear do they enter deeper processing like planning, execution, and acceptance.

Is it necessary to manually specify the model for planning or execution?

Not necessary. When the host's default model is sufficient, the Plugin won't autonomously select a model elsewhere; only when the user explicitly states in natural language "use provider-x/model-y for planning, reasoning level high" will it be persisted to $DSH_HOME/odai/routing.json, taking effect from the next user turn.

What local state will be written? Will it be cleared after uninstallation?

Routing, output mode, compression model, skill source, skill self-evolution, long-term memory, and personal safety continuity records are all written to the $DSH_HOME/odai/ directory; installation, update, repair, and uninstallation will not automatically clean these files up. Agent and Plugin share the same copy.

What is the relationship with odai-dsh-agent? Do they need to be installed together?

Plugin is a profile-level bundle that overrides all agent presets under that profile; Agent is an independent form that selects Odai preset per session. Under normal circumstances, having both installed is redundant; they are only installed together when needing "profile-scoped Plugin + separate Odai agent preset" to coexist.

Do I need to stop DSH before upgrading or uninstalling?

Yes. The odai-dsh-plugin repair-sessions subcommand actively checks whether the DSH process is still running; if local process check fails or an active DSH is found, it directly refuses to write, not relying on luck.

Will logs written by older versions cause DSH to refuse to load?

Older Plugins like 0.0.3 / 0.0.4 wrote private odai/* audit events; after 0.0.7, they are stored in $DSH_HOME/odai/session-evidence/. When upgrading from older versions, first stop DSH, then run npx odai-dsh-plugin repair-sessions --yes to add ignorable markers to historical events.

— source: plugin_wiki.faq_json

Compatibility

• DSH: 0.1.0-rc.7 || 0.1.0-rc.8
• Node: >=22.15.0

— source: plugin_wiki.compatibility_json

Pitfalls

Review the upstream repo before installing. This guide is auto-derived from indexed fields and may lag the latest release. If anything contradicts the official docs, treat the upstream source as authoritative.

— source: general rule