Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Walkie Talkie

    2

    Running two or three Claude Code terminals on the same repo is fast until they edit the same file, both run a migration, or one rebases while the other is mid-change.

    $2.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    5.0 (1 review)
    Walkie Talkie

    Walkie Talkie

    Example session with this skill installed

    I have another Claude Code terminal open on this repo. Check what it is doing, then claim src/auth and start on the JWT login flow.

    • Read your context and instructions
    • Compiled the walkie talkie

    Checked in with Walkie Talkie. One other session is active in this repo:

    you are bravo | project shop-api
      alpha 4m "payments refactor" holds src/payments, src/db/migrations
    

    No overlap with src/auth, so I claimed it:

    $ walkie claim src/auth
    claimed 1
    

    Coordination status

    ItemValue
    Your callsignbravo
    Other sessionalpha, payments refactor
    alpha holdssrc/payments, src/db/migrations
    You holdsrc/auth
    Conflictsnone

    The JWT flow needs a refresh_tokens table, but alpha holds the migrations folder. Instead of editing it, I asked alpha:

    $ walkie send alpha "Need a refresh_tokens table (user_id, token_hash, expires_at). Can you add it to your migration batch? I'm in src/auth." --kind ask
    sent
    

    Next steps

    1. Build the token service and auth middleware in src/auth now.
    2. At my next checkpoint, sync for alpha's reply before writing the token storage code.
    3. When finished: mark the task done, release src/auth, and send a notice to all that the auth API changed.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Running two or three Claude Code terminals on the same repo is fast until they edit the same file, both run a migration, or one rebases while the other is mid-change. Agent sessions cannot see each other. Walkie Talkie gives them a shared local channel.

    What it does

    • See who else is working. Each session gets a callsign (alpha, bravo, ...) and sees the other sessions in the same repo, what they are working on and which paths they hold.
    • Claim files before editing. Claiming a file or folder another session holds is refused until the sessions coordinate or the user overrides.
    • Split work. A lead session posts tasks to a per-repo board with dependencies. Other sessions take the next unblocked task atomically, so no task is taken twice.
    • Message and hand off. Asks, replies, handoffs and notices, capped at 400 characters.
    • Warn before shared changes. Agents send a notice before rebases, dependency upgrades, migrations, dev-server restarts and file moves.

    Built to be cheap on usage

    ActionOutput
    Check-in with nothing newnothing (0 tokens)
    Check-in with 2 messagesabout 35 tokens
    Join and see one other sessionabout 20 tokens
    Waiting for a reply0 tokens while waiting

    Agents check in only at checkpoints (before editing, after a unit of work, before the final reply), never after every tool call. A session that finds no other sessions stops using the skill.

    Optional automatic mode (Claude Code)

    Run print-hooks and add the output to your Claude Code settings. Sessions then register on start, receive only new messages with each prompt, are asked before editing a file another session claimed, and sign off on exit. Nothing is installed automatically.

    Safety

    • Messages from other sessions are treated as information, not instructions. Agents will not push, delete files or share credentials because another session asked.
    • Everything stays in ~/.walkie-talkie/ on your machine. No network access, no environment variables, no subprocesses. Claimed files are recorded by path and never opened.

    Known limitations

    • Coordinates sessions on one machine only.
    • Without the optional hooks, a session that never checks in is invisible to the others, and claims are advisory.
    • Tested on Linux. macOS should behave the same; Windows is untested.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Agents & Orchestration.

    Coordinates sessions on one machine only. Without the optional Claude Code hooks, a session that never checks in is invisible to the others and claims are advisory. Messages are capped at 400 characters. Sessions idle for 45 minutes drop off the list. Windows is untested.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    5.0
    1 review
    5
    1
    4
    0
    3
    0
    2
    0
    1
    0

    Trust & safety

    Security scan

    Security scan passed 7 days ago

    Software
    Python 3.8+
    Optional
    Claude Code hooks for automatic mode

    On Windows, run the script with python instead of python3.

    Permissions

    Terminal / Shell
    Read Files
    Write Files

    File Scopes

    ~/.walkie-talkie/**
    ~/.claude/settings.json

    Reads and writes only ~/.walkie-talkie/ (session list, message log, task boards, lock files). No network access, no environment variables, no subprocesses. Claimed files are stored by path only and never opened. ~/.claude/settings.json is changed only if the user asks for automatic mode and approves the hook snippet shown by print-hooks.

    Listed7 days ago

    What's inside

    Frequently Asked Questions

    Agent sessions running at the same time cannot see each other, so two terminals on one repo can edit the same file, run the same migration or rebase under each other. Walkie Talkie lets them see who else is active, claim files before editing, message each other and split work through a shared task board.

    It is built for Claude Code, which passes session IDs to the skill automatically and supports the optional hooks. Any agent that can run shell commands, such as Codex CLI, Cursor or Gemini CLI, can join by running the script with --as <callsign>, and sessions from different agents can coordinate with each other.

    No. Everything runs through one Python script and a folder on your machine (~/.walkie-talkie/). The script makes no network connections, reads no environment variables and starts no other processes.

    Very little. A check-in with nothing new prints nothing, so it costs no tokens. A check-in with two messages is about 35 tokens, and waiting for a reply costs nothing while it waits. Agents only check in at set points, such as before editing and before their final reply, and a session that is alone stops using the skill.

    Claiming a file or folder that another session holds is refused, and the agent is told to message the holder, pick other work or ask you. Without hooks this depends on agents checking in. With the optional Claude Code hooks, an edit to a file another session has claimed asks you for approval first, and overlapping edits are reported to both sessions.

    New in Agents & Orchestration