Skip to content

Remove the Bitbucket (bb) bundled agent#329

Open
basedfriday wants to merge 1 commit into
mainfrom
rip-out-bitbucket-agent
Open

Remove the Bitbucket (bb) bundled agent#329
basedfriday wants to merge 1 commit into
mainfrom
rip-out-bitbucket-agent

Conversation

@basedfriday
Copy link
Copy Markdown
Collaborator

Summary

  • The Bitbucket bundled agent (bb) is retired — it no longer ships in the daemon and won't show up in agent discovery, list_capabilities, or workspace config. Workspaces that referenced agent: bb will need to drop it.
  • Dropped the @coderabbitai/bitbucket dependency (the bb agent was its only consumer) and its transitive openapi-fetch@0.14.1, refreshed deno.lock and THIRD_PARTY_LICENSES.md to match.
  • The webhook-tunnel Bitbucket provider stays put — incoming Bitbucket webhooks still turn into Friday signals, so a user-space agent can pick them up.
  • Playground tidy-up: the workspace signal row no longer offers a bitbucket webhook provider option (it was only meaningful for the bb agent).

Test plan

  • deno task typecheck — clean
  • deno task test — full suite green
  • Confirm bundled agent registry no longer lists bb and the daemon starts without it
  • Webhook tunnel still maps a Bitbucket webhook payload to a signal

Known failures

Two eval suites fail on this branch, both unrelated to this change (it only removes a bundled agent — no path to chat or decision-timer behavior):

  • chat-attachments — all 16 cases fail with Chat POST 404: Workspace not found, a harness setup failure rather than a model regression.
  • promptfooconfig — 1 case, request-user-decision-expire, a decision-expiry timing eval.

The bb agent is being retired. Removing it from the bundled-agents
registry so it no longer ships in the daemon or appears in discovery
surfaces, and dropping the @coderabbitai/bitbucket dependency it was
the sole consumer of. The webhook-tunnel Bitbucket provider stays —
a user-space agent can still consume those signals.

## Progress
- Task: rip out the Bitbucket bundled agent
- Decisions: kept the webhook-tunnel Bitbucket provider and the jira
  agent's illustrative bitbucket.org URL per user direction; scope
  limited to the bundled agent and its direct wiring/deps
- Key Learnings: bb/agent.ts shared vcs/schemas.ts and
  shared/operation-parser.ts with the gh/hubspot/jira agents, so those
  helpers stay; THIRD_PARTY_LICENSES.md must also drop the transitive
  openapi-fetch@0.14.1 that only @coderabbitai/bitbucket pulled in
- Files: packages/bundled-agents/src/bb/*, index.ts, registry.ts,
  package.json, deno.lock, THIRD_PARTY_LICENSES.md, Dockerfile,
  .env.example, agent-playground signal-row/operation-form/+page
@basedfriday basedfriday added the do-not-merge Work in progress / not ready to merge label May 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge Work in progress / not ready to merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant