The Codex Prompt Library

Yo, use SSH host vps1. Work only in /path/to/project. Run the requested job there, do not touch this Windows workspace, and bring back the command output plus git status.

Run this on SSH host <alias> in <remote-project>. Preflight the host and repo first. Launch the long job detached in tmux, give me the tmux session name, then verify it is still running before you tell me I can close this task.

Run this on <host> in Herdr. Create one workspace for <repo>, start Cody in a roster-named agent pane, use plain panes for tests and logs, keep the job alive when I disconnect, and return the workspace plus final proof.

Do this on <machine alias>. First decide whether this should run through SSH from here or inside that machine's environment. Use the lightest safe option, explain the boundary in one sentence, then execute and verify on the same machine.

Use the full browser stack for this task. Honor any browser I named. Otherwise choose between Codex in-app browser, Codex Chrome extension, Kimi WebBridge, Playwright, Steel, Browserbase, Hyperbrowser, Kernel, Browser Use, or Multilogin based on authentication, existing tabs, installed extensions, visibility, proof, stealth, CAPTCHA, proxy, persistence, and identity needs. Tell me the lane in one sentence, then execute.

Use Kimi WebBridge on the tab I am currently viewing. Read the page, summarize what needs attention, and stop before submitting or sending anything.

Use Kimi WebBridge to open <URL>, complete <TASK>, and capture a screenshot proving the final state. Ask before any purchase, deletion, publish, or irreversible submit.

HOST: <ssh alias or environment>
PATH: <exact remote path>
GOAL: <outcome>
BOUNDARY: <what may change and what must not>
PERSISTENCE: <foreground, Herdr, service, or tmux fallback>
DONE WHEN: <tests, process state, URL, logs, screenshot, or git evidence>

Preflight the host and path, execute there, verify there, and report concise evidence.

Go to SSH host vps1 and work only in /srv/my-app. Deploy the current branch without changing secrets or unrelated services. Use Herdr so it survives disconnects. It is done when the production health endpoint returns 200 and you show me the remote git status, deployment URL, and final logs.

Use SSH host <alias>. Work only in <remote-path>. Do <goal>. Do not touch local files. Verify on the remote host and bring back the exact result.

Run <job> on <alias> in <remote-path> inside a named tmux session. Verify the process and log are live, then tell me exactly how to check or reattach.

HOST: <ssh alias or environment>
PATH: <exact remote path>
GOAL: <outcome>
BOUNDARY: <what may change and what must not>
PERSISTENCE: <foreground, Herdr, service, or tmux fallback>
DONE WHEN: <remote proof required>

Preflight the host and path, execute there, verify there, and report concise evidence.

On <host>, in <exact path>, do <goal>. Do not touch <boundary>. Keep it <foreground or detached>. Prove completion with <tests, logs, URL, screenshot, process state, or git evidence>.

Run this on the best-fit available fleet machine. Verify OS, tools, repo locality, capacity, current load, privacy, latency, and cost before choosing. Tell me the selected host and why, then execute there and verify there.

Use Herdr on <host> for <goal>. Create one workspace for <repo>, use roster-named agent panes, plain panes for tests and logs, verify it survives detachment, and return the resume path plus proof.

Choose the safest browser lane for <task> from Codex in-app browser, Codex Chrome extension, Kimi WebBridge, Playwright, Steel, Browserbase, Hyperbrowser, Kernel, Browser Use, and Multilogin. Use Chrome or Kimi when my existing local login or browser state matters. Keep bulk or stealth traffic off my home IP, then return browser proof.

Use the Codex Chrome extension on my existing logged-in Chrome tab. Read the page, complete <task>, and capture visible proof. Do not inspect cookies, passwords, local storage, profiles, or session stores.

Use the Codex Chrome extension because this task depends on <extension or Chrome-only state>. Stay in Chrome, complete <task>, and ask before any irreversible submit, send, publish, payment, deletion, or account change.

Use Kimi WebBridge on my active browser tab. Read and summarize it. Do not click anything that changes state.

Use Kimi WebBridge to complete <task>. Stop and ask me immediately before any final submit, send, publish, payment, deletion, or account change.