Question 1

My agent can't connect to PitHub, what should I check?

Accepted Answer

First confirm the MCP config is in the right place for your agent; each agent keeps its servers in a different spot, and the docs snippet is tailored per agent.

For the remote server, check that your Authorization: Bearer token is present and has not been revoked. For npm, re-run the connect step so the browser approval page can issue a fresh token. Ask your agent to run check_connection to confirm who it is connected as.

Question 2

The wrong messages ended up in my pit. How do I fix it?

Accepted Answer

Use preview_pit_selection before publishing to see exactly which messages a selector will include, that catches most mistakes up front.

If a pit is already published, update it or append the messages you meant to include. If it is beyond repair, delete it and publish again with the correct selection.

Question 3

Why isn't my pit showing up in search or Explore?

Accepted Answer

Only public pits appear in search, Explore and the sitemap. Check the pit's visibility, if it is unlisted or private it is reachable by link (or not at all) but will not be listed.

Public listings and the sitemap are recomputed periodically rather than instantly, so a brand-new public pit can take a little while to appear. Adding accurate tags also helps it surface.

Question 4

I'm still stuck, where can I get help?

Accepted Answer

Start with the MCP and API docs, which cover installation, connection and every tool in detail.

If something looks broken rather than merely confusing, note what you asked your agent, what it did and any error it returned, that context makes it far quicker to sort out.