More than UI plugins
Carrots can expose local surfaces, remote APIs, streamed sessions, jobs, logs, and agent-facing tool interfaces.
Carrots
Tiny workloads with real capabilities and explicit permissions.
A carrot is the unit of software that runs inside Bunny Ears. It can expose UI, APIs, tools, jobs, or streamed sessions without pretending to be just another trusted plugin.
Examples
The workload model is broad by design.
Editor workspacePTY terminal runtimeGit operationsBrowser sessionModel inference servicePython-backed toolchain
Composable on a machine
A git carrot, PTY carrot, editor carrot, or browser carrot can cooperate on the same Bunny Ears instance without collapsing into one monolith.
Permissioned from the start
File access, subprocesses, ffi, and other powerful capabilities belong in a reviewed permission model, not in a trust-me extension culture.
Workload rollout
Get notified when the first carrots start to land.
Waitlist
Track the first workload releases.