[bug] background subagents in auto mode flood me with permission prompts for safe…
Maintainers usually reply within 5 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 18/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- bun, shell, typescript
Research direction
Start with the LifeOSHooks tool.call hook and the SubagentGitSandbox class with its wrapInline method, which the report says wrap every subagent Bash command in sandbox-exec. Check how the hook's changed input leads to the "gave no verdict" result in auto mode, and reproduce with a background subagent running ls. Done means safe read-only subagent commands are judged without reaching the human, while the git-internals protection still holds.
Written by the indexing model from the issue text.
Description
What happened
background subagents in auto mode flood me with permission prompts for safe commands, 15-20 clicks in a few minutes
Summary
In auto mode, a background subagent's Bash calls often get no verdict from the auto-mode reviewer and end up as permission prompts for the human, even for read-only commands.
Cause, from reading the code and the message Claude Code returns: the LifeOSHooks tool.call hook wraps every subagent Bash command in sandbox-exec (SubagentGitSandbox, wrapInline). Claude Code then reports "gave no verdict: a hook changed this call's input after the model wrote it, so the review was of different input from what would run", adds "This is not a judgment that the action is unsafe", and tells the model to issue the call again once.
Seen on 8.761.0 with four background subagents: about 15-20 prompts within a few minutes, for work that only read files. The same command type passes in the main session, which is not wrapped. It is intermittent (bun test passed while ls and bun Places.ts did not), and the agents copying the wrapped text into their retry adds more prompts.
Expected: the git-internals protection stays, and safe subagent commands are judged without reaching the human. The current workaround is telling subagents not to use Bash at all, which rules out any subagent that has to run tests, so unattended work is not practical.
Details
- Kind: bug
- LifeOS version: 8.761.0
Filed with the LifeOS /feedback command. The reporter approved this exact text before it was sent; paths, secrets and personal details were stripped locally.
- Dominant language
- TypeScript
- Stars
- 19.9k
- Forks
- 2.5k
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from danielmiessler/LifeOS
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
danielmiessler/LifeOS#2894 ·
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
danielmiessler/LifeOS#2891 ·
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
danielmiessler/LifeOS#2888 ·
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
danielmiessler/LifeOS#2886 ·
Maintainers usually reply within 5 days
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
danielmiessler/LifeOS#2848 ·
Maintainers usually reply within 5 days
All issues in danielmiessler/LifeOS
Similar issues
-
ready-for-agent
Difficulty 1/5 Under an hour Newbie friendliness 86/100
LucasSantana-Dev/Lucky#3257 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
XiaomiMiMo/MiMo-Code#2849 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement frontend good first issue help wanted testing-infrastructure
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 2 days
-
enhancement follow-up
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
obsidian-tasks-group/obsidian-tasks#4155 ·
Maintainers usually reply within 1 day