Hi! Loving the plugin — quick suggestion on a default that surprised me when an agent invoked it.
What happens today
The mcp__plugin_claudebin_claudebin__share tool exposes:
"is_public": {
"default": true,
"description": "Whether the session appears in public listings (false = unlisted, accessible via link)"
}
So when an agent (or a human) invokes /claudebin:share or the underlying MCP tool without explicitly passing is_public: false, the session is published to the public listing.
Why I think the default is risky
Working sessions tend to contain things people would not want indexed publicly:
- Internal project paths, architecture, env var names
- API endpoints, infra details
- In-progress feature work, business context, references to customers/users
- Prompts, agent outputs, and reasoning that is not ready to be quoted publicly
- Occasionally, secrets that slip into terminal output
My read is that most people invoking "save my session" want a private/unlisted record they can revisit later or share with one specific teammate via the link — not something appearing in a public feed by default. The current default means anyone who skips the is_public arg (which is common for agents reading a brief invocation) accidentally publishes to a public listing.
Suggestion
Flip the schema default to is_public: false. Public sharing stays a fully supported option — users (and agents acting on explicit instructions) opt into it by passing is_public: true. Same end-state for people who want public; safer default for everyone else. This matches the typical pattern for paste/share tools (link-by-default, public opt-in).
Happy to send a small PR if useful — looks like the change is one default value in the tool's JSON schema plus a tiny README note.
Thanks for building this!
Hi! Loving the plugin — quick suggestion on a default that surprised me when an agent invoked it.
What happens today
The
mcp__plugin_claudebin_claudebin__sharetool exposes:So when an agent (or a human) invokes
/claudebin:shareor the underlying MCP tool without explicitly passingis_public: false, the session is published to the public listing.Why I think the default is risky
Working sessions tend to contain things people would not want indexed publicly:
My read is that most people invoking "save my session" want a private/unlisted record they can revisit later or share with one specific teammate via the link — not something appearing in a public feed by default. The current default means anyone who skips the
is_publicarg (which is common for agents reading a brief invocation) accidentally publishes to a public listing.Suggestion
Flip the schema default to
is_public: false. Public sharing stays a fully supported option — users (and agents acting on explicit instructions) opt into it by passingis_public: true. Same end-state for people who want public; safer default for everyone else. This matches the typical pattern for paste/share tools (link-by-default, public opt-in).Happy to send a small PR if useful — looks like the change is one default value in the tool's JSON schema plus a tiny README note.
Thanks for building this!