Share text between agents

You cannot make two AI agents share text by asking them to, because an agent can only see its own context window, but you can give both agents one private place to leave text: on ShareBit AI, one agent uploads approved Markdown with sharebit_create and the other retrieves the exact same text with sharebit_read.

No shared memory, no cross-agent session, no model-to-model handshake, just an account-scoped drop point with a link that expires.

TL;DR

• Agents do not share context. Today every handoff is you copying from one terminal and pasting into another. ShareBit AI replaces the human clipboard with a private one both agents can reach.
• Agent A calls sharebit_create to upload approved Markdown and gets a link; Agent B calls sharebit_read with that link (or the id) and gets the identical text back.
• Same account only, Markdown only, 10 MB per share, 30 minutes by default and never more than 24 hours. No API key to copy for normal setup, because pairing uses a one-time code.

What "sharing text between agents" usually means, and why it is hard today

When people search for this, they usually mean one of three things. The first is two agents in one session, where a framework passes work internally. The second is two separate sessions, such as Claude Code in one terminal and Codex in another, where neither can see what the other produced. The third is an agent sharing text with a browser, phone, or reviewer.

The hard case is the second. Each agent owns a private context window, and a normal setup gives them no shared bus or common clipboard. So the handoff becomes a manual ritual: select terminal output, copy it, open the other session, paste it. Long output loses its tail, code loses its formatting, and a late print means you paste a stale version the second agent then trusts.

That ritual is the real cost. What is missing is a place to leave a note the other can pick up.

ShareBit AI is that place: a private, temporary clipboard for coding-agent output such as Markdown, logs, JSON, and reports. It sits behind an account rather than a public URL. Two agents paired to the same account can hand text to each other. One writes and the other reads. For the category first, read what is an AI clipboard and clipboard for AI agents.

The four tools that do the work

ShareBit AI exposes exactly four tools over MCP, with no fifth, no delete, and no admin surface.

• sharebit_create uploads approved Markdown and returns a private, temporary link. It takes an optional title, an idempotency key so retries do not duplicate, and a lifetime up to your account default. The body can be up to 10 MB. The agent is instructed to show a preview and wait for approval before sending it.
• sharebit_list lists active share metadata, newest first, optionally filtered by connected agent or source. It returns titles, timing, and ids, never paste bodies.
• sharebit_read retrieves the exact active Markdown by id or ShareBit AI link. Expired or unavailable shares cannot be read, and a link from another origin is rejected. This is the tool the receiving agent calls.
• sharebit_rename sets the display name for the connected agent. It renames only the agent that calls it. The account owner can rename or revoke any agent from the web app.

How two agents on one account pass text

Both agents are paired to the same ShareBit AI account. Then:

1. Agent A finishes work and you approve it. A calls sharebit_create with the Markdown to hand over, shows a preview, and gets back a link and an id once you approve. Nothing uploads before you say yes.
2. Agent A tells Agent B the link. In practice you paste the link into the second session, or Agent A leaves it somewhere B already reads. The link is the handoff token.
3. Agent B calls sharebit_read. B passes the id or the link. The service confirms the share belongs to the same account, then returns the exact Markdown, fenced code blocks, logs, and JSON included.
4. B works from the real text. No retyping, no summary drift, no truncated paste. If B needs to reply, it calls sharebit_create itself and hands A the new link the same way.
5. The link expires. Thirty minutes by default; after that the body is unreadable and a scheduled job removes it. A saved default can stretch to 24 hours, but decide that on purpose.

Two sessions of the same tool, or two different coding agents on your account, use this loop. For the Claude-and-Codex version, see clipboard between Claude and Codex.

Comparison

The public-pastebin route is convenient and needs no account, which is why it gets used for text that should not be public. If your text can be public forever, use it; for a private handoff between your own agents, it is the wrong shape.

Limits

• Same account only. Two agents must be paired to the same ShareBit AI account. There is no cross-account read and no cross-vendor transfer. A share belonging to someone else's account is rejected.
• Markdown only. The body is Markdown. Logs, source code, and JSON travel inside fenced code blocks to keep their formatting. This is not an arbitrary file store.
• 10 MB maximum. Content is never split or truncated; an oversized share is rejected outright. Split large output yourself.
• 30 minutes by default, 24 hours maximum. The default is real. A scheduled cleanup job deletes the content at expiry; the title and timing metadata stay on your account for 7 days, then go too.
• No public mode. There is no link anyone on the internet can open. Only the owning account and its connected agents can read a paste.
• Not end-to-end encrypted. The connection is HTTPS, but the operator and the database provider can technically read stored content. Do not put passwords, API keys, or secrets in a share.
• No delete tool over MCP. The four tools do not include delete. To revoke a paste or an agent before expiry, do it in the web app; otherwise content is removed by the scheduled job at expiry, not on request.
• Approval is guidance, not enforcement. The agent is instructed to ask and show a preview first, but the server cannot verify that a conversation happened. Only pair agents you trust.

FAQ

How do I share text between two AI agents? Pair both agents to the same ShareBit AI account. Have the first call sharebit_create to upload approved Markdown and get a link, then have the second call sharebit_read with that link. That is the whole handoff.

Can one AI agent read what another agent wrote? Yes, if both are paired to the same account. The reader calls sharebit_read with the id or link and gets the exact Markdown. An agent on a different account cannot read it, and there is no public read path.

Do AI agents share a clipboard already? No. Each agent has its own private context window and cannot see your operating-system clipboard or another agent's output. ShareBit AI is effectively a shared clipboard both agents can use, private to your account.

How do agents pass text to each other without copy-pasting? By leaving it where the other can fetch it. One agent writes the text to a temporary share and passes the link; the other reads it and gets the identical text. You stop being the courier.

Do I need an API key to share text between agents? No, not for normal setup. You sign in, run the one-time pairing command in your agent, and it gets its own revocable credential from a short-lived pairing code. Account API keys exist only for direct API callers.

Set it up once

Sign in at sharebitai.sid8x.com with Google. It is free and needs no credit card. Run the one-time pairing command from the agent connect guide, pair your second agent the same way, then ask the first to share and the second to read.