Repository navigation
Bug: .autocoder/config.yaml and {projectdir}/.autocoder/allowed_commands.yaml have no effect #91
Description
Hi!
I tried to run autocoder in an already existing project (!) to add some features using three concurrent agents, but Claude is trying to run commands which are not allowed in the first place. And autocoder does not ask for approval as stated in the README. I tried to extend its capabilities via the mentioned files, either global or project-wide, but nothing works. I always get messages like
[Feature #392] Input: {'command': './venv/bin/python -m smtp2graph &> /tmp/smtp2graph.log &', 'description': 'Start server in background using venv python directly'}
[Feature #392] [BLOCKED] Command 'python' is not allowed.
[Feature #392] To allow this command:
[Feature #392] 1. Add to .autocoder/allowed_commands.yaml for this project, OR
[Feature #392] 2. Request mid-session approval (the agent can ask)
[Feature #392] Note: Some commands are blocked at org-level and cannot be overridden.
Regards,
Holger
Activity
fix: add diagnostic warnings for config loading failures (AutoForgeAI#91
ipodishima commentedon Jan 26, 2026
Hi
I've been working on this feature and it works for me.
However, disclaimer: phase 3 = ask mid flight approval is not implemented yet. Sorry, logs are misleading, didn't catch that.
What works though (working rn with my flutter project) is allowed commands on a project basis, but after a change, i restart the server to make sure it picks up the new config. Please lmk!
fix: add diagnostic warnings for config loading failures (AutoForgeAI#91
feat: Implement iteration limits for graph algorithms (Feature AutoFo…
docs: Update progress notes for Feature AutoForgeAI#91 completion
fix: add diagnostic warnings for config loading failures (AutoForgeAI#91
fix: add diagnostic warnings for config loading failures (AutoForgeAI#91
fix: add diagnostic warnings for config loading failures (AutoForgeAI#91