Tasks, automation and scheduled chats
Tasks track work inside a PHPSandbox project. Open Tasks from the workspace toolbar. Project settings contain automation sources and schedules; a task’s detail view shows its events, runs and review actions.
Turning project tasks on
Tasks and isolated workspaces require the current organization’s subscription entitlement. Without it, Tasks and Automation settings remain discoverable and show an upgrade prompt. There is no per-user opt-in. An authorized project manager can configure the project’s automation policy after access is available.
What happens during a task run
Ordinary chat changes the active sandbox. Manual and source-driven tasks use isolated sandbox forks so their output can be reviewed before merging into Main.
A completed task becomes ready for review. Inspect the changes, then merge the fork into Main or discard it. Completion does not automatically merge the result. If Main changed or the changes conflict, review the merge again before proceeding.
GitHub is optional for this fork-and-review workflow; it is not the storage layer for task output.
Sources and connected tools
Project settings can enable sources such as GitHub, Laravel Nightwatch and Sentry. Connect the relevant integration and configure the source policy before relying on incoming events.
GitHub tasks can also produce draft pull requests when that project policy is enabled. Sync Main first when repository state prevents creating a pull request.
Webhook URLs and secrets
For a Sentry or Nightwatch source:
- Open Project settings from the sliders control in the workspace toolbar.
- Open the source’s automation settings and copy its webhook URL.
- Configure that URL in the source system.
- Save the webhook secret in the source settings and enable the source.
Keep secrets in the owning secure form. Connecting an MCP server supplies agent tools; it does not by itself configure incoming webhook events.
Retriggering a task
Open the task’s detail view and use its retrigger action after correcting the cause of failure. Inspect the previous run and error first. Retrying an existing task preserves its history instead of creating duplicate work.
Scheduled chats
Ask the agent to schedule a one-time or recurring chat, or manage schedules in Project settings. Provide the instruction, when it should run and its time zone.
A schedule can continue an existing conversation, create a new conversation for every run, or create one conversation on the first run and continue it later. Review which destination was selected. Use the schedule’s menu to pause, resume or edit it.
A scheduled run uses the normal agent workflow and the permissions and account availability that apply when it runs. A schedule is not proof that an external operation succeeded; inspect the run’s result.
Review automation policy before enabling sources
In Project settings, Automation controls whether source-driven tasks run for this project. Require source connection makes external tasks wait for the matching connected tool before work starts. These project policies are separate from the organization’s subscription entitlement.
For GitHub issue tasks, the source settings can also enable draft pull requests when completed work becomes ready for review. A draft PR is an additional review destination; the sandbox fork remains available for review and merge into Main. If Main is ahead of the tracked GitHub branch, sync it before publishing that task’s PR.
Before relying on automation, confirm that the source is enabled, its webhook secret is configured where required, its tools are connected when the policy requires them and the team knows who reviews the resulting fork. Review or discard finished forks rather than leaving old output to accumulate while Main changes.