AOSplane for planning and checking coding agent pull requests

AOSplane manages coding work handed to agents such as Claude Code or Codex. It is aimed at teams that want a spec, a review and evidence from tests attached to a GitHub pull request before a person decides whether to merge it.

From an issue to a draft pull request

A team can start work in the console or from a Linear or Jira issue. In the Plan first workflow, a planning step drafts acceptance criteria and checks for them before code is written. A person can review and approve the plan. The coding agent then runs in an isolated cloud sandbox. Review reads the change, and a separate QA step runs repository checks and checks tied to the acceptance criteria.

The resulting pull request is a draft. A reviewer can read what the agent changed and see which checks it ran. The setup still depends on the team providing a usable repository and specifying what counts as a good change; a passing test only addresses the behavior the test covers.

Model accounts and spending limits

AOSplane runs agents using the provider accounts that customers connect. The publisher says model charges go directly to the customer’s provider. Its platform checks spending limits for the agent, project and company before it starts a run. Those limits do not stop an already running task. The terms also say approval gates cover only the actions configured to require approval.

Starting on the free plan

The FAQ lists two projects, two simultaneous tasks per project, small machines and seven days of history on Free. It also lists a $5 monthly usage credit. Paid plans start with a conversation with the company. A team comparing the two can first try one repository and check the evidence attached to a small draft pull request.