mirror of
https://github.com/hanzoai/dev.git
synced 2026-10-25 03:32:32 +00:00
zeekay
901a81abe9
The docs read as OpenAI's Codex CLI: a getting-started page titled for it, `codex --enable skills` and `code sandbox macos` for commands that do not exist, defaults given as gpt-5.1-codex-max/openai when they are zen5-coder/hanzo, a Homebrew page describing a formula we do not publish. Removed three tui-stream-chunking notes and the execpolicy page: they document modules and a subcommand that live only in the vendored upstream copy. There is no execpolicy subcommand and no .codexpolicy loader in code-rs; the page told users to run something the binary does not have. Rewrote tui-alternate-screen against the source. It described an auto/always/never enum and a --no-alt-screen flag; the shipped behavior is a tui.alternate_screen bool with Ctrl+T, which replays the transcript into scrollback on the way out — a better answer to Zellij than the one written down. Genuine openai-provider documentation stays.
1.4 KiB
1.4 KiB
Custom prompts
Save frequently used prompts as Markdown files and reuse them quickly from the slash menu.
- Location: Put files in
$CODE_HOME/prompts/(defaults to~/.code/prompts/; Dev also reads legacy~/.codex/prompts/). - File type: Only Markdown files with the
.mdextension are recognized. - Name: The filename without the
.mdextension becomes the slash entry. For a file namedmy-prompt.md, type/my-prompt. - Content: The file contents are sent as your message when you select the item in the slash popup and press Enter.
- Arguments: Local prompts support placeholders in their content:
$1..$9expand to the first nine positional arguments typed after the slash name$ARGUMENTSexpands to all arguments joined by a single space$$is preserved literally- Quoted args: Wrap a single argument in double quotes to include spaces, e.g.
/review "docs/My File.md".
- How to use:
- Start a new session (Dev loads custom prompts on session start).
- In the composer, type
/to open the slash popup and begin typing your prompt name. - Use Up/Down to select it. Press Enter to submit its contents, or Tab to autocomplete the name.
- Notes:
- Files with names that collide with built‑in commands (e.g.
/init) are ignored and won’t appear. - New or changed files are discovered on session start. If you add a new prompt while Dev is running, start a new session to pick it up.
- Files with names that collide with built‑in commands (e.g.