Skip to content

system prompt talks about running commands even without execute_command tool #585

@RayCarro

Description

@RayCarro

In modes without command access, a bunch of these lines are useless or even harmful, but they cannot be removed or replaced.

  • You have access to tools that let you execute CLI commands on the user's computer
  • You can use the execute_command tool to run commands on the user's computer whenever you feel it can help accomplish the user's task. When you need to execute a CLI command, you must provide a clear explanation of what the command does. Prefer to execute complex CLI commands over creating executable scripts, since they are more flexible and easier to run. Interactive and long-running commands are allowed, since the commands are run in the user's VSCode terminal. The user may keep commands running in the background and you will be kept updated on their status along the way. Each command you execute is run in a new terminal instance.
  • most of these lines: https://github.com/Zoo-Code-Org/Zoo-Code/blob/main/src/core/prompts/sections/rules.ts#L74-L92

These lines should maybe be conditional on if command access is allowed, or at least allow us to overwrite these per mode.

I exported and imported the Code mode, gave it custom tools for build and test, and removed its command permission. I kept it with the same slug code so it overwrites the built-in mode. But these lines are still in the system prompt.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request
    No fields configured for Feature.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions