YOUR DEVELOPER IN A SANDBOX
Describe the work, choose a model, and start your developer. Every task gets its own workspace.
Drafts are editable. Starting the task requires login.
2 · Describe the task
Choose where this task starts.
Repository-creation destinations for the agent's GitHub account.
Sign in to create and manage tasks.
Anyone with this link can view this task's conversation and status without signing in. They cannot send prompts or control the task.
The controller's mounted ConfigMap text. Workers reread instructions before each turn. Kubernetes propagates updates asynchronously; a turn already running keeps its starting instructions.
Repository and organization webhooks are supported. Assign an issue to the configured agent's GitHub user to start work. Issues assigned to other users are ignored. Assignment creates a Task; later eligible issue events and comments resume the same Task. The configured user must have repository access.
Merges of PRs linked to a Task wake that same Task, even in a different repository. Periodic GitHub API checks cover repositories without a configured webhook.
Mat sends task-bound email through the controller's SMTP account. Reply normally from a recipient address: In-Reply-To and References route the IMAP reply to the original Task. Replies enqueue an attributed prompt; they do not automatically post GitHub comments. Unmatched mail does not create Tasks. Mail settings come from IMAP_* / SMTP_* environment variables; credentials come from Secrets.
Add a receiver and route the desired alerts to it. Repeated fingerprints resume the same Task; resolved notifications do not mark code work complete.
POST an existing Task ID or GitHub issue URL with a stable delivery ID. Authenticate with the receiver bearer token.