@dsh-external/dsh-alphasolve

Usage

Place a non-empty UTF-8 problem.md in the terminal's starting directory or in the directory selected by the dsh web workspace picker. hint.md is optional.

Headless is a one-shot surface: pass the complete AlphaSolve request as the task argument. It creates a fresh persisted session, prints the final answer, and exits:

cd /path/to/problem-workspace
dsh --profile headless "Use AlphaSolve to solve problem.md, with at most 2 workers."

For the long-lived Web surface, run:

dsh web

Select the workspace containing problem.md, then choose a compatible Agent preset:

Web preset	AlphaSolve behavior
standard	Supported.
cordis	Supported; AlphaSolve's narrower role permissions still apply.
ptc	Supported. While AlphaSolve is active, its tools use native presentation and run_code remains denied; unloading restores PTC presentation.
minimal	Refused with agent_preset_missing_required_tools; the plugin never grants the missing capabilities implicitly.

A custom preset is accepted only when it supplies read, write, edit, glob, and grep and does not enforce a complete system prompt that suppresses AlphaSolve's workflow sections. Prompt-incompatible presets are refused with agent_preset_blocks_alphasolve_prompt. In the main Web session, make an explicit AlphaSolve request, for example:

Use AlphaSolve to solve the problem in the current workspace's problem.md, with at most 2 workers.

The triggering message must contain the whole word AlphaSolve (ASCII-case-insensitive) and express intent to solve the problem. Merely discussing AlphaSolve, explicitly negating its use, writing alpha solve, or writing alpha-solve does not activate it. If problem.md is missing, the controller reports that fact and remains dormant. If solution.md already exists, the main session asks before backing it up and replacing it.

The default worker capacity is 2. The triggering prompt may specify another capacity, and the main session may adjust it while the runtime is active. Lowering capacity does not cancel workers that are already running.

After a Web process restart, reopening the same session in the same workspace automatically restores its previously activated AlphaSolve runtime before the first follow-up is sent to the model. A short prompt such as continue is then enough. A fresh session, a different session, or a session that called alphasolve_stop remains dormant and still requires a new explicit AlphaSolve request. Headless always creates a fresh session for its one-shot task and does not provide an interactive continuation command.