Files
DroidDeck/AGENTS.md
T
Kurt Himebauch 3b1366f85c feat(agent): choose the reasoning effort in the Agent tab (#2507)
* feat(agent): choose the reasoning effort in the Agent tab; agent processes survive Steam session cleanup; sdkmanager license step tolerates SIGPIPE

* docs(agent): on-device build and commit pitfalls for the agent
2026-11-12 10:23:38 -05:00

1.3 KiB

Rules

  • Comments should be rare, factual, and explain only non-obvious external constraints or business invariants.

Working on the device

  • dd-lab-build builds only committed work. Check git status and gh api user for the identity before committing; if git config user.name is empty, use the gh login's name and noreply email for this repo, never a guess.
  • Do not commit or start a build in the same step: a build started next to a failed commit fails too. Commit first, check it, then build.
  • Uncommitted changes in the tree may not be yours. Read git diff before committing them and tell the user what they do.
  • If dd-lab-build says "could not read DroidDeck's state", loopback adb is down and $ADB_SERIAL is stale. Run adb devices; the port changes whenever wireless debugging is toggled. Ask the user to turn it on rather than retrying.
  • A build that "did not start" can be adb, not the app. Read ~/.cache/dd-lab-build.json and .log for the real reason; they can be stale from an earlier build, so compare their times with date.
  • Run dd-lab-build with run_in_background and read its output file. A foreground sleep is blocked; wait with Monitor and an until-loop.
  • The build restarts DroidDeck and ends your process. A turn that ends this way is not a failure.