FAQ · vibeshub

Question 1

What is vibeshub?

Accepted Answer

vibeshub turns your Claude Code and Codex sessions, including every subagent they spawn, into shareable, replayable traces. Instead of reviewing only the final diff, teammates can open the actual run: the prompts, tool calls, and reasoning behind how a change was shipped.

Question 2

How does a trace get from my terminal to a teammate?

Accepted Answer

You work the way you already do. When you open or update a PR from a Claude Code or Codex session, the plugin uploads the trace and posts a link back on the PR as a comment automatically, so reviewers see how you built it before they read the diff.

Question 3

What are the ways to share a session?

Accepted Answer

Three ways: automatically on every PR you open or update; on demand with the /share-trace slash command; or by dropping your .jsonl session file in the browser. They all land in the same place.

Question 4

What do I need before installing?

Accepted Answer

Claude Code or Codex, the gh CLI authenticated with gh auth login, and python3 3.9+ on your PATH. The hook uses only the Python standard library, so there is nothing to pip install.

Question 5

Does it work with Claude Code and the Anthropic CLI?

Accepted Answer

Yes. vibeshub is built for Claude Code first. Install it as a plugin from inside the CLI with /plugin marketplace add vibeshub/vibeshub then /plugin install vibeshub@vibeshub. After that, the next time your agent runs gh pr create the trace is redacted, uploaded, and commented on the PR automatically.

Question 6

Does it support Codex too?

Accepted Answer

Yes. Some teams run Claude Code, some run Codex; every PR carries its session either way, and it all lands in one searchable archive. Add it from your terminal with codex plugin marketplace add vibeshub/vibeshub then codex plugin add vibeshub@vibeshub.

Question 7

Are subagents captured too?

Accepted Answer

Yes. A trace includes the full session, including every subagent your primary agent spawns, so reviewers see the complete picture of how a change was built, not just the top-level conversation.

Question 8

Do I need a separate account?

Accepted Answer

No. Your GitHub auth is your vibeshub identity, so there is nothing else to set up. Sign in with GitHub and the next PR you open from Claude Code or Codex arrives with the session attached.

Question 9

Who can see my traces?

Accepted Answer

Visibility mirrors GitHub. A trace from a public repo stays public; a trace from a private repo stays private. The same people who can read the repo can read the trace, with no separate access list to manage.

Question 10

Do I have to set up separate permissions or ACLs?

Accepted Answer

No. Access mirrors GitHub, so the right people already have visibility with zero setup. There are no separate vibeshub ACLs or accounts to provision for your team.

Question 11

Can I share a session without opening a PR?

Accepted Answer

Yes. Use the /share-trace slash command to publish a single session on demand, or drop a .jsonl file on the web. These are handy for solo work or showing off a run.

Question 12

How are my secrets handled?

Accepted Answer

Secrets are stripped twice: once on your machine before anything leaves, and again on the server. Redaction catches API keys, tokens, and KEY=value shapes so they never appear in a published trace.

Question 13

What kinds of secrets does redaction catch?

Accepted Answer

Common credential patterns such as GitHub tokens, Anthropic and OpenAI API keys, and AWS secrets are matched and replaced inline before upload. Known provider patterns are matched first, with a high-entropy fallback for anything else that looks like a secret.

Question 14

Does redaction run before the trace leaves my machine?

Accepted Answer

Yes. The first redaction pass runs locally, so secrets are stripped on your machine before upload. A second pass runs on the server as a backstop. The local hook relies only on the Python standard library.

Question 15

How do I manage who can see a trace after it's shared?

Accepted Answer

Because visibility mirrors GitHub, you manage trace access through the repo it came from. Changing a repo's visibility or its collaborator list changes who can read the attached traces, with no separate permission layer to keep in sync.

Question 16

Can I delete a session I've shared?

Accepted Answer

Yes. Traces are tied to your GitHub identity, so you can remove a trace you published. Deleting it takes it out of the searchable archive, and removing the PR comment removes the link from that pull request.

Question 17

How do I stop new traces from being uploaded?

Accepted Answer

You have options: skip a single PR by sharing intentionally with /share-trace instead of the automatic flow; uninstall the plugin to stop automatic uploads entirely; or revoke the GitHub auth the plugin uses to cut off its access.

Question 18

Something isn't covered here — how do I get it removed?

Accepted Answer

For takedown or access questions that aren't self-serve, reach out through the vibeshub GitHub repo. Since access already mirrors your GitHub permissions, removing repo access is often the fastest first step.

Everything you need to know about sharing the vibe.

Common developer questions.

Install once. Every PR you ship comes with a trace.