brindle 0.5.4__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.
Files changed (198) hide show
  1. {brindle-0.5.4 → brindle-0.5.5}/PKG-INFO +24 -126
  2. {brindle-0.5.4 → brindle-0.5.5}/README.md +23 -125
  3. {brindle-0.5.4 → brindle-0.5.5}/pyproject.toml +3 -1
  4. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/builtin_agents/developer-local.md +1 -1
  5. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/cli.py +2 -2
  6. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/model_access.py +1 -1
  7. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/pipeline.py +5 -2
  8. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/pro/account.py +5 -4
  9. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/providers.py +1 -1
  10. {brindle-0.5.4 → brindle-0.5.5}/.gitignore +0 -0
  11. {brindle-0.5.4 → brindle-0.5.5}/LICENSE +0 -0
  12. {brindle-0.5.4 → brindle-0.5.5}/SCHEDULE-A +0 -0
  13. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/__init__.py +0 -0
  14. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/__main__.py +0 -0
  15. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/account.py +0 -0
  16. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/agents.py +0 -0
  17. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/airgap.py +0 -0
  18. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/antigravity.py +0 -0
  19. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/assembler.py +0 -0
  20. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/assets/braid_dark.png +0 -0
  21. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/assets/braid_light.png +0 -0
  22. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/autopilot.py +0 -0
  23. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/budget.py +0 -0
  24. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/builtin_agents/__init__.py +0 -0
  25. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/builtin_agents/backend-auditor.md +0 -0
  26. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/builtin_agents/coordinator.md +0 -0
  27. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/builtin_agents/developer-codex.md +0 -0
  28. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/builtin_agents/developer-fable.md +0 -0
  29. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/builtin_agents/developer-gemini.md +0 -0
  30. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/builtin_agents/developer-heavy.md +0 -0
  31. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/builtin_agents/developer-light.md +0 -0
  32. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/builtin_agents/developer-opencode.md +0 -0
  33. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/builtin_agents/developer-sonnet.md +0 -0
  34. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/builtin_agents/developer.md +0 -0
  35. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/builtin_agents/qa.md +0 -0
  36. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/builtin_agents/reviewer-codex.md +0 -0
  37. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/builtin_agents/reviewer-gemini.md +0 -0
  38. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/builtin_agents/reviewer-local.md +0 -0
  39. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/builtin_agents/reviewer-opencode.md +0 -0
  40. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/builtin_agents/reviewer.md +0 -0
  41. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/builtin_agents/subagent.md +0 -0
  42. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/builtin_agents/supervisor.md +0 -0
  43. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/builtin_rules/__init__.py +0 -0
  44. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/builtin_rules/security/backend.md +0 -0
  45. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/builtin_rules/style/minimal-diff.md +0 -0
  46. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/builtin_rules/tests/only.md +0 -0
  47. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/bus.py +0 -0
  48. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/check_scope.py +0 -0
  49. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/ci_adapters.py +0 -0
  50. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/ci_client.py +0 -0
  51. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/ci_federation.py +0 -0
  52. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/ci_hosts.py +0 -0
  53. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/clone.py +0 -0
  54. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/cloud_credential.py +0 -0
  55. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/cloud_login.py +0 -0
  56. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/codemap.py +0 -0
  57. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/codemap_docs.py +0 -0
  58. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/codex_hook.py +0 -0
  59. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/company_identity.py +0 -0
  60. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/company_login.py +0 -0
  61. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/config.py +0 -0
  62. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/conflicts.py +0 -0
  63. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/connections.py +0 -0
  64. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/coordinator.py +0 -0
  65. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/cost.py +0 -0
  66. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/cost_estimate.py +0 -0
  67. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/cull.py +0 -0
  68. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/daemon/__init__.py +0 -0
  69. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/daemon/api-schema.json +0 -0
  70. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/daemon/app.py +0 -0
  71. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/daemon/auth.py +0 -0
  72. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/daemon/events.py +0 -0
  73. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/daemon/holds.py +0 -0
  74. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/daemon/lifecycle.py +0 -0
  75. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/daemon/peer.py +0 -0
  76. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/daemon/routes_actions.py +0 -0
  77. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/daemon/routes_org_permissions.py +0 -0
  78. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/daemon/routes_read.py +0 -0
  79. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/daemon/schema.py +0 -0
  80. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/daemon/session_review.py +0 -0
  81. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/daemon/terminal.py +0 -0
  82. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/db.py +0 -0
  83. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/debuglog.py +0 -0
  84. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/demo.py +0 -0
  85. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/detect.py +0 -0
  86. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/doctor.py +0 -0
  87. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/entry.py +0 -0
  88. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/escapes.py +0 -0
  89. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/events.py +0 -0
  90. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/gates.py +0 -0
  91. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/git.py +0 -0
  92. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/guardrails.py +0 -0
  93. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/history.py +0 -0
  94. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/identity_lock.py +0 -0
  95. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/inbox.py +0 -0
  96. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/kb.py +0 -0
  97. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/key_check.py +0 -0
  98. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/keys_cmds.py +0 -0
  99. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/keystore.py +0 -0
  100. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/knowledge.py +0 -0
  101. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/launch_health.py +0 -0
  102. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/learned_rules.py +0 -0
  103. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/learning.py +0 -0
  104. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/legacy.py +0 -0
  105. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/local_setup.py +0 -0
  106. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/login_pause.py +0 -0
  107. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/mcp_server.py +0 -0
  108. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/model_availability.py +0 -0
  109. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/native/__init__.py +0 -0
  110. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/native/catalog.py +0 -0
  111. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/native/client.py +0 -0
  112. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/native/loop.py +0 -0
  113. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/native/lsp.py +0 -0
  114. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/native/permissions.py +0 -0
  115. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/native/runner.py +0 -0
  116. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/native/serve.py +0 -0
  117. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/native/tools.py +0 -0
  118. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/opencode.py +0 -0
  119. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/org_permissions.py +0 -0
  120. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/pane_auth.py +0 -0
  121. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/permission_asks.py +0 -0
  122. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/permission_grants.py +0 -0
  123. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/permission_groups.py +0 -0
  124. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/permission_routing.py +0 -0
  125. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/permissions.py +0 -0
  126. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/picker.py +0 -0
  127. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/plugins.py +0 -0
  128. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/policy.py +0 -0
  129. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/pool.py +0 -0
  130. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/preflight.py +0 -0
  131. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/pricing.py +0 -0
  132. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/pro/__init__.py +0 -0
  133. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/pro/_files.py +0 -0
  134. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/pro/audit_chain.py +0 -0
  135. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/pro/audit_export.py +0 -0
  136. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/pro/auth.py +0 -0
  137. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/pro/brief_learning.py +0 -0
  138. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/pro/cost_centers.py +0 -0
  139. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/pro/credentials.py +0 -0
  140. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/pro/features.py +0 -0
  141. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/pro/keys.py +0 -0
  142. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/pro/learning.py +0 -0
  143. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/pro/license.py +0 -0
  144. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/pro/loopback.py +0 -0
  145. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/pro/managed_models.py +0 -0
  146. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/pro/org_profiles.py +0 -0
  147. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/pro/orgkey.py +0 -0
  148. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/pro/rollout.py +0 -0
  149. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/pro/route_health.py +0 -0
  150. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/pro/settings_sync.py +0 -0
  151. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/pro/status.py +0 -0
  152. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/pro/team_events.py +0 -0
  153. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/pro/team_policy.py +0 -0
  154. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/procs.py +0 -0
  155. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/profiles.py +0 -0
  156. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/prompt_answer.py +0 -0
  157. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/provider_homes.py +0 -0
  158. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/providers_install.py +0 -0
  159. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/quota.py +0 -0
  160. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/repo_cmds.py +0 -0
  161. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/repos.py +0 -0
  162. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/rewind.py +0 -0
  163. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/rule_checks.py +0 -0
  164. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/savings.py +0 -0
  165. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/scratch.py +0 -0
  166. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/secrets.py +0 -0
  167. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/self_serve.py +0 -0
  168. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/service/__init__.py +0 -0
  169. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/service/dto.py +0 -0
  170. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/service/errors.py +0 -0
  171. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/service/inbox.py +0 -0
  172. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/service/permissions.py +0 -0
  173. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/service/routing.py +0 -0
  174. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/service/sessions.py +0 -0
  175. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/services.py +0 -0
  176. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/sessions.py +0 -0
  177. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/sidebar_follow.py +0 -0
  178. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/sidebar_logo.py +0 -0
  179. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/signin_pause.py +0 -0
  180. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/status_cache.py +0 -0
  181. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/tasks.py +0 -0
  182. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/tmux.py +0 -0
  183. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/updates.py +0 -0
  184. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/upgrade.py +0 -0
  185. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/usage.py +0 -0
  186. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/view.py +0 -0
  187. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/wake.py +0 -0
  188. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/watch.py +0 -0
  189. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/watch_costs.py +0 -0
  190. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/web/__init__.py +0 -0
  191. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/web/chat.py +0 -0
  192. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/web/dashboard.py +0 -0
  193. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/web/diff.py +0 -0
  194. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/web/server.py +0 -0
  195. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/web/static/app.js +0 -0
  196. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/web/static/index.html +0 -0
  197. {brindle-0.5.4 → brindle-0.5.5}/src/brindle/worker_models.py +0 -0
  198. {brindle-0.5.4 → 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.4
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
@@ -314,10 +314,12 @@ or put the goal in `.brindle/goals.md`, and it works like a project manager:
314
314
  reviewer agent has approved that exact commit, your pre-commit hooks pass,
315
315
  and your `checks` pass. brindle runs these itself before `merge_workspace`,
316
316
  and caches a clean commit's passing result so it isn't re-run for every
317
- review and merge attempt at the same sha. `request_review` starts the
318
- reviewer immediately and runs `checks` in the background, delivering a
319
- pass/fail summary (output only for failures) as a message once they
320
- finish, instead of asking the reviewer to run the whole suite itself.
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.
321
323
  `request_review` picks the reviewer profile itself unless you pass one: an
322
324
  explicit `profile` argument, else `review_profile` in the repo config,
323
325
  else `reviewer` (the repo's `reviewer` setting). brindle never picks a
@@ -1077,23 +1079,17 @@ how to use them, and the next step to get the rest:
1077
1079
  | per-worktree services | Pro | `"services"` in `.brindle/config.json` |
1078
1080
  | several repos in one session | Pro | `brindle repo add <path>` |
1079
1081
  | settings sync across machines | Pro | `brindle account sync` |
1080
- | Brindle-CI build fixing (the fix workflow) | Pro | `brindle ci init` |
1081
1082
  | learned rules from repeated review findings | Pro | `brindle rules suggest` |
1082
1083
  | cost (estimates, budgets, reports) | Pro | `brindle cost report` |
1083
1084
  | guardrails (write scope, read scope, env allowlist per profile) | Pro | `write_scope`, `read_scope`, `env_allow` in a profile |
1084
1085
  | org policies + audit feed | Team | `brindle account org policy` |
1085
- | Brindle-CI (fixes builds, issues into verified pull requests, validation) | Team | `brindle ci init` |
1086
1086
  | org profile and rule-pack library, pinned so a repo can't loosen it | Team | `brindle account org profiles` |
1087
1087
  | org budgets and protected paths | Team | `budget`, `protected_paths` in your org policy (`brindle account org policy`) |
1088
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 |
1089
1089
  | audit log, air-gap | Enterprise | `brindle audit verify`, `"airgap": true` |
1090
1090
  | audit export | Enterprise | `"audit_export"` in `~/.brindle/config.json`, `brindle audit ship` |
1091
1091
  | managed models | Enterprise | `agent_setup` routes with `enforce`, and `deny_personal_keys`, in your org policy (see "Managed models" below) |
1092
- | wider CI, cost centers, managed rollout | Enterprise | `brindle ci init --host gitlab`, `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) |
1093
-
1094
- `brindle ci init` checks your plan before it changes anything: it refuses
1095
- without Brindle-CI on the org you're using, and on Pro it sets up only the fix
1096
- 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) |
1097
1093
 
1098
1094
  ```sh
1099
1095
  brindle account # paid features: what you have, how to use them, how to get the rest
@@ -1383,109 +1379,7 @@ brindle audit ship [--force] # send now; exit 1 if a sink
1383
1379
  brindle audit prune [--repo PATH] [--days N] # prune now (default: retention_days)
1384
1380
  ```
1385
1381
 
1386
- ### Brindle-CI
1387
-
1388
- Brindle-CI (brindle Team; build fixing alone is on Pro) brings brindle into your CI: it fixes broken builds,
1389
- turns issues into pull requests whose checks it has verified, and reviews pull
1390
- requests with evidence. It runs on your own CI with your own model keys; the
1391
- hosted control plane decides what each run does and what it reports. The
1392
- workflows call these commands:
1393
-
1394
- - `brindle ci init`: set a repository up in one go (the GitHub App, the secrets,
1395
- the workflows as a pull request, then a doctor check). Run it inside a
1396
- checkout of the repository. For Claude it asks whether to use an API key
1397
- (the `ANTHROPIC_API_KEY` secret) or Anthropic
1398
- [workload identity federation](https://platform.claude.com/docs/en/manage-claude/wif-reference)
1399
- (`--credential key|federation` answers without asking). It also creates the
1400
- `brindle` issue label (label an issue with it to hand it to brindle CI), and
1401
- commits the workflows on a `brindle/ci-setup` branch, then puts you back on
1402
- the branch you started on and deletes the local setup branch, so `git pull`
1403
- after merging the setup pull request is clean (commit or stash your changes
1404
- first: it refuses to start with uncommitted work). With your own cloud
1405
- (`--credential bedrock|vertex|foundry`, keyless GitHub OIDC) it can read the
1406
- IDs from the deployment template's outputs instead of asking:
1407
- `--from-stack NAME [--region R]` (AWS CloudFormation), `--from-terraform DIR`
1408
- (Google) or `--from-deployment NAME -g RG` (Azure). They are defaults for
1409
- `--cloud-var`, which still overrides them, and every ID is format-checked. A
1410
- missing `aws`, `terraform` or `az` CLI or output is an error that names the
1411
- `--cloud-var` to pass instead. Vertex AI and Microsoft Foundry are in
1412
- **preview** (not yet verified end to end): `init` refuses them unless you pass
1413
- `--preview` or set `BRINDLE_CI_PREVIEW_CLOUDS=1`, and `doctor` marks them
1414
- `(preview)`. Bedrock is generally available.
1415
- - `brindle ci doctor`: which provider CLIs and credential names a runner has, and
1416
- which providers CI may use on this repository. `--models` also makes one tiny
1417
- call per pinned model and says why any is refused (a quota, a form not filled in).
1418
- - `brindle ci start`: start a run for an issue, a goal text or a dispatched run,
1419
- or a validation of a pull request.
1420
- - `brindle ci run`: run what was started: the supervisor and the result upload,
1421
- or the pull request's checks and reviews and the evidence upload.
1422
- - `brindle ci report`: tell the service how the workflow's jobs ended.
1423
-
1424
- Credential names are reported, never values. CI uses API keys, cloud sign-ins
1425
- (Bedrock, Vertex, Foundry) or identity federation only: a provider signed in
1426
- only with a subscription (`CLAUDE_CODE_OAUTH_TOKEN`, a Codex ChatGPT login) is
1427
- not used, on personal and organization repositories alike. Add an API key
1428
- secret instead.
1429
-
1430
- Fix builds only fix the default branch's *required* status checks, and a new
1431
- repository has none. When the default branch requires none, `brindle ci init`
1432
- warns and, for each job in your workflows, asks whether to make it required
1433
- (`--required-check NAME` picks one without asking, `--no-required-check` only
1434
- warns; run without a terminal, init only makes a check required when
1435
- `--required-check` names it). It adds the check to the branch's existing protection, or protects the
1436
- branch with just that check. GitHub only allows branch protection on a private
1437
- repository with a paid plan; when it refuses, init says how to require the
1438
- check yourself (Settings > Branches, "Require status checks to pass").
1439
-
1440
- An Anthropic API key is either a workspace key (scoped to one workspace) or an
1441
- organization-level key (not scoped to a workspace). An organization-level key
1442
- needs the workspace in every request, so after the key `brindle ci init` asks for
1443
- its workspace ID (`wrkspc_...`; leave it blank for a workspace key, or pass
1444
- `--workspace-id`, default `$ANTHROPIC_WORKSPACE_ID`) and stores it as the Actions
1445
- variable `ANTHROPIC_WORKSPACE_ID`. The workflow then sets
1446
- `ANTHROPIC_CUSTOM_HEADERS="anthropic-workspace-id: <id>"`, which reaches every
1447
- Claude Code process the run starts.
1448
-
1449
- With identity federation the repository stores no Anthropic key: the workflow
1450
- exchanges GitHub's OIDC token once for a short-lived Anthropic token, as a
1451
- Claude Console service account (billed as API, so it is allowed on
1452
- organization repositories), and gives the job `ANTHROPIC_AUTH_TOKEN`. `brindle
1453
- ci init` stores the rule, organization, service account and optional workspace
1454
- IDs as the Actions variables `ANTHROPIC_FEDERATION_RULE_ID`,
1455
- `ANTHROPIC_ORGANIZATION_ID`, `ANTHROPIC_SERVICE_ACCOUNT_ID` and
1456
- `ANTHROPIC_WORKSPACE_ID`, from `--rule-id`, `--organization-id`,
1457
- `--service-account-id` and `--workspace-id` or else asked (defaulting to those
1458
- environment variables). Without a terminal on stdin, init asks nothing and
1459
- takes the options and the environment, so it can run unattended; a missing or
1460
- malformed ID (rule `fdrl_...`, organization a UUID, service account
1461
- `svac_...`, workspace `wrkspc_...`) stops it before it creates the CI token.
1462
- The ID options imply `--credential federation` and can't be combined with
1463
- `--credential key`. Create the federation rule in the Claude Console with
1464
- subject prefix `repo:<owner>/<name>:*`, the condition
1465
-
1466
- ```text
1467
- claims.repository == "<owner>/<name>" && claims.workflow_ref.startsWith("<owner>/<name>/.github/workflows/brindle-ci-")
1468
- ```
1469
-
1470
- audience `https://api.anthropic.com`, and a token lifetime of at least 600
1471
- seconds. The condition lets only brindle's workflows mint tokens. On pull
1472
- requests the pull request's own copy of the validate workflow runs, so give
1473
- write access only to people you trust (forks never get a token). Leave the `ANTHROPIC_API_KEY` secret
1474
- unset: a key takes precedence (brindle drops an empty one before Claude Code
1475
- starts).
1476
-
1477
- A federated token lives at most about ten minutes, however long the rule
1478
- allows: Anthropic caps it at twice what remains of GitHub's OIDC token. So
1479
- the run job doesn't rely on the workflow's one exchange: `brindle ci run`
1480
- fetches a fresh OIDC token and exchanges it again at 70% of each token's
1481
- life, and lends the current token to the agents through a proxy on the
1482
- runner's loopback interface. The agents get `ANTHROPIC_BASE_URL` pointing at
1483
- it and a random per-run secret as `ANTHROPIC_AUTH_TOKEN`; the Anthropic token
1484
- itself stays in the `brindle ci run` process, and the GitHub token endpoint
1485
- (`ACTIONS_ID_TOKEN_REQUEST_URL` and its token) is scrubbed before any agent or
1486
- check starts. If the first exchange fails, the run goes on with the
1487
- workflow's token as before; `BRINDLE_CI_FEDERATION_REFRESH=0` in the job's
1488
- environment turns the refresh off.
1382
+ ## Cleanup, merging and workspace config
1489
1383
 
1490
1384
  **Closing and cleaning up.** Press `x` on an agent in the sidebar (twice for one
1491
1385
  that's still running) or run `brindle close <id>` to stop it and hide it. Stopping means
@@ -1504,8 +1398,10 @@ removes stale locks and empty worktree folders.
1504
1398
  **The pipeline.** The slow part of delegating isn't the workers, it's the supervisor's
1505
1399
  turns between the stages: report, review, merge, remove, each waiting on a model turn
1506
1400
  that carries the whole session's context. So brindle runs those stages itself. When a
1507
- worker reports, brindle starts the review at once and runs the checks in the
1508
- background; when the reviewer approves and the checks pass, brindle merges the branch,
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,
1509
1405
  removes the worktree, and sends the supervisor one message with the worker's report
1510
1406
  and the review. Findings go straight back to the worker to fix (`review_rounds`
1511
1407
  times) before they reach the supervisor, and anything the pipeline can't settle (a
@@ -1528,11 +1424,13 @@ merges. Conflicts in `protected_paths` (migrations, lockfiles, generated code) a
1528
1424
  never handed to a worker: the supervisor gets them as "needs you".
1529
1425
 
1530
1426
  **The completion audit.** A milestone's check can pass without the milestone being
1531
- done: the test asserts too little, or checks the wrong thing. So when every milestone
1532
- passes, brindle doesn't call the goal reached yet. A read-only reviewer audits everything since the goal was set
1533
- against the goal and each milestone, looking for what's missing, stubbed or weakly
1534
- tested. Only its approval of that commit finishes the goal. If it finds gaps, the
1535
- supervisor gets them as a message and keeps working until a fresh audit approves.
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.
1536
1434
  `"goal_audit": false` turns it off.
1537
1435
 
1538
1436
  **Spending fewer tokens.** Workers run only the tests that cover their change while
@@ -1663,7 +1561,7 @@ it's signed in without a plan that includes it, is reported to its supervisor.
1663
1561
  | Provider | Key login (environment variables) |
1664
1562
  |---|---|
1665
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`) |
1666
- | `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` (Brindle-CI) 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`) |
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`) |
1667
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 |
1668
1566
  | `opencode` | whatever the model's provider takes (`ANTHROPIC_API_KEY`, `OPENAI_API_KEY`, ...), or `opencode auth login`; its free `opencode/...` models need neither |
1669
1567
 
@@ -2063,9 +1961,9 @@ about 20 GB of GPU memory, so set `"local_models": false` if you don't want brin
2063
1961
  to start or preload one. When `brindle` (or `brindle continue`)
2064
1962
  starts and a native profile points at Ollama on this machine that isn't answering,
2065
1963
  brindle starts it in the background with `OLLAMA_CONTEXT_LENGTH` set to the largest
2066
- `context_tokens` any profile asks of it plus room for the reply (40960 for the
2067
- built-ins), then loads each profile's model so the first task doesn't wait on the
2068
- 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
2069
1967
  loopback address is started; a remote endpoint is yours to run. A server you
2070
1968
  started yourself (with whatever settings) is left alone.
2071
1969
 
@@ -282,10 +282,12 @@ or put the goal in `.brindle/goals.md`, and it works like a project manager:
282
282
  reviewer agent has approved that exact commit, your pre-commit hooks pass,
283
283
  and your `checks` pass. brindle runs these itself before `merge_workspace`,
284
284
  and caches a clean commit's passing result so it isn't re-run for every
285
- review and merge attempt at the same sha. `request_review` starts the
286
- reviewer immediately and runs `checks` in the background, delivering a
287
- pass/fail summary (output only for failures) as a message once they
288
- finish, instead of asking the reviewer to run the whole suite itself.
285
+ review and merge attempt at the same sha. `request_review` returns at
286
+ once. With `checks` configured, brindle runs them first, in the
287
+ background, and starts the reviewer when they finish, with a pass/fail
288
+ summary (output only for failures) in its prompt, instead of asking the
289
+ reviewer to run the whole suite itself. With no `checks`, the reviewer
290
+ starts right away.
289
291
  `request_review` picks the reviewer profile itself unless you pass one: an
290
292
  explicit `profile` argument, else `review_profile` in the repo config,
291
293
  else `reviewer` (the repo's `reviewer` setting). brindle never picks a
@@ -1045,23 +1047,17 @@ how to use them, and the next step to get the rest:
1045
1047
  | per-worktree services | Pro | `"services"` in `.brindle/config.json` |
1046
1048
  | several repos in one session | Pro | `brindle repo add <path>` |
1047
1049
  | settings sync across machines | Pro | `brindle account sync` |
1048
- | Brindle-CI build fixing (the fix workflow) | Pro | `brindle ci init` |
1049
1050
  | learned rules from repeated review findings | Pro | `brindle rules suggest` |
1050
1051
  | cost (estimates, budgets, reports) | Pro | `brindle cost report` |
1051
1052
  | guardrails (write scope, read scope, env allowlist per profile) | Pro | `write_scope`, `read_scope`, `env_allow` in a profile |
1052
1053
  | org policies + audit feed | Team | `brindle account org policy` |
1053
- | Brindle-CI (fixes builds, issues into verified pull requests, validation) | Team | `brindle ci init` |
1054
1054
  | org profile and rule-pack library, pinned so a repo can't loosen it | Team | `brindle account org profiles` |
1055
1055
  | org budgets and protected paths | Team | `budget`, `protected_paths` in your org policy (`brindle account org policy`) |
1056
1056
  | 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 |
1057
1057
  | audit log, air-gap | Enterprise | `brindle audit verify`, `"airgap": true` |
1058
1058
  | audit export | Enterprise | `"audit_export"` in `~/.brindle/config.json`, `brindle audit ship` |
1059
1059
  | managed models | Enterprise | `agent_setup` routes with `enforce`, and `deny_personal_keys`, in your org policy (see "Managed models" below) |
1060
- | wider CI, cost centers, managed rollout | Enterprise | `brindle ci init --host gitlab`, `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) |
1061
-
1062
- `brindle ci init` checks your plan before it changes anything: it refuses
1063
- without Brindle-CI on the org you're using, and on Pro it sets up only the fix
1064
- workflow.
1060
+ | 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) |
1065
1061
 
1066
1062
  ```sh
1067
1063
  brindle account # paid features: what you have, how to use them, how to get the rest
@@ -1351,109 +1347,7 @@ brindle audit ship [--force] # send now; exit 1 if a sink
1351
1347
  brindle audit prune [--repo PATH] [--days N] # prune now (default: retention_days)
1352
1348
  ```
1353
1349
 
1354
- ### Brindle-CI
1355
-
1356
- Brindle-CI (brindle Team; build fixing alone is on Pro) brings brindle into your CI: it fixes broken builds,
1357
- turns issues into pull requests whose checks it has verified, and reviews pull
1358
- requests with evidence. It runs on your own CI with your own model keys; the
1359
- hosted control plane decides what each run does and what it reports. The
1360
- workflows call these commands:
1361
-
1362
- - `brindle ci init`: set a repository up in one go (the GitHub App, the secrets,
1363
- the workflows as a pull request, then a doctor check). Run it inside a
1364
- checkout of the repository. For Claude it asks whether to use an API key
1365
- (the `ANTHROPIC_API_KEY` secret) or Anthropic
1366
- [workload identity federation](https://platform.claude.com/docs/en/manage-claude/wif-reference)
1367
- (`--credential key|federation` answers without asking). It also creates the
1368
- `brindle` issue label (label an issue with it to hand it to brindle CI), and
1369
- commits the workflows on a `brindle/ci-setup` branch, then puts you back on
1370
- the branch you started on and deletes the local setup branch, so `git pull`
1371
- after merging the setup pull request is clean (commit or stash your changes
1372
- first: it refuses to start with uncommitted work). With your own cloud
1373
- (`--credential bedrock|vertex|foundry`, keyless GitHub OIDC) it can read the
1374
- IDs from the deployment template's outputs instead of asking:
1375
- `--from-stack NAME [--region R]` (AWS CloudFormation), `--from-terraform DIR`
1376
- (Google) or `--from-deployment NAME -g RG` (Azure). They are defaults for
1377
- `--cloud-var`, which still overrides them, and every ID is format-checked. A
1378
- missing `aws`, `terraform` or `az` CLI or output is an error that names the
1379
- `--cloud-var` to pass instead. Vertex AI and Microsoft Foundry are in
1380
- **preview** (not yet verified end to end): `init` refuses them unless you pass
1381
- `--preview` or set `BRINDLE_CI_PREVIEW_CLOUDS=1`, and `doctor` marks them
1382
- `(preview)`. Bedrock is generally available.
1383
- - `brindle ci doctor`: which provider CLIs and credential names a runner has, and
1384
- which providers CI may use on this repository. `--models` also makes one tiny
1385
- call per pinned model and says why any is refused (a quota, a form not filled in).
1386
- - `brindle ci start`: start a run for an issue, a goal text or a dispatched run,
1387
- or a validation of a pull request.
1388
- - `brindle ci run`: run what was started: the supervisor and the result upload,
1389
- or the pull request's checks and reviews and the evidence upload.
1390
- - `brindle ci report`: tell the service how the workflow's jobs ended.
1391
-
1392
- Credential names are reported, never values. CI uses API keys, cloud sign-ins
1393
- (Bedrock, Vertex, Foundry) or identity federation only: a provider signed in
1394
- only with a subscription (`CLAUDE_CODE_OAUTH_TOKEN`, a Codex ChatGPT login) is
1395
- not used, on personal and organization repositories alike. Add an API key
1396
- secret instead.
1397
-
1398
- Fix builds only fix the default branch's *required* status checks, and a new
1399
- repository has none. When the default branch requires none, `brindle ci init`
1400
- warns and, for each job in your workflows, asks whether to make it required
1401
- (`--required-check NAME` picks one without asking, `--no-required-check` only
1402
- warns; run without a terminal, init only makes a check required when
1403
- `--required-check` names it). It adds the check to the branch's existing protection, or protects the
1404
- branch with just that check. GitHub only allows branch protection on a private
1405
- repository with a paid plan; when it refuses, init says how to require the
1406
- check yourself (Settings > Branches, "Require status checks to pass").
1407
-
1408
- An Anthropic API key is either a workspace key (scoped to one workspace) or an
1409
- organization-level key (not scoped to a workspace). An organization-level key
1410
- needs the workspace in every request, so after the key `brindle ci init` asks for
1411
- its workspace ID (`wrkspc_...`; leave it blank for a workspace key, or pass
1412
- `--workspace-id`, default `$ANTHROPIC_WORKSPACE_ID`) and stores it as the Actions
1413
- variable `ANTHROPIC_WORKSPACE_ID`. The workflow then sets
1414
- `ANTHROPIC_CUSTOM_HEADERS="anthropic-workspace-id: <id>"`, which reaches every
1415
- Claude Code process the run starts.
1416
-
1417
- With identity federation the repository stores no Anthropic key: the workflow
1418
- exchanges GitHub's OIDC token once for a short-lived Anthropic token, as a
1419
- Claude Console service account (billed as API, so it is allowed on
1420
- organization repositories), and gives the job `ANTHROPIC_AUTH_TOKEN`. `brindle
1421
- ci init` stores the rule, organization, service account and optional workspace
1422
- IDs as the Actions variables `ANTHROPIC_FEDERATION_RULE_ID`,
1423
- `ANTHROPIC_ORGANIZATION_ID`, `ANTHROPIC_SERVICE_ACCOUNT_ID` and
1424
- `ANTHROPIC_WORKSPACE_ID`, from `--rule-id`, `--organization-id`,
1425
- `--service-account-id` and `--workspace-id` or else asked (defaulting to those
1426
- environment variables). Without a terminal on stdin, init asks nothing and
1427
- takes the options and the environment, so it can run unattended; a missing or
1428
- malformed ID (rule `fdrl_...`, organization a UUID, service account
1429
- `svac_...`, workspace `wrkspc_...`) stops it before it creates the CI token.
1430
- The ID options imply `--credential federation` and can't be combined with
1431
- `--credential key`. Create the federation rule in the Claude Console with
1432
- subject prefix `repo:<owner>/<name>:*`, the condition
1433
-
1434
- ```text
1435
- claims.repository == "<owner>/<name>" && claims.workflow_ref.startsWith("<owner>/<name>/.github/workflows/brindle-ci-")
1436
- ```
1437
-
1438
- audience `https://api.anthropic.com`, and a token lifetime of at least 600
1439
- seconds. The condition lets only brindle's workflows mint tokens. On pull
1440
- requests the pull request's own copy of the validate workflow runs, so give
1441
- write access only to people you trust (forks never get a token). Leave the `ANTHROPIC_API_KEY` secret
1442
- unset: a key takes precedence (brindle drops an empty one before Claude Code
1443
- starts).
1444
-
1445
- A federated token lives at most about ten minutes, however long the rule
1446
- allows: Anthropic caps it at twice what remains of GitHub's OIDC token. So
1447
- the run job doesn't rely on the workflow's one exchange: `brindle ci run`
1448
- fetches a fresh OIDC token and exchanges it again at 70% of each token's
1449
- life, and lends the current token to the agents through a proxy on the
1450
- runner's loopback interface. The agents get `ANTHROPIC_BASE_URL` pointing at
1451
- it and a random per-run secret as `ANTHROPIC_AUTH_TOKEN`; the Anthropic token
1452
- itself stays in the `brindle ci run` process, and the GitHub token endpoint
1453
- (`ACTIONS_ID_TOKEN_REQUEST_URL` and its token) is scrubbed before any agent or
1454
- check starts. If the first exchange fails, the run goes on with the
1455
- workflow's token as before; `BRINDLE_CI_FEDERATION_REFRESH=0` in the job's
1456
- environment turns the refresh off.
1350
+ ## Cleanup, merging and workspace config
1457
1351
 
1458
1352
  **Closing and cleaning up.** Press `x` on an agent in the sidebar (twice for one
1459
1353
  that's still running) or run `brindle close <id>` to stop it and hide it. Stopping means
@@ -1472,8 +1366,10 @@ removes stale locks and empty worktree folders.
1472
1366
  **The pipeline.** The slow part of delegating isn't the workers, it's the supervisor's
1473
1367
  turns between the stages: report, review, merge, remove, each waiting on a model turn
1474
1368
  that carries the whole session's context. So brindle runs those stages itself. When a
1475
- worker reports, brindle starts the review at once and runs the checks in the
1476
- background; when the reviewer approves and the checks pass, brindle merges the branch,
1369
+ worker reports, brindle gets the branch reviewed at once: with `checks` configured it
1370
+ runs them first, in the background, and starts the reviewer when they finish, with
1371
+ their results in its prompt (with no `checks`, the reviewer starts right away). When
1372
+ the reviewer approves and the checks pass, brindle merges the branch,
1477
1373
  removes the worktree, and sends the supervisor one message with the worker's report
1478
1374
  and the review. Findings go straight back to the worker to fix (`review_rounds`
1479
1375
  times) before they reach the supervisor, and anything the pipeline can't settle (a
@@ -1496,11 +1392,13 @@ merges. Conflicts in `protected_paths` (migrations, lockfiles, generated code) a
1496
1392
  never handed to a worker: the supervisor gets them as "needs you".
1497
1393
 
1498
1394
  **The completion audit.** A milestone's check can pass without the milestone being
1499
- done: the test asserts too little, or checks the wrong thing. So when every milestone
1500
- passes, brindle doesn't call the goal reached yet. A read-only reviewer audits everything since the goal was set
1501
- against the goal and each milestone, looking for what's missing, stubbed or weakly
1502
- tested. Only its approval of that commit finishes the goal. If it finds gaps, the
1503
- supervisor gets them as a message and keeps working until a fresh audit approves.
1395
+ done: the check tests the wrong thing, or the deliverable was never built. So when
1396
+ every milestone passes, brindle doesn't call the goal reached yet. A read-only
1397
+ reviewer audits everything since the goal was set against the goal and each
1398
+ milestone, looking for deliverables that are missing, stubbed out or unhandled. It
1399
+ trusts the passing checks and doesn't debate how deep the tests go. Only its
1400
+ approval of that commit finishes the goal. If it finds gaps, the supervisor gets
1401
+ them as a message and keeps working until a fresh audit approves.
1504
1402
  `"goal_audit": false` turns it off.
1505
1403
 
1506
1404
  **Spending fewer tokens.** Workers run only the tests that cover their change while
@@ -1631,7 +1529,7 @@ it's signed in without a plan that includes it, is reported to its supervisor.
1631
1529
  | Provider | Key login (environment variables) |
1632
1530
  |---|---|
1633
1531
  | `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`) |
1634
- | `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` (Brindle-CI) 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`) |
1532
+ | `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`) |
1635
1533
  | `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 |
1636
1534
  | `opencode` | whatever the model's provider takes (`ANTHROPIC_API_KEY`, `OPENAI_API_KEY`, ...), or `opencode auth login`; its free `opencode/...` models need neither |
1637
1535
 
@@ -2031,9 +1929,9 @@ about 20 GB of GPU memory, so set `"local_models": false` if you don't want brin
2031
1929
  to start or preload one. When `brindle` (or `brindle continue`)
2032
1930
  starts and a native profile points at Ollama on this machine that isn't answering,
2033
1931
  brindle starts it in the background with `OLLAMA_CONTEXT_LENGTH` set to the largest
2034
- `context_tokens` any profile asks of it plus room for the reply (40960 for the
2035
- built-ins), then loads each profile's model so the first task doesn't wait on the
2036
- read from disk. Its output goes to `~/.brindle/ollama.log`. Only Ollama on a
1932
+ `context_tokens` any profile asks of it plus room for the reply (40192 for the
1933
+ built-ins: `32k` is 32000, plus 8192), then loads each profile's model so the
1934
+ first task doesn't wait on the read from disk. Its output goes to `~/.brindle/ollama.log`. Only Ollama on a
2037
1935
  loopback address is started; a remote endpoint is yours to run. A server you
2038
1936
  started yourself (with whatever settings) is left alone.
2039
1937
 
@@ -1,6 +1,6 @@
1
1
  [project]
2
2
  name = "brindle"
3
- version = "0.5.4"
3
+ version = "0.5.5"
4
4
  description = "Run coding agents in parallel, each on its own git branch, with a supervisor that delegates, reviews, and merges"
5
5
  readme = "README.md"
6
6
  requires-python = ">=3.11"
@@ -79,5 +79,7 @@ testpaths = ["tests"]
79
79
  pythonpath = ["tests"]
80
80
  markers = [
81
81
  "serial: run outside xdist (`pytest -m serial`); the parallel pass skips these",
82
+ "brindle_ci: a brindle CI test; deselected unless BRINDLE_CI_TESTS=1 (tests/conftest.py marks the test_ci_* files)",
83
+ "brindle_ci_guard: a refusal, fail-closed or secret-hygiene test of the brindle CI commands; always runs",
82
84
  "variant(reason): an input variant that covers no new code on purpose (see scripts/check_new_tests.py)",
83
85
  ]
@@ -5,7 +5,7 @@ provider: native
5
5
  api: openai # Ollama's OpenAI-compatible endpoint
6
6
  base_url: http://localhost:11434/v1
7
7
  model: qwen3-coder:30b # ollama pull qwen3-coder:30b (19 GB; needs ~24 GB of memory)
8
- context_tokens: 32k # Ollama's default window is smaller: set OLLAMA_CONTEXT_LENGTH=40960 for `ollama serve`
8
+ context_tokens: 32k # Ollama's default window is smaller: set OLLAMA_CONTEXT_LENGTH=40192 for `ollama serve`
9
9
  fallback: developer-light # hosted Haiku, when Ollama isn't running or the model isn't pulled
10
10
  permission_mode: acceptEdits # edits are free; commands need a rule below
11
11
  allowed_tools: Bash(git add:*), Bash(git commit:*), Bash(git status:*), Bash(git ls-files:*), Bash(git diff:*), Bash(git log:*), Bash(git show:*), Bash(git rev-parse:*), Bash(git branch:*), Bash(pytest:*), Bash(python -m pytest:*), Bash(python3 -m pytest:*), Bash(python -m unittest:*), Bash(python3 -m unittest:*), Bash(uv run:*), Bash(uv sync:*), Bash(npm test:*), Bash(npm run:*), Bash(npm ci:*), Bash(pnpm test:*), Bash(pnpm run:*), Bash(pnpm install:*), Bash(yarn test:*), Bash(yarn run:*), Bash(cargo build:*), Bash(cargo test:*), Bash(cargo check:*), Bash(cargo clippy:*), Bash(go build:*), Bash(go test:*), Bash(go vet:*), Bash(make:*), Bash(swift build:*), Bash(swift test:*), Bash(ls:*), Bash(pwd), Bash(cat:*), Bash(tail:*), Bash(head:*), Bash(grep:*), Bash(wc:*)
@@ -73,7 +73,7 @@ Run `brindle` with no arguments to open (or reopen) a supervisor chat here, with
73
73
  the live dashboard underneath. Outside a git repo it starts a scratch session;
74
74
  `brindle transfer <repo>` moves that work into a real repository later.
75
75
 
76
- Paid features (hosted learning, per-worktree services, team policies, CI):
76
+ Paid features (hosted learning, per-worktree services, team policies):
77
77
  `brindle account` shows what you have and how to get the rest.""")
78
78
  agent_app = typer.Typer(no_args_is_help=True, help="Manage agents.")
79
79
  app.add_typer(agent_app, name="agent")
@@ -2603,7 +2603,7 @@ def mcp() -> None:
2603
2603
  ci_app = typer.Typer(no_args_is_help=True,
2604
2604
  help="brindle CI (brindle Team): the client the CI workflows run. "
2605
2605
  "`brindle ci init` sets a repository up.")
2606
- app.add_typer(ci_app, name="ci")
2606
+ app.add_typer(ci_app, name="ci", hidden=True)
2607
2607
 
2608
2608
 
2609
2609
  def _ci_call(fn, *args, **kwargs):
@@ -85,7 +85,7 @@ LAUNCH_CAPACITY = Cause("launch_capacity", "", "the provider refused work on cap
85
85
  # Not a refusal: the login itself lapsed, so the same call works again after the
86
86
  # provider's login command. Never recorded by ``refuse``, never retried or swapped.
87
87
  EXPIRED_LOGIN = Cause("expired_login", "", "the cloud login has expired",
88
- "run the provider's login command (`brindle ci doctor` names it)")
88
+ "run the provider's login command")
89
89
 
90
90
  _EXPIRED_MARKERS = (
91
91
  "could not load google cloud credentials", "invalid_grant", "invalid_rapt",
@@ -7,8 +7,11 @@ seconds to minutes, and it sits on the critical path of every branch.
7
7
 
8
8
  With ``pipeline`` on (the default), brindle runs those stages itself:
9
9
 
10
- 1. A worker reports (``report_result``). brindle starts the review at once
11
- and runs the repo's checks in the background.
10
+ 1. A worker reports (``report_result``). brindle gets the branch reviewed at
11
+ once (``agents.start_review``): with ``checks`` configured, a detached
12
+ ``_review-after-checks`` process runs them first and then starts the
13
+ reviewer with their results in its prompt; with none, the reviewer starts
14
+ right away.
12
15
  2. The reviewer approves: the branch is ready. brindle merges every ready
13
16
  branch of the same base (through the same gates ``merge_workspace``
14
17
  uses), the one whose hunks overlap the others' least first and the rest
@@ -49,6 +49,9 @@ FEATURES = (
49
49
  "`min_version`, `required_profiles`, `required_rule_packs`, `kill_switch` in your org policy (`brindle account org policy`)"),
50
50
  )
51
51
 
52
+ # Features that work as usual for whoever has them but aren't listed by `brindle account`.
53
+ UNLISTED = frozenset({"ci_fix", "ci", "ci_enterprise"})
54
+
52
55
  ENTERPRISE_CONTACT = ("Enterprise is set up with PawDelta, not bought here. Email support@pawdelta.com "
53
56
  "with your team size and where agents will run; we'll turn it on for your org.")
54
57
 
@@ -100,10 +103,6 @@ USAGE = """usage: brindle account [<command>] [--base-url URL]
100
103
  show, or turn on/off, pooling this org's coarse learning records with
101
104
  the other orgs in its company, never with other companies
102
105
  (off by default; owner/admin to change)
103
- org ci-token create <name> [--org ORG]
104
- create a CI token for brindle CI (admin+); shown once
105
- org ci-token list [--org ORG] list the org's CI tokens
106
- org ci-token revoke <token_id> [--org ORG] revoke a CI token
107
106
  license install <file> install an offline (brindle Enterprise) license; verified with the
108
107
  pinned keys, no network; used in air-gap mode and when not logged in
109
108
  license status show the installed offline license and the air-gap status
@@ -621,6 +620,8 @@ class ProAccount(_OrgCommands):
621
620
  self._say("brindle Pro: not logged in. brindle is complete without it; paid plans add:")
622
621
  self._say("")
623
622
  for feature, plan, what, how in FEATURES:
623
+ if feature in UNLISTED:
624
+ continue
624
625
  if feature in have:
625
626
  self._say(f" ✓ {feature:<15} {what:<50} {how}")
626
627
  else:
@@ -1327,7 +1327,7 @@ CODEX_INTERACTIVE_USES_PLAN = (
1327
1327
  "interactive Codex agents use your ChatGPT plan whatever key is set; "
1328
1328
  "to put them on a key, run `codex login --with-api-key`")
1329
1329
  CODEX_EXEC_BILLS_KEY = (
1330
- "headless `codex exec` runs (and Brindle-CI) bill CODEX_API_KEY instead")
1330
+ "headless `codex exec` runs bill CODEX_API_KEY instead")
1331
1331
  CODEX_INTERACTIVE_IGNORES_KEYS = (
1332
1332
  "interactive Codex ignores OPENAI_API_KEY and CODEX_API_KEY while signed in with ChatGPT and "
1333
1333
  "uses your ChatGPT plan; run `codex login --with-api-key`, or use auth: subscription")
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes