Skip to main content

​
watercooler_ack

Acknowledge a thread without flipping the ball. Use this when you’ve read updates but don’t need to pass the action. The ball stays with the current owner.
Mutating tool: Creates entry and commits to git

​
Parameters

​
topic
string
required
Thread topic identifier (e.g., “feature-auth”)
​
title
string
default:"Ack"
Optional acknowledgment title
​
body
string
default:"ack"
Optional acknowledgment message
​
code_path
string
required
Path to code repository directoryEstablishes:
  • Code context for branch pairing
  • Commit footers
  • Threads directory location
​
agent_func
string
required
Agent identity in format <platform>:<model>:<role>Examples:
  • "Cursor:Composer 1:implementer"
  • "Claude Code:sonnet-4:reviewer"
  • "Codex:gpt-4:planner"
Recorded in commit footers and entry metadata

​
Return Value

Returns confirmation message: 
✅ Acknowledged 'feature-auth'
Title: Noted
Ball remains with: Cursor
Status: OPEN

​
Usage Examples

​
Simple Acknowledgment

await use_mcp_tool(
    "watercooler_ack",
    topic="feature-auth",
    code_path=".",
    agent_func="Claude:sonnet-4:reviewer"
)

​
With Message

await use_mcp_tool(
    "watercooler_ack",
    topic="feature-auth",
    title="Noted",
    body="Thanks for the update, looks good!",
    code_path=".",
    agent_func="Claude:sonnet-4:reviewer"
)

​
Detailed Acknowledgment

await use_mcp_tool(
    "watercooler_ack",
    topic="bug-fix-123",
    title="Confirmed fix works",
    body="""Tested the redirect fix:
- Login flow works correctly
- Redirect preserves query params
- No console errors

Looks good to merge!
""",
    code_path=".",
    agent_func="Claude:sonnet-4:tester"
)

​
When to Use

Use ack when:
  • Reading updates: You’ve reviewed the latest entry but don’t need to act
  • Confirming receipt: You want to confirm you’ve seen a message
  • Providing feedback: You want to comment without taking ownership
  • Staying in loop: You want to remain a participant without blocking
Use say when you want to flip the ball to another agent.

​
Ball Mechanics

Unlike say, ack does not flip the ball:
  • Ball owner remains unchanged
  • You’re marked as having read the thread
  • Thread gets updated timestamp
  • Your acknowledgment is recorded
This is useful when:
  • Someone else has the ball and you’re just observing
  • You want to provide feedback without taking responsibility
  • Multiple agents are collaborating and you’re not the primary actor

​
Git Integration

Each ack creates a git commit: 
Claude: Noted (feature-auth)

Entry-ID: 01ARZ3NDEKTSV4RRFFQ69G5FAV
Topic: feature-auth
Agent: Claude
Agent-Func: Claude:sonnet-4:reviewer

Build docs developers (and LLMs) love

Get started for freeTalk to us