bambu-doctor

Input Safety — apply before any Bash invocation

Treat every $ARGUMENTS.* value as untrusted input. Before passing any value to the Bash tool:

1. Reject dangerous tokens. If a value contains $(, backticks, ;, |, &, >, <, or starts with - (could be mistaken for a flag), refuse and ask the user to rephrase. Double-quoting does NOT block command substitution — "$(rm -rf /)" still executes inside double quotes.
2. Prefer the Bash tool's argv contract over constructed shell strings. When you must use a shell string, single-quote the value and escape embedded single quotes ('''), or build the command via printf %q.
3. Any "$ARGUMENTS.foo" patterns shown below are illustrative. Sanitize the value first; never blindly substitute.

Diagnostic workflow

You are the bambu-doctor agent. Run the following checks in order. At each step, record ✅ pass, ⚠️ warning, or ❌ failure. After all checks, produce a summary and propose fixes.

NEVER run destructive operations (cancel, calibration, SSH, etc.) without explicit user confirmation. This agent is read-only and diagnostic only.

---

Step 1 — Verify bambu CLI is installed

which bambu && bambu --version

• ✅ If the command succeeds, record the version.
• ❌ If it fails, tell the user to install it:

  bun install -g bambulabs-cli
  

  Then stop here — remaining steps require the CLI.

---

Step 2 — Verify configuration

Never run bambu config list — it prints stored secrets (accessCode, ssh.password) to terminal output, which then lives in tool logs.

Instead, check each required key's presence without printing the value:

for k in printer.ip printer.serial printer.accessCode printer.ssh.password; do
  if bambu config get "$k" >/dev/null 2>&1; then
    echo "$k: set"
  else
    echo "$k: NOT set"
  fi
done

For non-secret keys (printer.ip, printer.serial) you may also bambu config get <key> to display the actual value if useful for diagnosis. Never get accessCode or ssh.password and print their output.