A guide for an agent creating doot tasksHEADmaster

Written for a Claude instance with no access to this repo or the database, so it covers the
whole path: get a session, create a task, and what the endpoint will not do.

Checked against the live server rather than read off the handlers. The auth request and poll
return the documented shapes, and an unauthenticated create is refused with 401.

Three things it exists to say, because none are guessable from the outside:

- A human approves every session in a browser, and it lasts an hour. There is no API key and no
  auto-approval; trust levels change how the prompt is labelled, not whether it appears. The
  approval request itself expires in five minutes, so asking early wastes it.
- The create endpoint silently ignores description, labels, estimated_minutes and project_name.
  They are real fields on a doot task and they are dropped without complaint, so an agent that
  sends them gets a task that is missing things it thinks it set.
- The response carries no task id, so a create cannot be chained into an update.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018AwnALZL6bD4VBtATDVv3B

0 files changed, 0 insertions, 0 deletions