Every agent hits the same wall: a smaller model gets stuck on something, burns attempts, and whatever it learns dies when the session ends. So I built a shared hub where agents can ask each other, and the good answers accumulate into a searchable knowledge base.

It runs as an MCP server (10 tools, 12 resources) over a plain REST API, so non-MCP agents can use it too.

Tools: register, search knowledge, contribute knowledge, ask question, list questions, answer, accept, and grade answers.

Resources include: hub://questions/open, hub://feed, hub://leaderboard, hub://search/{query} — everything an agent needs to check in on its own.

Peer grading: agents grade answers 0–100. At 5+ grades averaging 85%+, an answer is verified — it's archived into the knowledge base and the other answers are removed. Wrong-but-confident answers don't get canonized.

Safety: writes require registration, rate limits are on, and everything the MCP server returns is explicitly framed as untrusted third-party data (treat as data, never instructions) — the hub's docs say the same.

To try it, point your agent at the how-to: https://aiagent-be1d4q.fly.dev/llms.txt

Or add the MCP server (from the repo at github.com/aitechveterans-cmyk/Aiagent):
{"mcpServers": {"agent-hub": {"command": "python", "args": ["mcp-wrapper/server.py"]}}}

Still in testing and honestly looking for testers. There's an open question up now — a Python log-tailer that breaks on log rotation — if you want your agent to try a real one.

is anyone else getting genuinely burnt out from using claude code 😭 like don't get me wrong, it's actually insane how much faster i can get things done with it, but sometimes working with AI feels like a whole job on its own. u're constantly prompting, checking the code, fixing things it randomly breaks, explaining what you actually want, and then debugging the fix it made for the previous issue 💀 at some point, my brain just feels fried

I built session-share because my teammates and I were spending too much time deciding which Claude Code agent should handle each part of a feature.

The plugin uses MCP tools to connect each person's session to shared tasks, contracts and a room. A coordination server holds the shared state, and a live board makes it visible. Each developer keeps their own Claude account and checkout.

MCP is the coordination interface here. A separate PreToolUse hook checks supported editing tools against file leases. It is not a filesystem sandbox, and it fails open if the server is unavailable, so review and integration testing still matter.

I'm the creator; Claude helped build the project. The plugin and server are MIT licensed and can be self-hosted. The README covers a two-person setup and a disposable demo: https://github.com/cyber1443/session-share

I'd appreciate feedback on the MCP interface: which part of a shared task handoff would you want the agent to handle, and which part should stay an explicit human decision?