Hi, i'm trying to get the warp cli running on ubuntu, but every prompt ends with "The agent tried to execute a prohibited action".
How do I configure what the agent can do via CLI?
Thanks in advance
#The agent tried to execute a prohibited action
cosmic haven
bitter knollBOT
Hi @cosmic haven. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
The error "The agent tried to execute a prohibited action" in Warp typically means the agent attempted to run a command or perform an action that is restricted by your current permissions or denylist settings.
To configure what the agent can do, you need to adjust the AI permissions and command allowlist/denylist. While the knowledge sources do not mention a direct CLI method for changing these settings, you can manage them through the Warp UI:
-
Change AI Permissions: Go to
Settings > AIand set permissions such as "Create plans," "Apply code edits," "Read files," and "Execute commands" to "Always allow." You can also adjust the command allowlist to permit all commands if needed. This is confirmed by user discussions and suggestions in the Warp community, though some users note that these settings can be hard to find and may not always resolve every issue immediately Developer Too Full of Themselves. -
Command Denylist: If a specific command (like
sourceor others) is in the denylist, the agent will not be able to execute it, even if permissions are otherwise open. You can remove commands from the denylist in the same settings area YOLO mode doesn't work with all commands. -
Auto-detection and Agent Mode: If you want to prevent Warp from automatically switching to agent mode or triggering on certain commands, you can disable auto-detection or add commands to the denylist via
Settings > AI > Input Auto-detectionandAuto-detection denylistWarp automatically forces me into agent mode when i type certain commands.
Note: The knowledge sources do not provide a way to configure these permissions directly via the CLI. All configuration appears to be through the Warp graphical interface.
If you continue to encounter issues after adjusting these settings, ensure that the commands you want to run are not in the denylist and that all relevant permissions are set to "Always allow." If the problem persists, it may be a bug or a limitation in the current version of Warp.
Let me know if you need more detailed steps for the Warp UI, or if you encounter a specific error message!
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
cosmic haven
@bitter knoll via Warp UI I can do whatever I want. The problem happens by using warp via terminal when running "warp agent run"
bitter knollBOT
Let me check the knowledge base for you again. One moment! :books:
I'm sorry, but the knowledge sources do not contain specific information about configuring agent permissions or allow/deny lists when running warp via the CLI (such as with warp agent run) on Ubuntu or other platforms. All available details about adjusting agent permissions, allowlists, and denylists refer to using the Warp UI, not the CLI.
If you are encountering "The agent tried to execute a prohibited action" when using warp agent run, and you have already confirmed that permissions are set correctly in the UI, the knowledge sources do not provide further guidance on how to resolve or configure this via the CLI.
If this is blocking your workflow, I recommend checking for any updates in the official Warp documentation or opening an issue with the Warp team for more targeted support.
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
cosmic haven
@bitter knoll I just noticed that warp cli cannot create/write files
bitter knollBOT
Let me check the knowledge base for you again. One moment! :books:
Based on the knowledge sources, there are currently limitations with the Warp agent and CLI regarding file creation and writing. Multiple users have reported that the agent can read from Warp Drive notebooks but cannot write to them or create new files, even when using commands like warp agent run. The agent may attempt to execute commands (such as using warp-cli drive create-notebook) but these actions are not supported, resulting in errors or prohibited action messages.
This limitation is recognized by the Warp team and users have requested the ability for the agent to write to files or notebooks, as it is important for advanced workflows. However, as of now, this functionality is not available, and there is no documented way to enable file creation or writing via the Warp CLI or agent. The only workaround mentioned by users is to use regular markdown files in your codebase instead of relying on Warp Drive notebooks for write operations agent does not have access to the warp drive notebooks.
If you need the agent to create or write files, you will need to wait for this feature to be implemented in a future release.
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
cosmic haven
@bitter knoll "warp agent run" cannot event create a file in /tmp
bitter knollBOT
Let me check the knowledge base for you again. One moment! :books:
Based on the knowledge sources, there are known issues with the Warp agent and CLI being unable to create or write files, even in locations like /tmp. Users have reported that the agent can read files but not write or create them, and attempts to do so result in errors or messages such as "The agent tried to execute a prohibited action" or simply no changes being made. This limitation is present both for Warp Drive notebooks and for regular file operations, and it affects both the UI and CLI agent modes. There is currently no documented way to enable file creation or writing via the CLI or to configure permissions for this in the CLI settings. The Warp team is aware of this limitation, and users have requested this feature, but as of now, it is not supported in the CLI or agent mode agent does not have access to the warp drive notebooks In Linux Light mode does not write files.