| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| README.md | 2026-06-30 | 11.6 kB | |
| v2.0.0 source code.tar.gz | 2026-06-30 | 4.8 MB | |
| v2.0.0 source code.zip | 2026-06-30 | 6.4 MB | |
| Totals: 3 Items | 11.3 MB | 2 | |
AI Features Highlights
v2 marks Bit's first-class commitment to agentic developer workflows. Out of the box, bit init now wires up AI agents with everything they need: a hosted MCP connection to Bit Cloud, editor-specific instruction files written to the paths each tool auto-loads, and CLI output tuned for machine parsing. AI agents working in a Bit workspace have the right tools, context, and commands to understand component state, run builds, inspect CI results, and act on failures — without any manual configuration.
-
Bit Cloud MCP — zero-config setup —
bit initnow automatically writes a.mcp.jsonat the workspace root pointing to the hosted Cloud MCP athttps://mcp.bit.cloud/mcp. Auto-picked up by Claude Code, Cursor, and other MCP-aware editors with zero extra configuration. Idempotent: merges into any existing.mcp.json, preserving other server entries (#10379) -
Per-editor agent instructions written on
bit init— the new--agent [type]flag (options:claude,cursor,copilot; default:AGENTS.md) writes the right config and rules to the auto-loaded path for each tool: -
Claude Code writes
.claude/rules/bit.md(auto-loaded per Claude Code memory docs) and.mcp.json - Cursor writes
.cursor/rules/bit.mdcand.cursor/mcp.json - GitHub Copilot writes
.github/instructions/bit.instructions.md -
Non-interactive
bit init(no.git) always writesAGENTS.mdand.mcp.json(#10379) -
bit ripple— CI context for agents — agents can now query Ripple CI directly viabit ripple. The command exposes job listings, per-component build logs, errors, success/failure status, and which components built vs. which didn't — giving agents the full picture of what happened after an export without leaving the terminal or parsing web UIs (#10261, [#10330], [#10443]) -
Agent instructions include
bit ripple— the generated instruction files documentbit ripplein both the common commands section and the publishing workflow, so agents know when and how to use it (#10443) -
AI-agent-friendly CLI output —
bit diffgained structured output flags andbit testproduces a per-component result rollup that agents can parse cleanly (#10307, [#10313]) -
bit initgeneratesAGENTS.md—bit initwrites anAGENTS.mdwith workspace-specific instructions on initialization (#10308) -
Semantic API diff with impact assessment —
bit api diffsurfaces breaking changes and their severity, giving agents the context they need to understand what changed across a component's public API (#10262)
Breaking Changes
Core Environments Upgraded to React 19
Bit's internal UI and all core environments (core-aspect-env, node-babel-mocha, node-typescript-mocha, base-react-env) have been upgraded from React 17 to React 19 (#10295, [#10385]). The Bit UI itself has been migrated to the new createRoot API and React 19 compatible dependencies.
What this means for you: If your components use one of Bit's built-in core environments, they will now resolve React 19 as a peer dependency. Components that rely on React 17-specific behavior or APIs may encounter incompatibilities.
Recommended action: If you are using a Bit core environment directly (e.g. teambit.react/react, teambit.harmony/node), migrate to a custom environment that explicitly declares the React version your components target. Custom environments give you full control over peer dependency versions and insulate your components from future upgrades in Bit's internals. See the Bit documentation on custom environments for guidance.
New Features
- New workspace minimal mode redesign with improved layout and component breadcrumb support (#10343)
bit internalize— new command to mark components as internal, hiding them by default in the Bit Cloud UI and workspace without removing them from versioning. Supports component patterns,--revert, and--list(#10397)- Lean lane scopes —
bit exporton a lane now skips shipping main-origin history snaps to the lane scope. Lane scopes stay lean; main history remains on the component's home scope and is fetched transparently on demand. Fixes OOM conditions on lanes that have been merging main over time (#10390) bit import --dependencies-depth <n>— limit how deep the import traversal follows transitive dependencies (#10373)bit test <file-path>— run tests for a specific file directly, without needing to know the component ID (#10403)bit switchnow fetches latest by default — no more stale heads after switching lanes (#10381)bit lane merge --squashon diverged components — allow squash-merging even when a component has diverged, with explicit opt-in (#10387)bit ci pr --keep-lane— opt-in mode that reuses the same lane across multiple PR commits, with adopt-on-conflict resolution and automatic recovery from stale remote state (#10388, [#10400], [#10460])bit ci pr --skip-tasksand[skip-tasks]commit token — skip build tasks in CI on demand, either via flag or by including[skip-tasks]in the commit message (#10436)bit ci prskip post-export restore — skip the workspace restore step after export in CI, shaving time off PR builds (#10431)- Opt-in parallel build pipeline — run build environments concurrently with
BIT_BUILD_CONCURRENCY=<n>or thebuild.concurrencyconfig. Default behavior (serial) is unchanged (#10432) bit debug-load <id>— new command that loads a component with tracing and prints the stage/timing tree, extension-merge source table, resolved env, and load issues. Load failures now surface inbit statusinstead of being silently swallowed (#10418)- Capsule auto-prune — bound disk usage of the capsules cache automatically; prunes by age (#10382, [#10408])
bit snap/bit tag --no-lock-deps— skip saving the dependencies graph to the snapshot, useful for CI scenarios where the graph is computed separately (#10383)bit deprecate/bit undeprecatesupport component patterns — run deprecation commands against a pattern likeui/**instead of one component at a time (#10440)- Deprecated version warnings in the workspace UI — historical deprecated versions now display a warning badge in the component history view (#10450)
BIT_SERVER_HOSToverride — set the environment variable to override the bind address of the local API server (#10394)bitcommands from a git worktree — Bit now detects the worktree root and maps it to the correct workspace, so commands work from any worktree checkout (#10405)- Lane
updateDependentsrearchitected — per-component cascade diverge for hidden entries: workspace snaps now cascade to hidden update-dependents automatically,bit statussplits staged vs hidden-pending, andbit exportsurfaces exported cascade entries separately (#10358) - Live controls panel reworked — improved layout and theme/font handling in portaled UI (#10384)
Improvements
bit export: improve error message when a scope doesn't exist (#10257)bit install: throw a clearOutsideWorkspaceErrorwhenbit linkis run outside a workspace (#10375)bit doctor: exclude previous doctor-results archives from the new archive (#10372)
Performance
- Benchmark harness and aggregate load profiler added as groundwork for the component-loading redesign (#10429)
- Capsule installs now run sequentially per-capsule instead of all at once, reducing contention on shared resources (#10457)
Bug Fixes
- Fix an issue where
rootComponentsmode left stale links in.bit_roots(#10356) - Fix an issue where package paths with a single segment had trailing slashes stripped incorrectly (#10366)
- Fix an issue where scope object refs were not validated before being joined into a file path (#10367)
- Fix an issue where the Code tab did not show live updates when a workspace component changed (#10368)
- Fix an issue where
bit import <id>resolved to a lane head instead of main head for hiddenupdateDependents(#10370) - Fix an issue where object refs in
/scope/fetchwere not validated (#10371) - Fix an issue where saved dependency graphs referenced unpublishable snaps and could not be loaded (#10380)
- Fix an issue where preview props did not re-render on change (#10392)
- Fix an issue where
bit builddidn't check out the latest version before building (#10393) - Fix an issue where cross-scope lane
updateDependentswere routed to the wrong scope (#10395) - Fix an issue where a component was falsely shown as modified due to
extensionDependenciesordering (#10396) - Fix an issue where
--keep-lanemode could fail when the remote lane was stale (#10400) - Fix an issue where the
--tokenflag value was logged in debug output and analytics (#10402) - Fix an issue where merging main into a lane re-imported the main history gap unnecessarily (#10404)
- Fix an issue where
npm configwas run via a shell, allowing potential command injection (#10407) - Fix an issue where preview generation failed for envs without a compiler (#10406)
- Fix an issue where the sign task did not persist the dependency graph from capsules (#10410)
- Fix an issue where
mdx-multi-compilerpulled in an external tsconfig dependency (#10420) - Fix an issue where remote lane scope/name were not validated, allowing path traversal writes (#10414)
- Fix an issue where hard linking across devices failed with
EXDEVinstead of falling back to copy (#10419) - Fix an issue where the preview server could serve files outside the workspace via path traversal (#10424)
- Fix an issue where
bit diffreported phantom peer dependency changes for component-level peers (#10437) - Fix an issue where deprecated component logs leaked into workspace output (#10438)
- Fix an issue where staged deprecation was not reflected in
bit log(#10441) - Fix an issue where resolution-less workspace-component snaps were included in the generated lockfile (#10439)
- Fix an issue where the deprecated range was missing from
bit deprecateoutput (#10442) - Fix an issue where installing a component that depends on an unpublished update-dependent gave no clear error (#10427)
- Fix an issue where
bit removeon a lane left deleted-on-lane deps at stale versions in the workspace policy (#10444) - Fix an issue where resolving a deleted-on-lane dep version caused a network hang (#10447)
- Fix an issue where cyclic seeder dependencies triggered unnecessary registry fetches (#10449)
- Fix an issue where unmodified deps were rebuilt from source when their package had never been published (#10451)
- Fix an issue where snap-versioned cyclic deps were not isolated and linked correctly during aspect isolation (#10453)
- Fix an issue where
@types/*packages were incorrectly included as component peer dependencies (#10186) - Fix an issue where
bit ci pr --keep-lanecould fail because main's head objects were not fetched before config sync (#10460)
Internal
- Replace ESLint with Oxlint for repo linting (already shipped in v1.13.177; carried forward) (#10324)
- Remove dead binary-build scripts and unused config files (#10417)
- Upgrade
@mdx-js/reactto v3 (required for React 19 compatibility) (#10412) - Update dependencies (#10377, [#10411], [#10433], [#10448])