Pokemon Catcher

Turn shipped engineering work into Pokémon catches, evolutions, and a collection that grows across BB threads. Earn rewards from local branches and worktrees, or selected GitHub repositories and Shortcut, Jira, or GitHub Issues. Choose any catch as an evolving companion, incubate Eggs through token usage, and filter the collection by type, rarity, generation, or shiny status. GitHub, Shortcut, and Jira connections require user-supplied credentials; the plugin also requests data, sprites, and cries from PokéAPI-hosted services. Requires BB 0.43+ and Plugin SDK 0.4.87+.

Overview

View source

What you get

Build a Pokémon collection while you ship software. New branches, commits, closed pull requests, and completed project-management work can trigger catches. Caught Pokémon retain their own experience, can become your active companion, and evolve as your BB token usage grows.

The collection panel includes starter selection, shiny and rarity details, type and generation filters, a paginated Pokédex, Egg incubation, evolution progress, and controls for choosing a companion. Your companion also appears in the thread header and can run alongside active agent work.

Activity sources

Pokemon Catcher detects new branches and worktrees in repositories known to BB. Optional integrations can watch selected GitHub repositories for branches, commits, closed pull requests, and closed GitHub issues. Shortcut and Jira can also supply completed project-management work.

Requirements and privacy

Local Git detection requires no external account. GitHub, Shortcut, and Jira integrations require credentials supplied in plugin settings. Credentials are stored as secret plugin settings and are not returned to the frontend.

The plugin requests Pokémon data from PokéAPI and loads sprites and cries from PokéAPI-hosted GitHub repositories. Pokemon Catcher is an unofficial fan project and is not affiliated with Nintendo, Game Freak, Creatures Inc., The Pokémon Company, or PokéAPI.

More in Thread Content 89

Change what people see or do inside an open thread.

View all

Generative UITurns agent replies into charts, diagrams, maps, plans and forms you can use, right in the chat. Agents choose from 86 components on their own, with no setup: sliders and filters recompute in the page, and buttons, choices and forms put your answers in your message, which reaches the agent when you send it. Test reports, logs, lint errors and coverage files render as their own components instead of pasted text, and a thread's changes, commits, pull request and workers are read live from BB. Adds about 6,400 tokens of instructions to sessions whose replies you read, and looks up photos, places and map tiles on Wikimedia Commons, Wikipedia, Photon and OpenStreetMap unless you turn web lookups off. Relies on BB internals, so a BB update can show the blocks as code until the plugin catches up.

ComicBit894

Agent BoardFollow live BB agent activity, freshness, completion outcomes and monitoring health. Filter and group visible work by project, repository, provider or status. Optional Ollama Fleet and Redteam add worker visibility. Requires BB 0.40+; BB 0.46.0 recommended.

Aaron Phifer363

Agent TracesSee where your agents' time goes, from every thread down to each command, tool call, and subagent of a turn. A turn opens as a timeline that splits the agent's time into waiting on you, tools, subagents, thinking, writing, and model time, and it grows live while the agent works. Select a call to see its exit code, output, and arguments, or jump to the reply that followed it in the chat. A Traces page in the sidebar compares your recent threads by active time, calls, and errors, and two turns can be compared phase by phase. Turns export as OpenTelemetry or an HTML snapshot, and the bb agent-traces command gives agents the same answers. Traces come from the thread history on your bb server; an OpenTelemetry collector is optional.

Nicolas Charpentier277