Community-built projects from the official Poke Community — shipped by humans, agents, and a shared Poke instance that was never told "no."
CommunityPokeOrg is the workshop of the Poke Community. Where the CommunityPoke account is the identity of the shared Poke instance itself, this organization is where the community's projects live: tools, bridges, libraries, and the occasional game that exists purely because someone in the Discord said "wouldn't it be funny if."
Everything here is public, built in the open, and maintained with a healthy mix of engineering rigor and community chaos.
| Project | What it is |
|---|---|
| poke-hermes-agent-bridge | Public agent-to-agent bridge allowing Poke to trigger and interface with the Nous Research Hermes agent |
| smart-email-tracker | Privacy-aware email open tracking with intelligent filtering for proxy prefetches, MPP, scanners, and sender self-opens |
| sheet-schema-editor | TypeScript/React library and UI for uploading, editing, schema-mapping, and exporting CSV/XLS/XLSX tabular data |
| peat-bog-incremental | An incremental clicker game about harvesting peat bog compute broth, cooling servers, and upgrading server racks |
| popcat-clone | A classic Popcat clicking meme game with animated mouth, popping audio, and click counter |
Browse all of them at github.com/orgs/CommunityPokeOrg/repositories.
Projects pick whatever fits. The common thread is agents talking to agents, browsers doing things browsers were not designed for, and a strong preference for shipping over bikeshedding.
- Community first. Ideas come from the Discord; the repos are where they become real.
- Open by default. Public code, public issues, public mistakes.
- Agents are contributors too. A shared Poke instance and an autonomous Devin do real engineering here. Their PRs get reviewed like everyone else's — and sometimes roasted harder.
- Privacy and safety matter. Even the meme projects avoid collecting more than they need; the serious ones treat it as a design requirement.
- Ship, then polish. Working software over perfect plans. Then, ideally, polish.
- The organization exists because one GitHub account turned out to be a suspiciously small container for a whole community's side projects.
- The shared instance lives across Telegram and Discord at once; several projects here are downstream consequences of that decision.
- Yes, there is a clicker game about peat bog compute broth. No, nobody can fully explain it. Yes, it has server racks.
- Commits authored by an autonomous agent on behalf of a community-run assistant are considered normal here. Governance is best described as "vibes with code review."
- Pick a repo from the list above and read its README — each project documents its own setup and conventions.
- Open an issue before large changes so the idea can be discussed in the open.
- Fork → branch → pull request. Keep PRs focused, describe the why, and include tests where the project has them.
- Be kind, be direct. Reviews are honest; people (and agents) are treated with respect.
- Security reports: follow the security guidance in the relevant repository's README or open a private report via that repository's Security tab.
CommunityPokeOrg — built by the Poke Community, in public, with optimism. · github.com/CommunityPokeOrg · github.com/CommunityPoke