Security

Navin Git kill-switches: cut auto-branch and auto-PR machine-wide

Q: Where in the UI?

Settings → Security → Git section.

August 5, 2026 · 2 min read · Navin team

Settings > Security > Git: two global switches that override project consent. Powerful autonomy, instant operator brake.

Board autonomy is powerful. Git kill-switches are what make it enterprise-acceptable: you can consent per project… and cut machine-wide in one second when needed.

Two global toggles live in Settings > Security > Git (and in ~/.navin/config.json). They override local consent.

The two switches

Toggle	Effect when OFF
Task auto-branch	No project creates a `navin/task-*` branch on claim, even with Autonomy ON
Pull request on task done	No project opens an auto-PR on `done`, even with Autonomy ON

Project consent (.navin/board/settings.json) × global kill-switch = effective permission. The autonomy UI warns when a global switch is off.

Config

{
  "tools": {
    "boardGit": {
      "autoBranchEnabled": false,
      "openPrEnabled": false
    }
  }
}

Both default to true. Turning them off via Settings persists in the operator config - not in the repo.

Why Security, not Runtime

These are not comfort preferences: they are control guardrails. Placing them next to agent permissions and git deny rules (reset --hard, push --force, …) keeps the mental model clear:

project: do I allow autonomy?
machine: may this machine automate git?
shell: does this destructive command still need my OK?

See also board autonomy and the "Never lose work" section.

Real scenarios

Situation	Setting
Personal laptop, full power	Both ON + project Autonomy ON
Shared / CI machine	Auto-branch OFF or Open PR OFF
Security audit	Both OFF machine-wide
Client demo	Open PR OFF (local branches OK)

What kill-switches do not do

They do not disable the board or board next / manual claim.
They do not replace project consent (still required to chain).
They do not bypass shell approvals for force-push / hard reset.

FAQ

Can a project force auto-PR if global is OFF?

No. Global always wins.

Where in the UI?

Settings → Security → Git section.

Link with Deny rules?

Complementary: kill-switches cut board automation; deny rules intercept dangerous git typed in the shell.

Download Navin · Features · Autonomy docs

Conclusion

Autonomy without a kill-switch is blind trust. A kill-switch without autonomy is a useless brake. Navin offers both - and the global lives where you expect security.

Try Navin on your machine

Local agent, cross-platform. Code, debug, scrape, leads, security and review - without leaving Navin.

Download See features