Running Longer Work

Some work needs something to keep running while CodeBot continues: a local web server, a file watcher, a test host, or a longer investigation loop. CodeBot can manage that kind of work without losing track of it in the chat.

Ask CodeBot to Start a Local Server or Watcher

CodeBot can start a long-running command, give it a name, keep it associated with the current chat, and continue working while it runs.

Typical prompts:

• "Start the dev server and give me the URL."
• "Run the test watcher while you make changes."
• "Start a local web server for this HTML file."

Starting a managed process requires approval because it runs a command on your machine.

Ask CodeBot to Check Running Processes

CodeBot can list managed processes it started, show whether they are still running, and read captured output.

Typical prompts:

• "Is the dev server still running?"
• "Show me the latest server output."
• "Read the test watcher output since last time."

This is useful when a verification step spans multiple chat turns.

Ask CodeBot to Stop a Process

CodeBot can stop a managed process by name or ID, or stop the only running managed process when there is no ambiguity.

Typical prompts:

• "Stop the dev server."
• "Shut down the watcher."
• "Stop any managed process you started for this task."

Ask CodeBot to Work Through a Longer Task

For larger tasks, CodeBot can run a longer agent-style loop that keeps making progress, reporting status, and using tools as needed.

Typical prompts:

• "Work through this migration and keep me updated."
• "Investigate the failing tests until you find the root cause."
• "Review this module and create a prioritized fix list."