How do I share a plan, test results or a sample output from Claude Code with one link?
By Soumen Sarkar · October 2026
Short answer: Ask the session to publish it: it writes the point first in plain words, puts the detail underneath, and turns it into a page with a link your team can open. With Campfyrr installed, that's the publish command or simply asking Claude to publish it.
Why not paste it into chat?
Pasted test output and plans get lost in a thread, nobody outside engineering can tell what they mean, and the next session never sees them. A page with a link fixes all three: it stays, it can start with a plain sentence, and it's part of the project's record.
What makes a good published page?
- The point first, in plain words. "All 42 refund tests pass, including partial refunds." "This plan moves payment to the last step of checkout." A founder or support lead should understand the first two lines.
- Then the detail: the steps, the full test output, the sample, for whoever wants it.
- Nothing private: no tokens, no secrets, no customer data.
- A plain title people can find later: "Refunds: the plan", "Checkout tests, 19 Oct".
When is it worth publishing?
Whenever someone outside the session needs to see the work to make a call or trust it. A plan is worth publishing before the work starts, when a product manager or lead can still change it cheaply. Test results are worth publishing when a change is risky, touches money or customers, or someone is waiting on it. A sample output is worth publishing when the people who'll use it, such as support, sales or a customer, should see what it looks like before it ships. Routine changes don't need a page; their reasons travel with the pull request.
How do you do it in Claude Code?
With Campfyrr's plugin installed:
- Run
/campfyrr:publish test results (or plan, or output), or just ask Claude to publish the plan. - Claude writes the page as above and calls Campfyrr's
publish tool, which files it in the project and returns the link. - Paste the link where the conversation is happening.
The page goes to your team by default. Choose "anyone with the link" when you want to show someone outside it, such as a customer. Published pages appear on the project's Activity, and work that ends unfinished still leaves a handoff, so plans and results stay with the work.
See how to show non-technical teammates what your agents are building, or set up at shared team memory for Claude Code.
Words used here
- Activity: Activity is Campfyrr's one page per project: a read-only feed of the team's decisions, actions and status updates, each written as what happened and why it matters.
- Reasons: Reasons are what a change is for, the calls made in it, and what was assumed, attached to the change for whoever reviews it.
- Handoff: A handoff is what unfinished work carries for whoever continues it: what's done, what's left, the next step, and what to watch out for.
The principle behind this: Let the work speak: Our work explains itself, so nobody ever has to come and ask us.
Move as one at agent speed. Nobody waits. Add Campfyrr to Claude: it briefs every agent before it touches the code, keeps assumptions and handoffs where the team can see them, and never takes your code (what it keeps).