brindle 0.5.3__tar.gz → 0.5.5__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- {brindle-0.5.3 → brindle-0.5.5}/PKG-INFO +56 -160
- {brindle-0.5.3 → brindle-0.5.5}/README.md +55 -159
- {brindle-0.5.3 → brindle-0.5.5}/pyproject.toml +3 -1
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/agents.py +6 -3
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/autopilot.py +13 -18
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/builtin_agents/developer-local.md +1 -1
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/check_scope.py +109 -11
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/cli.py +24 -37
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/config.py +12 -3
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/daemon/routes_actions.py +4 -11
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/daemon/routes_read.py +29 -9
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/daemon/session_review.py +2 -2
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/db.py +17 -1
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/gates.py +6 -5
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/model_access.py +1 -1
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/pipeline.py +5 -2
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/pro/account.py +5 -4
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/providers.py +1 -1
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/service/sessions.py +3 -7
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/sessions.py +6 -5
- {brindle-0.5.3 → brindle-0.5.5}/.gitignore +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/LICENSE +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/SCHEDULE-A +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/__init__.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/__main__.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/account.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/airgap.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/antigravity.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/assembler.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/assets/braid_dark.png +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/assets/braid_light.png +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/budget.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/builtin_agents/__init__.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/builtin_agents/backend-auditor.md +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/builtin_agents/coordinator.md +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/builtin_agents/developer-codex.md +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/builtin_agents/developer-fable.md +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/builtin_agents/developer-gemini.md +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/builtin_agents/developer-heavy.md +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/builtin_agents/developer-light.md +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/builtin_agents/developer-opencode.md +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/builtin_agents/developer-sonnet.md +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/builtin_agents/developer.md +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/builtin_agents/qa.md +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/builtin_agents/reviewer-codex.md +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/builtin_agents/reviewer-gemini.md +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/builtin_agents/reviewer-local.md +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/builtin_agents/reviewer-opencode.md +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/builtin_agents/reviewer.md +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/builtin_agents/subagent.md +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/builtin_agents/supervisor.md +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/builtin_rules/__init__.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/builtin_rules/security/backend.md +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/builtin_rules/style/minimal-diff.md +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/builtin_rules/tests/only.md +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/bus.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/ci_adapters.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/ci_client.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/ci_federation.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/ci_hosts.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/clone.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/cloud_credential.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/cloud_login.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/codemap.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/codemap_docs.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/codex_hook.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/company_identity.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/company_login.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/conflicts.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/connections.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/coordinator.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/cost.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/cost_estimate.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/cull.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/daemon/__init__.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/daemon/api-schema.json +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/daemon/app.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/daemon/auth.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/daemon/events.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/daemon/holds.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/daemon/lifecycle.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/daemon/peer.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/daemon/routes_org_permissions.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/daemon/schema.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/daemon/terminal.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/debuglog.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/demo.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/detect.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/doctor.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/entry.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/escapes.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/events.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/git.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/guardrails.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/history.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/identity_lock.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/inbox.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/kb.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/key_check.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/keys_cmds.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/keystore.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/knowledge.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/launch_health.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/learned_rules.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/learning.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/legacy.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/local_setup.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/login_pause.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/mcp_server.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/model_availability.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/native/__init__.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/native/catalog.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/native/client.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/native/loop.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/native/lsp.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/native/permissions.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/native/runner.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/native/serve.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/native/tools.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/opencode.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/org_permissions.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/pane_auth.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/permission_asks.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/permission_grants.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/permission_groups.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/permission_routing.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/permissions.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/picker.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/plugins.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/policy.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/pool.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/preflight.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/pricing.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/pro/__init__.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/pro/_files.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/pro/audit_chain.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/pro/audit_export.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/pro/auth.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/pro/brief_learning.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/pro/cost_centers.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/pro/credentials.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/pro/features.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/pro/keys.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/pro/learning.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/pro/license.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/pro/loopback.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/pro/managed_models.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/pro/org_profiles.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/pro/orgkey.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/pro/rollout.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/pro/route_health.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/pro/settings_sync.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/pro/status.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/pro/team_events.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/pro/team_policy.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/procs.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/profiles.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/prompt_answer.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/provider_homes.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/providers_install.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/quota.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/repo_cmds.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/repos.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/rewind.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/rule_checks.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/savings.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/scratch.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/secrets.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/self_serve.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/service/__init__.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/service/dto.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/service/errors.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/service/inbox.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/service/permissions.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/service/routing.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/services.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/sidebar_follow.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/sidebar_logo.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/signin_pause.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/status_cache.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/tasks.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/tmux.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/updates.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/upgrade.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/usage.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/view.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/wake.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/watch.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/watch_costs.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/web/__init__.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/web/chat.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/web/dashboard.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/web/diff.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/web/server.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/web/static/app.js +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/web/static/index.html +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/worker_models.py +0 -0
- {brindle-0.5.3 → brindle-0.5.5}/src/brindle/workspaces.py +0 -0
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.4
|
|
2
2
|
Name: brindle
|
|
3
|
-
Version: 0.5.
|
|
3
|
+
Version: 0.5.5
|
|
4
4
|
Summary: Run coding agents in parallel, each on its own git branch, with a supervisor that delegates, reviews, and merges
|
|
5
5
|
Project-URL: Homepage, https://pawdelta.com/brindle/
|
|
6
6
|
Project-URL: Documentation, https://pawdelta.com/brindle/docs/recommended-use
|
|
@@ -70,7 +70,7 @@ service ([details](#license)).
|
|
|
70
70
|
- **Delegation built in.** Agents get a `brindle` MCP server: `assign` work to
|
|
71
71
|
parallel workers with the files they'll touch and what they depend on, `handoff`
|
|
72
72
|
and wait, `send_message`, then review and merge without spending the supervisor's turns.
|
|
73
|
-
- **Walk away.**
|
|
73
|
+
- **Walk away.** brindle keeps going until every milestone is verified, pauses
|
|
74
74
|
at your usage limit and resumes after the reset, and asks you only when it
|
|
75
75
|
needs a decision. Quit and `brindle continue` later; workers resume too.
|
|
76
76
|
- **Any model, including local ones.** Claude Code, Codex, Google Antigravity, or
|
|
@@ -158,8 +158,7 @@ switch windows or sessions; you can still move it manually or use `brindle attac
|
|
|
158
158
|
to choose a brindle window.
|
|
159
159
|
|
|
160
160
|
**Sidebar keys.** `?` shows them in the sidebar too. ◆ marks an agent that needs
|
|
161
|
-
you: stuck on a prompt
|
|
162
|
-
worker whose branch is waiting for your review. Under autopilot, a reported worker shows
|
|
161
|
+
you: stuck on a prompt or a supervisor with a question. A reported worker shows
|
|
163
162
|
a dim ◇ instead, because the supervisor reviews it.
|
|
164
163
|
|
|
165
164
|
**Copying chat text.** Drag with the mouse in the chat: the selection stays inside
|
|
@@ -263,7 +262,7 @@ things itself instead of starting workers.
|
|
|
263
262
|
2. **Give it a goal with checks.** For anything bigger than one sitting, tell the
|
|
264
263
|
supervisor what "done" means in commands (a test file, `npm test`, a build), or
|
|
265
264
|
write `.brindle/goals.md` yourself. Milestones with real checks are what let
|
|
266
|
-
|
|
265
|
+
brindle keep going without you and stop when the work is actually done.
|
|
267
266
|
3. **Set `checks` in `.brindle/config.json`** (usually your full test suite) so no
|
|
268
267
|
branch merges red, and a `setup` if new worktrees need `npm install` or similar.
|
|
269
268
|
4. **Watch the sidebar, not every window.** It flags agents waiting on you (◆);
|
|
@@ -281,9 +280,9 @@ task to one area of the code with its own test command, and let the supervisor r
|
|
|
281
280
|
to `max_agents` workers at once. Use a cheaper profile (see [Cheap workers](#cheap-workers))
|
|
282
281
|
for mechanical edits and a Codex reviewer for a second model's opinion.
|
|
283
282
|
|
|
284
|
-
##
|
|
283
|
+
## Driving toward a verified goal
|
|
285
284
|
|
|
286
|
-
`brindle`
|
|
285
|
+
`brindle` drives the supervisor toward a verified goal. Tell it what we're building,
|
|
287
286
|
or put the goal in `.brindle/goals.md`, and it works like a project manager:
|
|
288
287
|
|
|
289
288
|
1. **Goal and milestones.** The goal is split into milestones, and each one has
|
|
@@ -309,16 +308,18 @@ or put the goal in `.brindle/goals.md`, and it works like a project manager:
|
|
|
309
308
|
approves it, or (`approved=false`, with feedback) sends it back for a
|
|
310
309
|
revision. For Claude workers brindle's PreToolUse hook refuses Edit, Write
|
|
311
310
|
and NotebookEdit until the plan is approved; other CLIs are only told to
|
|
312
|
-
wait.
|
|
311
|
+
wait. brindle doesn't count a worker waiting on approval as stalled, and
|
|
313
312
|
reminds the supervisor about plans awaiting a decision.
|
|
314
313
|
3. **Gated merges.** A branch merges only when everything is committed, a
|
|
315
314
|
reviewer agent has approved that exact commit, your pre-commit hooks pass,
|
|
316
315
|
and your `checks` pass. brindle runs these itself before `merge_workspace`,
|
|
317
316
|
and caches a clean commit's passing result so it isn't re-run for every
|
|
318
|
-
review and merge attempt at the same sha. `request_review`
|
|
319
|
-
|
|
320
|
-
|
|
321
|
-
|
|
317
|
+
review and merge attempt at the same sha. `request_review` returns at
|
|
318
|
+
once. With `checks` configured, brindle runs them first, in the
|
|
319
|
+
background, and starts the reviewer when they finish, with a pass/fail
|
|
320
|
+
summary (output only for failures) in its prompt, instead of asking the
|
|
321
|
+
reviewer to run the whole suite itself. With no `checks`, the reviewer
|
|
322
|
+
starts right away.
|
|
322
323
|
`request_review` picks the reviewer profile itself unless you pass one: an
|
|
323
324
|
explicit `profile` argument, else `review_profile` in the repo config,
|
|
324
325
|
else `reviewer` (the repo's `reviewer` setting). brindle never picks a
|
|
@@ -353,7 +354,7 @@ for byte as you wrote it. Since `goals.md` may be committed, it stays free of
|
|
|
353
354
|
session data: no agent or session ids, check output, notes, usage or
|
|
354
355
|
questions ever go in. A status line is information only: a new session
|
|
355
356
|
starts every milestone as pending and re-runs the checks, never trusting it.
|
|
356
|
-
A session stops writing when it's handed over
|
|
357
|
+
A session stops writing when it's handed over or paused,
|
|
357
358
|
or once its goal was replaced from the chat. From a linked worktree, it writes
|
|
358
359
|
the `goals.md` it loaded (the main checkout's), never another session's. A
|
|
359
360
|
write that fails never fails the check.
|
|
@@ -363,15 +364,14 @@ A new session takes a hand-written `goals.md` over by moving it to its own
|
|
|
363
364
|
its deletion is left for you to commit or restore; brindle doesn't count it as
|
|
364
365
|
an uncommitted change, so it never blocks a merge or a milestone's check.
|
|
365
366
|
|
|
366
|
-
`brindle
|
|
367
|
-
|
|
368
|
-
|
|
369
|
-
starts without it.
|
|
367
|
+
`brindle goal` shows progress and `brindle goal check` runs the checks now.
|
|
368
|
+
Pause the session to stop it. The deprecated `--autopilot`/`--no-autopilot`
|
|
369
|
+
flags and the `autopilot` config key are ignored: goal driving is always on.
|
|
370
370
|
|
|
371
|
-
When your Claude usage reaches `usage_limit`,
|
|
371
|
+
When your Claude usage reaches `usage_limit`, brindle pauses for usage: its
|
|
372
372
|
running Claude workers stop (worktrees, branches, queued messages and sessions
|
|
373
373
|
are kept) and the sidebar says "paused for usage until <time>". Once the usage
|
|
374
|
-
window resets, brindle restarts those workers on its own,
|
|
374
|
+
window resets, brindle restarts those workers on its own, resumes goal driving
|
|
375
375
|
again and tells the supervisor what it resumed. Speaking to the supervisor
|
|
376
376
|
doesn't end the pause.
|
|
377
377
|
|
|
@@ -391,9 +391,9 @@ your own status line prints, so what you see doesn't change.
|
|
|
391
391
|
| `brindle new BRANCH [-b BASE] [-p PROMPT] [--no-agent]` | worktree + branch + a supervisor in it |
|
|
392
392
|
| `brindle continue [ID]` / `brindle -c` | resume a paused session (default: the most recent) |
|
|
393
393
|
| `brindle sessions` / `brindle prune` | list paused sessions / apply retention rules, remove merged or missing worktrees, close stale stopped agents whose work is merged or gone, and remove leftover tmux sessions |
|
|
394
|
-
| `brindle start [-p PROMPT] [--no-watch] [
|
|
394
|
+
| `brindle start [-p PROMPT] [--no-watch] [-b BRANCH] [-w PATH]` | the same, with options; `-b`/`-w` run it in that branch's worktree (created if needed, or the one you already made), which gets the repo's `.brindle` config |
|
|
395
395
|
| `brindle handover --to BRANCH\|PATH [-n NOTE]` | hand the session to a new supervisor there: goal and milestones, workers, queued tasks and your note move across; the old one is paused |
|
|
396
|
-
| `brindle
|
|
396
|
+
| `brindle goal [check]` | the goal's progress; run the checks now |
|
|
397
397
|
| `brindle audit-decision FINDING [-r RATIONALE]` | record acceptance of an audit finding with rationale so subsequent audits respect it |
|
|
398
398
|
| `brindle delegation [conservative\|balanced\|fast]` | how readily the supervisor delegates: fewest tokens, the default, or quickest |
|
|
399
399
|
| `brindle transfer [REPO] [--from SESSION] [-b BRANCH]` | move a scratch session's work into a real repo |
|
|
@@ -443,7 +443,7 @@ With no `WS` argument, commands act on the workspace you're in.
|
|
|
443
443
|
`brindle web` serves the current session to your browser: workspaces, agents
|
|
444
444
|
and their status, and the goal's milestones with each one's last check. Run
|
|
445
445
|
it from a terminal in the session's tmux session to show that session's
|
|
446
|
-
goal; elsewhere it shows the newest
|
|
446
|
+
goal; elsewhere it shows the newest session
|
|
447
447
|
in the repo. The page refreshes itself every couple of seconds.
|
|
448
448
|
|
|
449
449
|
It listens on `127.0.0.1` only, on a free port (or `--port N`), and prints a
|
|
@@ -475,7 +475,7 @@ knowing them helps when you tell the supervisor how to work.
|
|
|
475
475
|
| `approve_plan` | supervisor | approve a worker's plan, or send it back with feedback (`approved=false`) |
|
|
476
476
|
| `answer_permission` | supervisor | allow, deny or escalate (with a reason) a worker's permission ask before the person sees it |
|
|
477
477
|
| `complete_subagent` | supervisor | record the result of a `subagent`-profile task |
|
|
478
|
-
| `set_goal` / `get_progress` / `check_milestone` | supervisor |
|
|
478
|
+
| `set_goal` / `get_progress` / `check_milestone` | supervisor | the session's goal, its progress, and running the checks |
|
|
479
479
|
| `record_audit_decision` | supervisor | record acceptance of an audit finding with rationale so subsequent audits respect it |
|
|
480
480
|
| `who_is_working` | supervisor | other sessions in this repo: their goals and running tasks, optionally only those matching `paths` or a `query` |
|
|
481
481
|
| `record_decision` / `decisions` | supervisor (`decisions` also workers) | record a durable decision about the system / list the accepted ones that apply |
|
|
@@ -544,7 +544,7 @@ Set in `~/.brindle/config.json`, `.brindle/config.json` or `config.local.json`
|
|
|
544
544
|
take the task, its goal or the month over a limit (a task's cost is estimated
|
|
545
545
|
from this repo's finished tasks on that profile, else a typical token mix at
|
|
546
546
|
list prices), brindle skips that candidate and uses the next cheaper one. If
|
|
547
|
-
none fits it refuses the assign, says why and
|
|
547
|
+
none fits it refuses the assign, says why and asks you. A
|
|
548
548
|
profile you name yourself is never second-guessed. Running workers are
|
|
549
549
|
reported to the supervisor at 80% of `task_usd` and again at 100%; set
|
|
550
550
|
`"stop": true` to close a worker at 100% instead of only warning. Without the
|
|
@@ -633,7 +633,7 @@ brindle coordinator stop # close it and turn it off for this che
|
|
|
633
633
|
brindle keeps one place (`~/.brindle/quota.json`) that knows how close each
|
|
634
634
|
provider is to its subscription limit, and shows a note per provider that has
|
|
635
635
|
data (e.g. `Codex at 82% of its weekly limit, resets Thu 9:00am`) in `assign`
|
|
636
|
-
replies, `get_progress`, the sidebar's
|
|
636
|
+
replies, `get_progress`, the sidebar's goal block and `brindle doctor`.
|
|
637
637
|
It only uses what the CLIs write locally, and never reads a CLI's login
|
|
638
638
|
token or auth files or calls a provider's servers:
|
|
639
639
|
|
|
@@ -666,16 +666,16 @@ A linked git worktree you made yourself doesn't have the git-ignored parts of
|
|
|
666
666
|
}
|
|
667
667
|
```
|
|
668
668
|
|
|
669
|
-
|
|
669
|
+
Goal driving, merge gates and cleanup:
|
|
670
670
|
|
|
671
671
|
| Key | Default | |
|
|
672
672
|
|---|---|---|
|
|
673
|
-
| `autopilot` | `true` | start the supervisor with autopilot on |
|
|
674
673
|
| `claude_permission_mode` | `"default"` | the `--permission-mode` for Claude Code sessions whose profile sets no `permission_mode`; the default holds permission requests for the brindle app, set `"auto"` to opt into auto mode. Only read from `~/.brindle/config.json` |
|
|
675
674
|
| `auto_update` | `false` | run `uv tool upgrade brindle` in the background at session start when PyPI has a newer version; restart to use it. Can also be set in `~/.brindle/config.json` for every repo |
|
|
676
675
|
| `scoped_checks` | unset (acts as `"off"`) | `"infer"` narrows a bare pytest check (`pytest ...`, `python -m pytest ...`, `uv run pytest ...`, options only) on a worker's branch to the tests `graphify affected` reaches plus the touched test files, when the repo has a stored graph; it runs in full when the mapping fails or `conftest.py`, `pyproject.toml`, `setup.cfg`, `pytest.ini`, `tox.ini` or a lockfile changed. A pytest command that already names test paths (`pytest tests/`) and every other command always run in full. `"off"` narrows nothing. It becomes the default next release; until you set it, brindle tells you once |
|
|
676
|
+
| `scoped_checks_max_files` | `40` | with `scoped_checks`, a worker's branch whose selected tests exceed this many files runs only its own changed test files and each changed module's namesake tests (`tests/test_<module>.py`, `tests/test_<module>_*.py`) instead, and the check output carries a one-line note saying so. The session branch and the full run before a PR (`gates.pr_checked`) always run everything. `0`: no cap |
|
|
677
677
|
| `checks` | `[]` | commands (plain strings) that must pass in a worker's branch before it merges. On a worker's branch every check also gets `BRINDLE_CHANGED_FILES` (the files changed since the branch left its base, one repo-relative path per line) so a script can narrow itself; the supervisor's checkout always runs every check in full (see `scoped_checks` and `brindle/check_scope.py`) |
|
|
678
|
-
| `review` |
|
|
678
|
+
| `review` | required for sessions | require a reviewer's approval before merging |
|
|
679
679
|
| `reviewer` | `"reviewer"` | the agent profile that reviews (a Codex profile gives a second model's view) |
|
|
680
680
|
| `review_profile` | none | force `request_review`'s profile, skipping its automatic cross-model pick (see below) |
|
|
681
681
|
| `pre_commit` | `true` | run [pre-commit](https://pre-commit.com) over the branch, if the repo uses it |
|
|
@@ -683,7 +683,7 @@ Autopilot, merge gates and cleanup:
|
|
|
683
683
|
| `check_timeout` | `900` | seconds each check may take |
|
|
684
684
|
| `check_concurrency` | half the logical cores, at least 2, at most 6 and 2 GB of RAM per run | check runs at once on this machine, across branches; the rest wait their turn (`0`: no cap). A run far past its last duration is reported to the supervisor |
|
|
685
685
|
| `fable_escalation` | on, unless the worker runs on a cloud account (Bedrock, Vertex or Foundry) | retry a failed heavy task once on `developer-heavy` before handing it to you; `true` turns it on for a cloud account, `false` off |
|
|
686
|
-
| `usage_limit` | `90` |
|
|
686
|
+
| `usage_limit` | `90` | brindle stops pushing on at this % of your Claude usage limit |
|
|
687
687
|
| `limit_cooldown_minutes` | `300` for Antigravity | how long a provider that hit its limit counts as unavailable |
|
|
688
688
|
| `graphify` | if the graph is there | point agents at the repo's [graphify](https://github.com/safishamsi/graphify) code map (`false` turns it off) |
|
|
689
689
|
| `graphify_auto_refresh` | `true` | automatically rebuild untracked code maps; `false` disables rebuilds while keeping queries available |
|
|
@@ -815,7 +815,7 @@ probe here; no Claude CLI or synthetic generation request is used for these chec
|
|
|
815
815
|
The real first worker task is sent once. A detached helper inspects its current
|
|
816
816
|
pane five seconds after delivery, so readiness delays do not use up that window.
|
|
817
817
|
Fresh interactive Antigravity chats without a task still receive their profile,
|
|
818
|
-
tool instructions and
|
|
818
|
+
tool instructions and goal context once after readiness; worker
|
|
819
819
|
instructions accompany the actual task in the same delivery.
|
|
820
820
|
For argv tasks, the timer starts at prompt submission or observed CLI readiness,
|
|
821
821
|
after trust/startup handling; readiness timeout does not establish delivery or
|
|
@@ -1079,23 +1079,17 @@ how to use them, and the next step to get the rest:
|
|
|
1079
1079
|
| per-worktree services | Pro | `"services"` in `.brindle/config.json` |
|
|
1080
1080
|
| several repos in one session | Pro | `brindle repo add <path>` |
|
|
1081
1081
|
| settings sync across machines | Pro | `brindle account sync` |
|
|
1082
|
-
| Brindle-CI build fixing (the fix workflow) | Pro | `brindle ci init` |
|
|
1083
1082
|
| learned rules from repeated review findings | Pro | `brindle rules suggest` |
|
|
1084
1083
|
| cost (estimates, budgets, reports) | Pro | `brindle cost report` |
|
|
1085
1084
|
| guardrails (write scope, read scope, env allowlist per profile) | Pro | `write_scope`, `read_scope`, `env_allow` in a profile |
|
|
1086
1085
|
| org policies + audit feed | Team | `brindle account org policy` |
|
|
1087
|
-
| Brindle-CI (fixes builds, issues into verified pull requests, validation) | Team | `brindle ci init` |
|
|
1088
1086
|
| org profile and rule-pack library, pinned so a repo can't loosen it | Team | `brindle account org profiles` |
|
|
1089
1087
|
| org budgets and protected paths | Team | `budget`, `protected_paths` in your org policy (`brindle account org policy`) |
|
|
1090
1088
|
| per-member budgets, pause, and admin messages (sidebar "Messages", the bottom bar, `brindle org messages`) | Team | `brindle org messages [--keep]` lists and marks read the notices your admins sent you; a pause refuses new workers and stops running ones |
|
|
1091
1089
|
| audit log, air-gap | Enterprise | `brindle audit verify`, `"airgap": true` |
|
|
1092
1090
|
| audit export | Enterprise | `"audit_export"` in `~/.brindle/config.json`, `brindle audit ship` |
|
|
1093
1091
|
| managed models | Enterprise | `agent_setup` routes with `enforce`, and `deny_personal_keys`, in your org policy (see "Managed models" below) |
|
|
1094
|
-
|
|
|
1095
|
-
|
|
1096
|
-
`brindle ci init` checks your plan before it changes anything: it refuses
|
|
1097
|
-
without Brindle-CI on the org you're using, and on Pro it sets up only the fix
|
|
1098
|
-
workflow.
|
|
1092
|
+
| cost centers, managed rollout | Enterprise | `brindle cost request`, and `min_version`, required packs and the kill switch in your org policy; admins can also shut down or throttle a member, role or org remotely (it arrives within about a minute) |
|
|
1099
1093
|
|
|
1100
1094
|
```sh
|
|
1101
1095
|
brindle account # paid features: what you have, how to use them, how to get the rest
|
|
@@ -1385,109 +1379,7 @@ brindle audit ship [--force] # send now; exit 1 if a sink
|
|
|
1385
1379
|
brindle audit prune [--repo PATH] [--days N] # prune now (default: retention_days)
|
|
1386
1380
|
```
|
|
1387
1381
|
|
|
1388
|
-
|
|
1389
|
-
|
|
1390
|
-
Brindle-CI (brindle Team; build fixing alone is on Pro) brings brindle into your CI: it fixes broken builds,
|
|
1391
|
-
turns issues into pull requests whose checks it has verified, and reviews pull
|
|
1392
|
-
requests with evidence. It runs on your own CI with your own model keys; the
|
|
1393
|
-
hosted control plane decides what each run does and what it reports. The
|
|
1394
|
-
workflows call these commands:
|
|
1395
|
-
|
|
1396
|
-
- `brindle ci init`: set a repository up in one go (the GitHub App, the secrets,
|
|
1397
|
-
the workflows as a pull request, then a doctor check). Run it inside a
|
|
1398
|
-
checkout of the repository. For Claude it asks whether to use an API key
|
|
1399
|
-
(the `ANTHROPIC_API_KEY` secret) or Anthropic
|
|
1400
|
-
[workload identity federation](https://platform.claude.com/docs/en/manage-claude/wif-reference)
|
|
1401
|
-
(`--credential key|federation` answers without asking). It also creates the
|
|
1402
|
-
`brindle` issue label (label an issue with it to hand it to brindle CI), and
|
|
1403
|
-
commits the workflows on a `brindle/ci-setup` branch, then puts you back on
|
|
1404
|
-
the branch you started on and deletes the local setup branch, so `git pull`
|
|
1405
|
-
after merging the setup pull request is clean (commit or stash your changes
|
|
1406
|
-
first: it refuses to start with uncommitted work). With your own cloud
|
|
1407
|
-
(`--credential bedrock|vertex|foundry`, keyless GitHub OIDC) it can read the
|
|
1408
|
-
IDs from the deployment template's outputs instead of asking:
|
|
1409
|
-
`--from-stack NAME [--region R]` (AWS CloudFormation), `--from-terraform DIR`
|
|
1410
|
-
(Google) or `--from-deployment NAME -g RG` (Azure). They are defaults for
|
|
1411
|
-
`--cloud-var`, which still overrides them, and every ID is format-checked. A
|
|
1412
|
-
missing `aws`, `terraform` or `az` CLI or output is an error that names the
|
|
1413
|
-
`--cloud-var` to pass instead. Vertex AI and Microsoft Foundry are in
|
|
1414
|
-
**preview** (not yet verified end to end): `init` refuses them unless you pass
|
|
1415
|
-
`--preview` or set `BRINDLE_CI_PREVIEW_CLOUDS=1`, and `doctor` marks them
|
|
1416
|
-
`(preview)`. Bedrock is generally available.
|
|
1417
|
-
- `brindle ci doctor`: which provider CLIs and credential names a runner has, and
|
|
1418
|
-
which providers CI may use on this repository. `--models` also makes one tiny
|
|
1419
|
-
call per pinned model and says why any is refused (a quota, a form not filled in).
|
|
1420
|
-
- `brindle ci start`: start a run for an issue, a goal text or a dispatched run,
|
|
1421
|
-
or a validation of a pull request.
|
|
1422
|
-
- `brindle ci run`: run what was started: the supervisor and the result upload,
|
|
1423
|
-
or the pull request's checks and reviews and the evidence upload.
|
|
1424
|
-
- `brindle ci report`: tell the service how the workflow's jobs ended.
|
|
1425
|
-
|
|
1426
|
-
Credential names are reported, never values. CI uses API keys, cloud sign-ins
|
|
1427
|
-
(Bedrock, Vertex, Foundry) or identity federation only: a provider signed in
|
|
1428
|
-
only with a subscription (`CLAUDE_CODE_OAUTH_TOKEN`, a Codex ChatGPT login) is
|
|
1429
|
-
not used, on personal and organization repositories alike. Add an API key
|
|
1430
|
-
secret instead.
|
|
1431
|
-
|
|
1432
|
-
Fix builds only fix the default branch's *required* status checks, and a new
|
|
1433
|
-
repository has none. When the default branch requires none, `brindle ci init`
|
|
1434
|
-
warns and, for each job in your workflows, asks whether to make it required
|
|
1435
|
-
(`--required-check NAME` picks one without asking, `--no-required-check` only
|
|
1436
|
-
warns; run without a terminal, init only makes a check required when
|
|
1437
|
-
`--required-check` names it). It adds the check to the branch's existing protection, or protects the
|
|
1438
|
-
branch with just that check. GitHub only allows branch protection on a private
|
|
1439
|
-
repository with a paid plan; when it refuses, init says how to require the
|
|
1440
|
-
check yourself (Settings > Branches, "Require status checks to pass").
|
|
1441
|
-
|
|
1442
|
-
An Anthropic API key is either a workspace key (scoped to one workspace) or an
|
|
1443
|
-
organization-level key (not scoped to a workspace). An organization-level key
|
|
1444
|
-
needs the workspace in every request, so after the key `brindle ci init` asks for
|
|
1445
|
-
its workspace ID (`wrkspc_...`; leave it blank for a workspace key, or pass
|
|
1446
|
-
`--workspace-id`, default `$ANTHROPIC_WORKSPACE_ID`) and stores it as the Actions
|
|
1447
|
-
variable `ANTHROPIC_WORKSPACE_ID`. The workflow then sets
|
|
1448
|
-
`ANTHROPIC_CUSTOM_HEADERS="anthropic-workspace-id: <id>"`, which reaches every
|
|
1449
|
-
Claude Code process the run starts.
|
|
1450
|
-
|
|
1451
|
-
With identity federation the repository stores no Anthropic key: the workflow
|
|
1452
|
-
exchanges GitHub's OIDC token once for a short-lived Anthropic token, as a
|
|
1453
|
-
Claude Console service account (billed as API, so it is allowed on
|
|
1454
|
-
organization repositories), and gives the job `ANTHROPIC_AUTH_TOKEN`. `brindle
|
|
1455
|
-
ci init` stores the rule, organization, service account and optional workspace
|
|
1456
|
-
IDs as the Actions variables `ANTHROPIC_FEDERATION_RULE_ID`,
|
|
1457
|
-
`ANTHROPIC_ORGANIZATION_ID`, `ANTHROPIC_SERVICE_ACCOUNT_ID` and
|
|
1458
|
-
`ANTHROPIC_WORKSPACE_ID`, from `--rule-id`, `--organization-id`,
|
|
1459
|
-
`--service-account-id` and `--workspace-id` or else asked (defaulting to those
|
|
1460
|
-
environment variables). Without a terminal on stdin, init asks nothing and
|
|
1461
|
-
takes the options and the environment, so it can run unattended; a missing or
|
|
1462
|
-
malformed ID (rule `fdrl_...`, organization a UUID, service account
|
|
1463
|
-
`svac_...`, workspace `wrkspc_...`) stops it before it creates the CI token.
|
|
1464
|
-
The ID options imply `--credential federation` and can't be combined with
|
|
1465
|
-
`--credential key`. Create the federation rule in the Claude Console with
|
|
1466
|
-
subject prefix `repo:<owner>/<name>:*`, the condition
|
|
1467
|
-
|
|
1468
|
-
```text
|
|
1469
|
-
claims.repository == "<owner>/<name>" && claims.workflow_ref.startsWith("<owner>/<name>/.github/workflows/brindle-ci-")
|
|
1470
|
-
```
|
|
1471
|
-
|
|
1472
|
-
audience `https://api.anthropic.com`, and a token lifetime of at least 600
|
|
1473
|
-
seconds. The condition lets only brindle's workflows mint tokens. On pull
|
|
1474
|
-
requests the pull request's own copy of the validate workflow runs, so give
|
|
1475
|
-
write access only to people you trust (forks never get a token). Leave the `ANTHROPIC_API_KEY` secret
|
|
1476
|
-
unset: a key takes precedence (brindle drops an empty one before Claude Code
|
|
1477
|
-
starts).
|
|
1478
|
-
|
|
1479
|
-
A federated token lives at most about ten minutes, however long the rule
|
|
1480
|
-
allows: Anthropic caps it at twice what remains of GitHub's OIDC token. So
|
|
1481
|
-
the run job doesn't rely on the workflow's one exchange: `brindle ci run`
|
|
1482
|
-
fetches a fresh OIDC token and exchanges it again at 70% of each token's
|
|
1483
|
-
life, and lends the current token to the agents through a proxy on the
|
|
1484
|
-
runner's loopback interface. The agents get `ANTHROPIC_BASE_URL` pointing at
|
|
1485
|
-
it and a random per-run secret as `ANTHROPIC_AUTH_TOKEN`; the Anthropic token
|
|
1486
|
-
itself stays in the `brindle ci run` process, and the GitHub token endpoint
|
|
1487
|
-
(`ACTIONS_ID_TOKEN_REQUEST_URL` and its token) is scrubbed before any agent or
|
|
1488
|
-
check starts. If the first exchange fails, the run goes on with the
|
|
1489
|
-
workflow's token as before; `BRINDLE_CI_FEDERATION_REFRESH=0` in the job's
|
|
1490
|
-
environment turns the refresh off.
|
|
1382
|
+
## Cleanup, merging and workspace config
|
|
1491
1383
|
|
|
1492
1384
|
**Closing and cleaning up.** Press `x` on an agent in the sidebar (twice for one
|
|
1493
1385
|
that's still running) or run `brindle close <id>` to stop it and hide it. Stopping means
|
|
@@ -1506,8 +1398,10 @@ removes stale locks and empty worktree folders.
|
|
|
1506
1398
|
**The pipeline.** The slow part of delegating isn't the workers, it's the supervisor's
|
|
1507
1399
|
turns between the stages: report, review, merge, remove, each waiting on a model turn
|
|
1508
1400
|
that carries the whole session's context. So brindle runs those stages itself. When a
|
|
1509
|
-
worker reports, brindle
|
|
1510
|
-
|
|
1401
|
+
worker reports, brindle gets the branch reviewed at once: with `checks` configured it
|
|
1402
|
+
runs them first, in the background, and starts the reviewer when they finish, with
|
|
1403
|
+
their results in its prompt (with no `checks`, the reviewer starts right away). When
|
|
1404
|
+
the reviewer approves and the checks pass, brindle merges the branch,
|
|
1511
1405
|
removes the worktree, and sends the supervisor one message with the worker's report
|
|
1512
1406
|
and the review. Findings go straight back to the worker to fix (`review_rounds`
|
|
1513
1407
|
times) before they reach the supervisor, and anything the pipeline can't settle (a
|
|
@@ -1530,11 +1424,13 @@ merges. Conflicts in `protected_paths` (migrations, lockfiles, generated code) a
|
|
|
1530
1424
|
never handed to a worker: the supervisor gets them as "needs you".
|
|
1531
1425
|
|
|
1532
1426
|
**The completion audit.** A milestone's check can pass without the milestone being
|
|
1533
|
-
done: the
|
|
1534
|
-
passes,
|
|
1535
|
-
|
|
1536
|
-
|
|
1537
|
-
|
|
1427
|
+
done: the check tests the wrong thing, or the deliverable was never built. So when
|
|
1428
|
+
every milestone passes, brindle doesn't call the goal reached yet. A read-only
|
|
1429
|
+
reviewer audits everything since the goal was set against the goal and each
|
|
1430
|
+
milestone, looking for deliverables that are missing, stubbed out or unhandled. It
|
|
1431
|
+
trusts the passing checks and doesn't debate how deep the tests go. Only its
|
|
1432
|
+
approval of that commit finishes the goal. If it finds gaps, the supervisor gets
|
|
1433
|
+
them as a message and keeps working until a fresh audit approves.
|
|
1538
1434
|
`"goal_audit": false` turns it off.
|
|
1539
1435
|
|
|
1540
1436
|
**Spending fewer tokens.** Workers run only the tests that cover their change while
|
|
@@ -1582,7 +1478,7 @@ commands around the team's list. `~/.brindle/config.json` holds your own default
|
|
|
1582
1478
|
for every repo (any key except the command lists, like `delegation` or
|
|
1583
1479
|
`sidebar`); a repo's two files override it. With brindle Pro or higher, those
|
|
1584
1480
|
preferences (`delegation`, `sidebar`, `message_delivery`, `pr_footer`,
|
|
1585
|
-
`delete_merged_branches`, `max_agents`, `
|
|
1481
|
+
`delete_merged_branches`, `max_agents`, `plan_first`, `stale_after`,
|
|
1586
1482
|
`usage_limit`, `review_rounds`) sync across your machines (last change wins; nothing
|
|
1587
1483
|
else in the file leaves the machine); `brindle account sync` syncs now.
|
|
1588
1484
|
|
|
@@ -1665,7 +1561,7 @@ it's signed in without a plan that includes it, is reported to its supervisor.
|
|
|
1665
1561
|
| Provider | Key login (environment variables) |
|
|
1666
1562
|
|---|---|
|
|
1667
1563
|
| `claude` | yes: `ANTHROPIC_API_KEY`, `ANTHROPIC_AUTH_TOKEN`, `CLAUDE_CODE_OAUTH_TOKEN`, or Bedrock/Vertex/Foundry (`CLAUDE_CODE_USE_BEDROCK`, `CLAUDE_CODE_USE_VERTEX`, `CLAUDE_CODE_USE_FOUNDRY`) |
|
|
1668
|
-
| `codex` | yes: `OPENAI_API_KEY`, `CODEX_API_KEY`. With Codex signed in with ChatGPT (checked on Codex CLI 0.162.0): interactive `codex`, which brindle runs in agent panes, ignores both keys and uses the ChatGPT plan, and only `codex login --with-api-key` switches it to a key; headless `codex exec`
|
|
1564
|
+
| `codex` | yes: `OPENAI_API_KEY`, `CODEX_API_KEY`. With Codex signed in with ChatGPT (checked on Codex CLI 0.162.0): interactive `codex`, which brindle runs in agent panes, ignores both keys and uses the ChatGPT plan, and only `codex login --with-api-key` switches it to a key; headless `codex exec` bills `CODEX_API_KEY` over the login and ignores `OPENAI_API_KEY`. `brindle doctor` and `brindle keys set` say so, and `auth: api_key` on an interactive Codex profile is refused under a ChatGPT login (run `codex login --with-api-key`, or use `auth: subscription`) |
|
|
1669
1565
|
| `antigravity` | `GEMINI_API_KEY`, only with `"modelProvider": "gemini"` in `agy`'s `settings.json` (see [Google Antigravity](#google-antigravity)); otherwise `agy`'s own browser sign-in |
|
|
1670
1566
|
| `opencode` | whatever the model's provider takes (`ANTHROPIC_API_KEY`, `OPENAI_API_KEY`, ...), or `opencode auth login`; its free `opencode/...` models need neither |
|
|
1671
1567
|
|
|
@@ -1690,16 +1586,16 @@ Your org's `deny_personal_keys` (Enterprise) still applies on top of `auth`.
|
|
|
1690
1586
|
|
|
1691
1587
|
#### Running unattended on API keys
|
|
1692
1588
|
|
|
1693
|
-
When running long, unattended
|
|
1589
|
+
When running long, unattended sessions with API keys:
|
|
1694
1590
|
|
|
1695
1591
|
- **Quota, token and cost measurements per provider**:
|
|
1696
|
-
-
|
|
1592
|
+
- brindle's automatic usage pause (`usage_limit: 90`) relies on the percentage numbers emitted by Claude Code's status line under subscription plans. Under API-key billing (`ANTHROPIC_API_KEY`, `OPENAI_API_KEY`, `GEMINI_API_KEY`), the CLIs report no subscription percentage, so subscription usage pause thresholds do not trigger; manage spend via provider account budget limits or brindle budget policies.
|
|
1697
1593
|
- Token and cost tracking: Token counts and cost estimates are captured from Claude and Codex transcripts. Antigravity (`agy`) currently has **no token/cost measurements**, so budget policies and cost tracking cannot monitor Antigravity spend; enforce usage caps directly in Google AI Studio or your Google Cloud project billing settings.
|
|
1698
1594
|
- **Runtime auth failure handling and provider differences**:
|
|
1699
|
-
- **Claude and Antigravity**: Runtime authentication failures (such as 401/403, revoked API keys, or credit/billing errors) are intercepted via StopFailure and exit hooks. Brindle marks the worker as failed, alerts the supervisor, invalidates cached sign-in checks, and pauses
|
|
1700
|
-
- **Codex (unsupported runtime auth detection)**: Codex CLI turn completion (`agent-turn-complete`) does not classify auth errors at runtime. If an OpenAI API key expires or is rejected, Codex workers will not automatically transition to `failed` or trigger
|
|
1595
|
+
- **Claude and Antigravity**: Runtime authentication failures (such as 401/403, revoked API keys, or credit/billing errors) are intercepted via StopFailure and exit hooks. Brindle marks the worker as failed, alerts the supervisor, invalidates cached sign-in checks, and pauses goal driving with a `Credentials need attention` notice rather than cycling idle nudges.
|
|
1596
|
+
- **Codex (unsupported runtime auth detection)**: Codex CLI turn completion (`agent-turn-complete`) does not classify auth errors at runtime. If an OpenAI API key expires or is rejected, Codex workers will not automatically transition to `failed` or trigger a credential pause. When running Codex workers unattended, monitor their progress via `brindle watch` or check tmux panes; if an auth failure occurs, manually restart or rotate keys.
|
|
1701
1597
|
- **Supervisor credential refresh and key rotation**:
|
|
1702
|
-
- **Recovering failed/blocked workers**: When an agent fails on an expired key or
|
|
1598
|
+
- **Recovering failed/blocked workers**: When an agent fails on an expired key or brindle pauses with a credential error, export the fresh key (or update `brindle keys set`), then run `brindle continue`. This unpauses the session and relaunches paused/failed agents with the new credentials. The replacement credentials are automatically synced to the session credential store, dynamically refreshed by the supervisor's launcher on all subsequent worker delegations (`assign`/`handoff`).
|
|
1703
1599
|
- **Proactive rotation in live sessions**: For Claude keys rotated outside brindle, set Claude Code's `apiKeyHelper` in `~/.claude/settings.json` or the project's `.claude/settings.json`. Claude Code re-runs the helper every 5 minutes (configurable with `CLAUDE_CODE_API_KEY_HELPER_TTL_MS`) and after a 401, so running workers pick up the new key. Don't also export `ANTHROPIC_API_KEY` or set a Claude key with `brindle keys set`, since an environment key takes precedence over the helper. Codex and Antigravity keys still need workers stopped, then `brindle keys set`, then `brindle continue`. Exporting a new key while an active session is healthy does not restart running workers or the supervisor (running `brindle continue` on an active healthy session simply reattaches to tmux without restarting workers). To proactively rotate credentials for the entire session and all running workers: run `brindle stop` -> update credentials in your environment or via `brindle keys set` -> run `brindle continue`.
|
|
1704
1600
|
- **Precedence**: Newly stored keys (`brindle keys set`) or session credentials updated during recovery take effect dynamically for all new panes, overriding stale launcher environments. For profile-level overrides, an explicit profile key (`env.NAME`) takes precedence over default provider credentials.
|
|
1705
1601
|
- **Antigravity permissions prerequisite**: Antigravity (`agy`) does not support approving shell commands solely via external hooks. brindle therefore runs agy workers with `--dangerously-skip-permissions` and its own hook as the gate, applying their profile's `allowed_tools` and denying the rest (see Permissions). Under an explicit `agy_approvals: "prompt"` they instead stall on approval prompts for anything `settings.json` doesn't allow, their profile's `allowed_tools` included.
|
|
@@ -2065,9 +1961,9 @@ about 20 GB of GPU memory, so set `"local_models": false` if you don't want brin
|
|
|
2065
1961
|
to start or preload one. When `brindle` (or `brindle continue`)
|
|
2066
1962
|
starts and a native profile points at Ollama on this machine that isn't answering,
|
|
2067
1963
|
brindle starts it in the background with `OLLAMA_CONTEXT_LENGTH` set to the largest
|
|
2068
|
-
`context_tokens` any profile asks of it plus room for the reply (
|
|
2069
|
-
built-ins), then loads each profile's model so the
|
|
2070
|
-
read from disk. Its output goes to `~/.brindle/ollama.log`. Only Ollama on a
|
|
1964
|
+
`context_tokens` any profile asks of it plus room for the reply (40192 for the
|
|
1965
|
+
built-ins: `32k` is 32000, plus 8192), then loads each profile's model so the
|
|
1966
|
+
first task doesn't wait on the read from disk. Its output goes to `~/.brindle/ollama.log`. Only Ollama on a
|
|
2071
1967
|
loopback address is started; a remote endpoint is yours to run. A server you
|
|
2072
1968
|
started yourself (with whatever settings) is left alone.
|
|
2073
1969
|
|
|
@@ -2148,7 +2044,7 @@ To run workers on your own Bedrock, Vertex, Codex or Antigravity account, see
|
|
|
2148
2044
|
Codex agents report status through Codex's `notify` hook (brindle passes
|
|
2149
2045
|
`-c notify=[...]` at launch, leaving your own Codex config alone): a completed turn
|
|
2150
2046
|
marks the agent idle and delivers any queued message. Codex has no Stop hook, so for
|
|
2151
|
-
|
|
2047
|
+
a supervisor on Codex that turn end is also where brindle tells it to keep
|
|
2152
2048
|
going, with the same limit on reminders as Claude Code.
|
|
2153
2049
|
|
|
2154
2050
|
### Running workers on your own cloud
|
|
@@ -2367,7 +2263,7 @@ model's review) and the supervisor can hand it tasks.
|
|
|
2367
2263
|
|
|
2368
2264
|
`agy` has no command-line options for hooks, MCP servers or instructions, so brindle
|
|
2369
2265
|
adds three files to the checkout's `.agents/` folder: `mcp_config.json` (brindle's tools),
|
|
2370
|
-
`hooks.json` (status, messages,
|
|
2266
|
+
`hooks.json` (status, messages, goal driving) and `rules/brindle.md`. They're listed in
|
|
2371
2267
|
`.git/info/exclude`, so they never show up in `git status`. brindle adds to these files if
|
|
2372
2268
|
you already have them, and won't change one that's committed. Each agent's first
|
|
2373
2269
|
message is a short warm-up with its instructions, because `agy` connects MCP servers
|
|
@@ -2410,7 +2306,7 @@ add rules to that file yourself, for example:
|
|
|
2410
2306
|
- **Messages wake a supervisor through brindle's own hook.** Your interactive
|
|
2411
2307
|
Claude Code chat runs a small background waiter (an `asyncRewake` hook started
|
|
2412
2308
|
at `SessionStart` and at every `Stop`). When a worker reports, or brindle has a
|
|
2413
|
-
"new messages" notice or
|
|
2309
|
+
"new messages" notice or a goal nudge, the waiter hands it over and Claude
|
|
2414
2310
|
Code wakes the model with it: an idle chat starts a new turn, a busy one gets it
|
|
2415
2311
|
between steps, and the chat shows one "Stop hook feedback" line. Each message
|
|
2416
2312
|
is wrapped as `<brindle-msg nonce="..." from="developer agent w1">...</brindle-msg>`
|