diff options
| -rw-r--r-- | prompts/skills/continue-reminder/SKILL.md | 4 | ||||
| -rw-r--r-- | prompts/skills/continue-reminder/references/amp.md | 20 |
2 files changed, 9 insertions, 15 deletions
diff --git a/prompts/skills/continue-reminder/SKILL.md b/prompts/skills/continue-reminder/SKILL.md index 6ed360b..b927a31 100644 --- a/prompts/skills/continue-reminder/SKILL.md +++ b/prompts/skills/continue-reminder/SKILL.md @@ -13,7 +13,7 @@ Use this skill when a coding agent running inside a tmux pane gets paused (rate- - You need to schedule a delayed `continue` or equivalent command - The agent lives in a tmux pane and accepts keyboard input to resume - You want the resume to happen automatically even if you step away -- You support multiple coding agents (Claude, Codex, OpenCode, AMP) and need per-agent specifics +- You support multiple coding agents (Claude, Codex, OpenCode, ampcode) and need per-agent specifics ## How It Works @@ -30,7 +30,7 @@ Each coding agent has its own quirks (prompt text, resume command, key sequences - [Claude](references/claude.md) — Claude Code CLI in tmux, rate-limit screen, `continue` - [Codex](references/codex.md) — Placeholder for Codex CLI specifics - [OpenCode](references/opencode.md) — Placeholder for OpenCode Agent specifics -- [AMP](references/amp.md) — Placeholder for AMP agent specifics +- [ampcode](references/amp.md) — Placeholder for ampcode agent specifics ## Common Ingredients diff --git a/prompts/skills/continue-reminder/references/amp.md b/prompts/skills/continue-reminder/references/amp.md index 7dfd2aa..2e14424 100644 --- a/prompts/skills/continue-reminder/references/amp.md +++ b/prompts/skills/continue-reminder/references/amp.md @@ -1,31 +1,25 @@ -# AMP Agent — Continue Reminder +# ampcode Agent — Continue Reminder -> **PLACEHOLDER** — This reference has not been populated yet because the AMP agent was not active in the originating session. +> **PLACEHOLDER** — This reference has not been populated yet because the ampcode agent was not active in the originating session. ## Known Differences from Claude | Aspect | Expected Behavior | |--------|-------------------| -| Rate-limit screen | Unknown; AMP may handle throttling server-side | +| Rate-limit screen | Unknown; ampcode may handle throttling server-side | | UI paradigm | Unknown; could be TUI, web UI, or API-driven | | Resume command | Unknown | -| Session model | AMP might use long-running processes or ephemeral workers | +| Session model | ampcode might use long-running processes or ephemeral workers | ## TODO -1. Clarify what "AMP" refers to in this context: - - **Amplify** (AWS)? - - **AIX MP** (IBM)? - - A proprietary/multi-agent coding harness? - - Something else? - -2. Determine AMP's runtime environment: +1. Determine ampcode's runtime environment: - Does it run in a tmux pane? - Is it daemonized? - Does it expose a CLI that can be scripted? -3. If AMP has a resumable terminal session, capture the pane state and record: +2. If ampcode has a resumable terminal session, capture the pane state and record: - Pause / limit indicator text - Keystrokes or commands required to resume -4. Update this file with a concrete example mirroring the Claude reference structure. +3. Update this file with a concrete example mirroring the Claude reference structure. |