- TypeScript 70.2%
- Rust 25.3%
- JavaScript 1.5%
- PowerShell 0.9%
- Shell 0.8%
- Other 1.2%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
e25424da3f## Summary Goose only reads `DATABRICKS_HOST` from `config.yaml` when the env var is unset, so the value Berd injects from the shell and runtime config always shadowed a user's goose config. Now, when the user's goose config has a valid `DATABRICKS_HOST`, Berd removes the env var before it spawns `goose serve`. Goose then reads the host from its config file. Berd removes the var instead of copying the value in, so goose keeps re-reading the file: settings edits apply live, and the host stays paired with the token stored in the same file. - A value counts as valid if it's an HTTPS URL with no credentials, query, or fragment. Path prefixes are allowed so pass-through proxies work. - If the value is missing or invalid, Berd keeps today's env value and logs a warning. - The override is skipped in E2E mode, and whenever the child would resolve a different config root than Berd (`GOOSE_PATH_ROOT`, `HOME`, `XDG_CONFIG_HOME`, `APPDATA`, `USERPROFILE`), so an isolated goose root never picks up the real user config. Also fixes a flaky `message_search` test: `secure_cache_permissions` could hit ENOENT when a closing SQLite connection deleted its `-wal`/`-shm` files between the `exists()` check and `set_permissions()`. A missing sidecar is now treated as success. ### Related issue N/A ### Testing - New unit tests cover config parsing and validation, the env override, and the config-root guard: `cargo test --lib -- databricks_host config_environment` (7 passed). - The flaky `reopening_after_offline_delete_cannot_preserve_prior_generation_rows` test failed 1 in 30 runs before the fix and passed 60 of 60 after. - The pre-push hooks passed (fmt-check, check, tauri-check, clippy). 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
| .agents | ||
| .cargo | ||
| .github | ||
| .vscode | ||
| bb-cli | ||
| bin | ||
| crates/builderbot-auth | ||
| distro | ||
| docker/linux | ||
| docs | ||
| LAWS | ||
| public | ||
| release-agents | ||
| resources | ||
| scripts | ||
| sdk | ||
| skills | ||
| src | ||
| src-tauri | ||
| tests | ||
| tools | ||
| .gitattributes | ||
| .gitignore | ||
| acp-tools.lock.json | ||
| AGENTS.md | ||
| app-icon.png | ||
| biome.json | ||
| CHANGELOG.md | ||
| CLAUDE.md | ||
| CODE_OF_CONDUCT.md | ||
| CODEOWNERS | ||
| CONTRIBUTING.md | ||
| DESIGN.md | ||
| doctor.config.ts | ||
| goose-backend.lock.json | ||
| GOVERNANCE.md | ||
| index.html | ||
| justfile | ||
| lefthook.yml | ||
| LICENSE | ||
| node-runtime.lock.json | ||
| package.json | ||
| playwright.config.ts | ||
| playwright.table-overflow.config.ts | ||
| pnpm-lock.yaml | ||
| pnpm-workspace.yaml | ||
| postcss.config.js | ||
| PRODUCT.md | ||
| README.md | ||
| renovate.json | ||
| rust-toolchain.toml | ||
| SECURITY.md | ||
| TELEMETRY.md | ||
| tsconfig.json | ||
| tsconfig.node.json | ||
| vite.config.ts | ||
| vitest.app-e2e.config.ts | ||
| vitest.config.ts | ||
| vitest.release-scripts.config.ts | ||
Berd
Berd is an open-source desktop app for working with AI agents. It is built with
Tauri 2 and React 19 and talks to the upstream Goose backend through the ACP
WebSocket served by a goose serve sidecar.
The repository builds a general-purpose public distribution. Organizations can also create enterprise distributions by supplying managed provider settings, private resources, and release infrastructure through the repository's distribution seams without adding private material to the public source tree.
Getting started
just setup
just dev
just setup installs pnpm dependencies, builds the vendored @aaif/goose-sdk,
and prepares the Goose backend pinned by goose-backend.lock.json in your
platform cache directory. just dev reuses that stamped pinned binary and fails
if the lockfile commit no longer matches the cached build.
If you already have an upstream Goose binary you want to test, set
GOOSE_BIN=/path/to/goose before running just dev; that is an explicit local
override and bypasses the managed pinned checkout.
To bump the default Goose backend, update the lockfile in a PR:
scripts/update-goose-backend-lock.sh main # or a tag/branch/sha
just goose-sync # fetch/build the new pinned commit
Bundling and distributions
Tauri bundles the Goose backend as an external sidecar. By default, just bundle
stages the pinned managed Goose binary from goose-backend.lock.json and then
runs pnpm tauri build:
just bundle
You can stage an explicit local binary with
GOOSE_BIN=/path/to/goose just stage-sidecar. Staging creates
src-tauri/binaries/goosed-<rust-host-triple>, matching the
"externalBin": ["binaries/goosed"] entry in src-tauri/tauri.conf.json.
The public build is self-contained and does not require private package registries or enterprise credentials. Enterprise distributors may overlay private agents, runtime configuration, optional companion tools, update channels, and signing or publishing infrastructure in their own private build orchestration.
Optional companion CLI
Berd includes a distribution seam for bundling an optional companion CLI as an app resource. The public app does not require a private CLI package; enterprise distributors can provide and package their own implementation while retaining the normal Berd build and validation flow.
Public Agent Skills
Berd publishes portable Agent Skills under skills/. These
can be installed independently of the Berd app and are separate from the
contributor workflows under .agents/skills/ and the starter skills bundled
under distro/skills/.
The first published skill, buzz-handoff, brings
Buzz channel or thread context into a private agent conversation and can send an
explicitly approved reply through the public Buzz CLI.
Adding an experiment
Experiments are user-local preferences for unstable UI or workflow behavior.
Untouched experiments follow the global auto-enable setting, which defaults on
in dev builds and off in production builds. Use
.agents/skills/experimental-features/SKILL.md for the current workflow,
registry contract, storage rules, Tauri guardrails, and test coverage.
Participating
Berd is built by a small team at Block, in the open. You can read the source, build it, and fork it freely — but we don't accept pull requests from outside authorized repository collaborators, and outside PRs are closed automatically.
The way to participate is to open a well-formed issue. A bug report we can reproduce is worth more to us than a patch, because it's the part we can't do ourselves. CONTRIBUTING.md spells out exactly what each kind of issue needs; the issue forms require it.
Filing one? Hand this to your coding agent:
Read https://raw.githubusercontent.com/block/berd/main/CONTRIBUTING.md
and help me file a Berd issue. Interview me for anything the guide
requires that I haven't given you, and tell me if what I'm reporting
is actually two separate issues.
Please also review the Code of Conduct and Security Policy. Never report a security vulnerability as a public issue.
Useful commands
just check— Biome, design-system, i18n, contract, and type checksjust test— unit and component testsjust tauri-check— Rust type check with sidecars disabledjust clippy— Rust lint with warnings deniedjust bundle— stage the pinned Goose backend and runpnpm tauri build