Review open tickets
In Project settings → Agents, use a bounded backlog review to find missing details and possible next steps. The current review looks at up to 20 open tickets and suggests up to three next steps.
Review the total cost before starting. Suggestions stay linked to the tickets they concern. The team makes the decisions; the review does not approve work, publish changes or close tickets.
Optional watch stays off until selected and has a daily allowance inside the project’s shared pool. Review its budget before enabling it.
What a quoted review includes
- Review open tickets · 20 project units. Up to three useful next steps from up to 20 open tickets.
- Investigate one ticket · 20 project units. Observations, possible explanations and the next checks for one problem.
- Prepare an implementation brief · 20 project units. Suggested implementation steps and checks for one improvement.
These Astor-funded jobs require an enabled Agents connection and project access. They use available project units, including Free or Pro's monthly allowance; a separate review subscription is not required. Read the total before starting. Necessary follow-ups within the accepted work are included; a larger assignment requires a new total and approval.
New managed reviews retain their accepted model, unit allowance and cost-estimate ceiling through retries. A settings change does not rewrite the accepted job. An interrupted or stopped review can still have a provider cost even when project capacity is returned; estimates are not reconciled invoices.
Astor checks current permission before sending further ticket context. If the person who started the review loses access or its time limit is reached, the review stops. Capacity stays reserved until the remote service confirms that work has ended. Delayed replies cannot replace a confirmed stop or an already saved result. This does not remove context already sent to the service.
A permitted API or MCP connection can request a one-ticket investigation or implementation-brief suggestions. Read get_agents for availability and the review cost. These managed jobs use the backlog quote, including when their task is investigate or brief. The result contains suggestions and implementation steps for review; it leaves the ticket and its approved scope unchanged.
Local Codex investigation and planning have separate quotes. They require an installed, verified local connector and the connected person's provider account; they are different from the managed reviews above.
What a review shares
Backlog reviews send masked ticket briefs, recent clarification answers, summaries of linked feedback and results, and approved project context to OpenAI’s managed sessions. The service retains session history; this connection currently uses US data residency. Private comments, recordings, screenshots and unfinished drafts are excluded. Review the information you put in a brief before starting.
Connect development tools
Open your profile menu and choose Connected tools. If your installation offers a local connector, open Local code connection → Connect a local repository. A connected repository instead shows Manage Codex connection. The local Codex connector uses the connected person’s Codex account and works within configured repositories.
Investigation and planning use read-only access. Implementation and testing use an isolated task worktree. The current local connector runs one job per project at a time.
The quoted Astor capacity and any usage billed by the connected tool’s provider are separate. Review both before starting. A GitHub remote appearing as repository information does not mean a pull request or deployment has happened.
Continue the same local task
Where an installation provides local tasks, a new task saves its accepted units and total execution time. A necessary continuation keeps the same approved work, code connection, account, model and saved thread. It does not receive a fresh time allowance. Once the original deadline stops a task, a rounded timer value cannot leave a new turn available.
Continuing successfully completed work within that allowance adds no project units, including when the pool is empty. If a failed or interrupted attempt returned its reserved units, retrying reserves the original accepted amount once. Failure of an included continuation does not refund earlier completed work. The connected provider can still charge for its usage separately.
Saved output remains readable after the time allowance is exhausted or the source or connection changes. Review a separately bounded task and its total before starting more work. Older tasks without saved accepted terms cannot silently receive a new allowance. This does not enable local tasks in an installation that does not offer them.
Review the result
Reviews distinguish waiting to start, preparation, running and a stop awaiting confirmation. Review status not confirmed means Astor has not confirmed whether that review is still running.
Inside a ticket, Full brief & checks also shows the saved investigation or implementation-brief task. Its state distinguishes waiting, preparation, running, stopping and Status not confirmed. Updated is the last recorded task update, not the time you opened the page. Open What Astor received for this task to inspect the input; reading it starts no job.
Saved results remain readable with no available project units. Open Improvements in this review for the ticket list, or use Review ticket beside a recommendation. Reading and refreshing do not start another review.
Read the report, changes and tests. Check the actual behavior against the agreed ticket. Stop or resume work deliberately; an agent’s completion is not human approval or verification.
Where a verified local connector provides saved before/after screenshots, they require current project and development access. A missing capture returns 404; an unavailable or forbidden source returns its actual access error instead of a blank successful image response. Saved screenshots are not verification of the change.
Local code review checks current access while reading the changes. If your sign-in, project permissions or the run's code source changes during the read, it returns an error without the code. Reload the current review after resolving access; this does not start or resume an agent job.
If a tool is not connected or an AI service is unavailable, use manual review and an ordinary builder handoff. External tools need their own supported connection. Current bounded reviews and local jobs use quoted project capacity. Separate prepaid Astor work budgets are planned; general cloud coding agents are not available. Your existing plan and agreement are unchanged.