Building, Running, and Debugging

In Fire and Water, CodeBot can use the IDE's normal build, run, deploy, test, publish, and debugger workflows. This lets CodeBot verify changes in the same environment you use.

Ask CodeBot to Build or Test

CodeBot can start a background build and inspect compiler messages afterward. It can also start EUnit tests when the solution supports them.

Typical prompts:

• "Build the solution and summarize failures."
• "Run the tests and explain what failed."
• "Fix the first build error, then build again."
• "Check whether this change introduces warnings."

Build and test actions can take time, so CodeBot reports progress in the chat.

Ask CodeBot to Run, Deploy, or Publish

CodeBot can launch the active project in the debugger, run it without debugging, deploy to a device or server, or publish publishable projects through the IDE flow.

Typical prompts:

• "Run this in the debugger."
• "Launch without debugging after the build succeeds."
• "Deploy the active project."
• "Publish this project."

Use these when the task needs the IDE's configured targets, devices, or publish settings.

Ask CodeBot to Inspect a Debug Session

CodeBot can inspect debugger state, output, breakpoints, expressions, locals, registers, threads, frames, modules, and disassembly.

Typical prompts:

• "Why did we stop here?"
• "Evaluate this expression in the current frame."
• "Show locals and the call stack."
• "Set a breakpoint here and continue."
• "Inspect disassembly around the current instruction."

Debugger actions can change runtime state, so CodeBot should be explicit about what it is doing.

Ask CodeBot to Drive a Debugging Loop

For harder runtime bugs, CodeBot can run a structured observe, step, continue, pause, and stop loop while reporting what it learns.

Typical prompts:

• "Debug this crash and stop before changing code."
• "Step through until the value becomes nil."
• "Observe the failing run and explain the root cause."