Skip to content

Buzz for Devin 0.4.25 alpha 2 (source only)

Pre-release
Pre-release

Choose a tag to compare

Buzz for Devin alpha 2 is an unofficial, source-only technical preview for
builders who want to test Cognition's official Devin CLI in Buzz before the
focused upstream preset merges.

There are no application binaries attached to this release. Clone and run the
reviewed source; do not redistribute an unsigned local build.

Start here

git clone https://github.com/fenner888/BuzzforDevin.git
cd BuzzforDevin
git checkout buzz-for-devin-v0.4.25-alpha.2
./scripts/run-buzz-for-devin-source.sh

Read the complete macOS, Linux, and Windows prerequisites and acceptance
checklist:

https://github.com/fenner888/BuzzforDevin/blob/buzz-for-devin-v0.4.25-alpha.2/docs/buzz-for-devin-builders.md

Install and authenticate the official Devin CLI using Cognition's documentation:

https://docs.devin.ai/cli

Platform status

  • Apple Silicon macOS: verified technical alpha; full CI, source
    preparation, isolated package lifecycle, and live Devin ACP acceptance pass.
  • Intel macOS: source preview available; fork-specific live acceptance
    pending.
  • Linux x86_64 / ARM64: source preview and CI compilation available; live
    Devin ACP acceptance pending.
  • Windows x86_64 MSVC: source preview and Windows CI pass; live Devin ACP
    acceptance pending.

Experimental means the source path is available for builders. It does not mean
this fork publishes or supports a platform installer.

Safety boundary

  • Uses Cognition's official devin acp command and each builder's own account.
  • Does not inspect, copy, or modify Devin credentials or configuration.
  • Keeps one-worker and owner-only defaults.
  • Keeps permission decisions explicit and fail closed.
  • Does not enable a bypass or persistent auto-approval mode.
  • Does not claim model switching, Fusion, fan-out, Outposts, cloud handoff, or
    cloud Devin parity.
  • Does not enable an updater or use signing credentials.

Provenance

The first CI attempt's backend integration job could not reach Docker Hub. Its
failed-job-only rerun pulled the services successfully and passed the full
backend integration and security test sequence. All final required jobs are
green.