MaCcyP Adds a Clipboard Agents View
MaCcyP is Harleen Sahni’s open-source fork of Maccy, p0deje’s lightweight clipboard manager for macOS. Agents keep producing text that humans must copy into another place. MaCcyP adds a separate Agents view where coding agents can push commands, snippets, SQL, drafts, and other paste-ready text without touching your normal clipboard. Make agent handoffs visible and reviewable before they become pasted action.
An agent-to-user paste channel is a small interface boundary where an agent can prepare text for a human to inspect, choose, and paste elsewhere. That boundary matters for developer productivity, but it also fits the bigger AI coding governance question: how do you let coding agents help without turning every suggestion into an implicit action?
Watch the paste queue, not the whole chat
MaCcyP’s core trick is humble. Instead of making you scroll through Claude Desktop, Anthropic’s desktop app, or a coding agent transcript to find “the one command,” it gives the agent a place to put the command.
That sounds small until you notice how often agent work ends with copy-paste. Run this shell command. Paste this JavaScript into DevTools. Try this SQL in a console. Send this drafted reply. Add this environment variable.
The project’s README describes MaCcyP as “Maccy Put” and points readers to MACCYP.md before the inherited Maccy README. As of August 31, 2026, the repository is tiny: mainly Swift, one GitHub star in the verified snapshot, and a forked base rather than a large product surface.
That smallness is part of the story. Developers on Hacker News tend to notice tools that remove one paper cut cleanly. MaCcyP does not promise a new IDE, a new agent runtime, or a replacement for review. It names a real friction point and adds one view to an app many Mac developers already understand.
Don't treat the Agents view as a safe execution lane. It is not. It is a queue for text the human can paste. The review step still belongs to the person at the keyboard.
Keep agent output out of your normal clipboard
The most interesting design choice is separation. MaCcyP’s Agents view is not just “agent writes to clipboard faster.” The stated point is that agents push text into a separate place, without touching your clipboard.
That distinction matters because your clipboard is ambient state. It leaks into password managers, terminals, browsers, ticket comments, and chat windows. If an agent overwrites it, you may not notice until the wrong thing lands in the wrong field.
A separate agent paste queue makes the handoff explicit. You can scan the item, pick the right one, and paste it intentionally. For Codex the same idea maps nicely to a terminal workflow: the agent can draft a command, but the human still decides when and where it runs.
A concrete example: Codex suggests a migration check after editing a Prisma schema.
npx prisma migrate diff --from-schema-datamodel prisma/schema.prisma --to-schema-datasource prisma/schema.prisma --script
That is useful text. It is also a command that deserves context. A paste queue gives you a chance to ask: is this local, staging, or production? Does it read only, or can it mutate state? Am I in the right repo?
Watch for optimizing away the pause. MaCcyP helps with hunting and copying. It should not remove the “do I actually want to paste this?” moment.
Add one repo rule for pasteable commands
For Codex users, the practical move is not to rebuild your workflow around MaCcyP. It is to make pasteable agent output boring and labeled.
Put a small rule in AGENTS.md for repos where agents frequently hand you commands. Keep it short enough that a coding agent will follow it under pressure.
# AGENTS.md
## Pasteable output
When you produce text the human is expected to paste elsewhere:
- Put only the final pasteable text in the paste channel when one is available.
- Label the destination before the text: terminal, browser console, SQL client, email, or config file.
- Do not push secrets, tokens, production connection strings, or destructive commands.
- For shell commands, include the expected working directory and one verification step in the chat.
- If a command can mutate data, explain the risk before offering the pasteable version.
This is a light rule, not a policy tome. It tells the agent what belongs in the queue and what belongs in the conversation around the queue.
It also creates a clean split with MCP. The Model Context Protocol is the integration layer many agents use to reach tools and data; a paste queue is the human handoff layer after the agent has prepared text. If you connect an agent to an MCP server that can read tickets, query docs, or inspect a repo, the paste queue should still contain only the final text you want to evaluate.
Don't use the queue as a dumping ground. If every intermediate thought, partial command, and speculative SQL query lands there, you are back to searching a transcript with extra steps.
Try MaCcyP on one annoying handoff
MaCcyP is worth trying when the same copy-paste handoff interrupts you several times a day. It is probably overkill if your agent mostly edits files in-place and your verification loop already lives inside the terminal.
A good first experiment is narrow. Pick one workflow where agents produce pasteable text but do not need execution permissions. Browser console snippets are a nice test. So are drafted release notes, local-only commands, or non-secret config examples.
Start from the repository, read MACCYP.md, and build only if the current instructions and macOS requirements fit your machine. The upstream Maccy README says Maccy works on macOS Sonoma 14 or higher; because MaCcyP is a fork, do not assume broader compatibility unless the fork documents it.
For people tracking adjacent agent-skill experiments, the same “put reusable help behind a clean boundary” pattern also shows up in Skills MCP Searches Thousands of Agent Skills. The shape is different, but the taste is similar: make the agent’s help easier to find, constrain, and inspect.
Watch for starting with secrets. Do not test a new paste path with production credentials, customer data, or database URLs. Use harmless text first and learn how the interface behaves.
Try it safely
| Fit | Use MaCcyP when... | Skip it when... |
|---|---|---|
| Daily friction | You often copy commands or snippets out of agent chat. | You rarely paste agent output outside the editor. |
| Human review | You want a visible queue before pasting. | You want the agent to execute actions automatically. |
| Clipboard safety | You do not want agents overwriting your normal clipboard. | Your current clipboard history already solves the problem. |
| Data sensitivity | You can test with harmless local text. | The first use case involves secrets or production access. |
A small safe test looks like this:
git clone https://github.com/harleensahni/MaCcyP.git
cd MaCcyP
open MACCYP.md
Then choose one paste type, such as local terminal commands. Ask the agent to label the destination, put only the final command in the Agents view, and keep risk notes in chat. Paste nothing until you have read the exact text.
Further reading
Where to go next
Start from AI coding governance.