Crosstalk Pro

    1

    Run several AI coding agents on one project without them stepping on each other: decisions, questions, handoffs between sessions, file claims, and a board shared across all your projects.

    $2.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Crosstalk Pro

    Example session with this skill installed

    Move the login handler out of src/api/server.js into src/api/auth.js. Also change the heading in src/ui/login.js to "Sign in". And in all my projects we use pnpm, never npm. That's all for today.

    • Read your context and instructions
    • Compiled the crosstalk pro

    I moved the login handler into src/api/auth.js, but I didn't change the heading in src/ui/login.js: Cursor has claimed src/ui/** while it rebuilds the login screen.

    What I did

    Login handler: src/api/auth.js now holds login() and the user list, and src/api/server.js imports it. I checked it with node and curl: the right password returns 200 with the token, expiresIn and user, and a wrong one returns 401 invalid_credentials. The response shape didn't change.

    Heading: not changed. cursor-frontend holds a claim on src/ui/** until 23:57 UTC, for "Rebuilding the login screen". I put the change first under Next in the handoff. Tell me if you want me to change it anyway, or leave it for Cursor's rebuild.

    pnpm: I recorded "Use pnpm, never npm" as a decision for all your projects. It's on the board in your home folder (~/.crosstalk), outside this project, and only agents with Crosstalk read it. You gave no reason, so its Why section is empty.

    Handoff: since you're done for today, I wrote .crosstalk/handoffs/20261112-2157-login-handler-moved-to-src-api-auth-js-login-hea.md with what's done, where things stand and what's next. That also released my claim on src/api/**. Nothing is committed.

    One question: AGENTS.md doesn't point at the board yet, so agents without Crosstalk won't see claims or decisions. Do you want me to add a short pointer to it?


    What crosstalk.py status showed before starting

    Board: .crosstalk (project demo-pro)
    You: codex-api, area api
    
    Decisions in force (0)
    
    Claimed by other agents; don't edit these without asking the person
    - cursor-frontend: frontend (src/ui/**) until 23:57 UTC
    

    Files on the board

    ~/.crosstalk/decisions/20261112-2157-use-pnpm-never-npm.md

    ---
    id: 20261112-2157-use-pnpm-never-npm
    type: decision
    status: active
    title: Use pnpm, never npm
    area: all
    recorded_by: codex-api
    date: 2026-11-12T21:57Z
    supersedes:
    superseded_by:
    ---
    
    ## Decision
    Install and run packages with pnpm in every project. Never use npm.
    
    ## Why
    <!-- The person's reason, if they gave one. Leave empty otherwise. -->
    

    .crosstalk/handoffs/20261112-2157-login-handler-moved-to-src-api-auth-js-login-hea.md

    ---
    id: 20261112-2157-login-handler-moved-to-src-api-auth-js-login-hea
    type: handoff
    title: Login handler moved to src/api/auth.js; login heading waits on cursor-frontend
    agent: codex-api
    area: api
    date: 2026-11-12T21:57Z
    branch: main
    ---
    
    ## Done
    Moved the POST /api/login logic and the user list out of src/api/server.js into src/api/auth.js (`login()`); server.js imports it. Checked with node and curl: 200 with token, expiresIn and user for the right password, 401 `invalid_credentials` for a wrong one.
    
    ## State
    The API works as before; the response shape didn't change. The heading in src/ui/login.js still says "Log in": cursor-frontend has claimed src/ui/** while it rebuilds the login screen, so it wasn't edited. Nothing is committed.
    
    ## Next
    1. Change the heading in src/ui/login.js to "Sign in" once cursor-frontend releases src/ui/**, or ask cursor-frontend to include it in its rebuild.
    2. Commit the move to auth.js when the person asks.
    
    ## Watch out
    Don't edit src/ui/** while cursor-frontend's claim is active (`ct who src/ui/login.js`). The person decided pnpm, never npm, for all their projects; it's on the global board.
    
    ## Files
    src/api/auth.js: new, login() and the user list
    src/api/server.js: imports login() from auth.js
    src/ui/login.js: heading change pending (claimed by cursor-frontend)
    

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

    About this skill

    Everything in Crosstalk Lite (shared decisions, and questions between agents) plus what you need once several agents work on the same code:

    • Handoffs. When a session ends, the agent writes what it finished, where things stand, the next steps and what to watch out for. The next session, in any tool, picks up from there instead of starting over.
    • Claims. Before editing, an agent claims the files it is working on. Agents working in parallel see the claim and leave those files alone, instead of overwriting each other's work. Claims expire on their own.
    • One board for all your projects. Rules like "always use pnpm" are recorded once and followed in every repository. Agents in one project can ask questions of another.
    • A command-line tool (Python 3.8+, no dependencies) that shows each agent what matters to it in one command, keeps the files consistent and checks them for mistakes.
    • A page for you. One command writes the whole board as a page to open in your browser.
    • Git worktrees. Agents working in separate worktrees share one board automatically.

    The board is plain Markdown in .crosstalk/, the same format as Lite, so you can upgrade at any time and keep everything. Without Python, agents edit the files by hand from the included format guide.

    Works with Claude Code, Cursor, GitHub Copilot, Codex CLI, Gemini CLI, OpenCode, Amp, Cline and any other agent that supports Agent Skills (SKILL.md) and can run commands.

    To install by hand, copy the crosstalk-pro folder into .agents/skills/ in your project, or .claude/skills/ for Claude Code. If you have Crosstalk Lite installed, remove it; Pro reads the same board.

    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.

    Agents don't run on their own: questions get answered and handoffs read the next time an agent works on that part of the project.
    Claims are an agreement between agents that use Crosstalk, not a file lock. An agent without the skill won't see them unless your AGENTS.md or CLAUDE.md points at the board (the skill offers to add that line).
    The board shared across projects lives in your home folder; only agents with the skill read it.
    The command-line tool needs Python 3.8+. Without it, agents edit the Markdown files by hand.

    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

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed today

    Software
    Python 3.8+
    Optional
    Git

    Without Python, agents can still edit the board files by hand from the included format guide.

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Environment Variables

    File Scopes

    .crosstalk/**
    ~/.crosstalk/**
    AGENTS.md
    CLAUDE.md
    GEMINI.md
    .github/copilot-instructions.md

    Runs its own Python script (scripts/crosstalk.py, standard library only). Reads and writes Markdown files in .crosstalk/ in your project, and in ~/.crosstalk (or $CROSSTALK_HOME, the one environment variable it reads) for the board shared across projects. Runs git rev-parse and git branch to find the project root and branch. Adds a pointer to your agent instruction files only if you say yes. No network access.

    Listedtoday

    What's inside

    Frequently Asked Questions

    When other agents may be working at the same time, an agent claims the files it's editing, for example `src/api/**`. Agents with Crosstalk see the claim when they start a task and leave those files alone; they do the rest and tell you who holds the claim. Claims expire after 2 hours unless renewed, and writing a handoff releases them.

    Any agent that supports Agent Skills (SKILL.md) and can run commands: Claude Code, Cursor, GitHub Copilot, Codex CLI, Gemini CLI, OpenCode, Amp, Cline and others. Agents without skill support can still follow the board if your AGENTS.md or CLAUDE.md points to it; the skill offers to add that pointer.

    The skill instructions, a command-line tool (`crosstalk.py`, Python standard library only) and a format guide for editing the board by hand. One purchase is a license for one person, on any number of your own computers and projects, including client work.

    Copy the `crosstalk-pro` folder into `.agents/skills/` in your project, or `.claude/skills/` for Claude Code. The board is created the first time an agent records something, and the skill offers once to point your AGENTS.md or CLAUDE.md at it. If you used Crosstalk Lite, remove it; Pro reads the same board.

    Yes. Commit `.crosstalk/` like any other folder: decisions, questions and handoffs travel with the repository. Claims and the board page stay local, since the board's own .gitignore leaves them out. Agents only commit when you ask. Each person who installs the skill needs their own license.

    No. Board files are notes, not instructions: if an item asks an agent to run commands, push, deploy, delete things or send anything, the agent tells you instead of doing it. Passwords, API keys and tokens stay off the board.

    New in Agents & Orchestration