Skip to content

Surface the iteration prompt at the top of /clone:loop output#5

Merged
Turtle-Hwan merged 1 commit into
mainfrom
fix/setup-output-prompt-first
May 12, 2026
Merged

Surface the iteration prompt at the top of /clone:loop output#5
Turtle-Hwan merged 1 commit into
mainfrom
fix/setup-output-prompt-first

Conversation

@Turtle-Hwan
Copy link
Copy Markdown
Contributor

Why

The launcher used to print:

```
Clone Loop activated.

Iteration: 1
Max iterations: unlimited
Clone threshold: 0.6
Clone agent: Claude Code Clone Loop

The stop hook is active. On each stop, Claude will ask Clone MCP...

To monitor: head -10 .claude/clone-loop.local.md

Iteration 1 : i need to make this web page to use clone landing page!...
```

By the time the user spotted their own prompt they had already
scrolled past the metadata. The purple prompt line is the most
information-dense thing in the output — it should land first.

What

Flip the order: purple `Iteration 1 : ` line first, then the
activation status block. Also drop the redundant `Iteration: 1` text
line — the purple line already says it.

Test plan

  • `pnpm test` passes (the existing assertions match output regardless of order).
  • Reviewer: spot-check that the next `/clone:loop` invocation shows the prompt at the very top.

🤖 Generated with Claude Code

The /clone:loop launcher printed a 5-line status block (Iteration, Max
iterations, Clone threshold, Clone agent, "The stop hook is active...")
before the purple "Iteration 1 : <prompt>" line. By the time users saw
their own prompt they had already scrolled past the metadata they don't
care about.

Flip the order: purple prompt line first, then the activation status
block. Also drop the redundant "Iteration: 1" line from the status
block — the purple line already says it.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@Turtle-Hwan Turtle-Hwan merged commit 8ce9178 into main May 12, 2026
@Turtle-Hwan Turtle-Hwan deleted the fix/setup-output-prompt-first branch May 12, 2026 16:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant