The author reports using GPT-6.2 Astra as an adviser and three GPT-6.2 Sol agents to do the work on development optimization tasks. He says this setup was faster, used fewer quotas, and more often produced successful optimizations than his previous GPT-6 Astra + GPT-6.1 Sol setup, but he did not disclose the actual prompts or agent orchestration details.
Suitable tasks: Development work that involves proposing and implementing code performance optimizations; this can be treated as a multi-agent division of labor to test.
Unsuitable uses: The post is not enough to reproduce the author's specific agent scheduling, and its subjective speed and quota results should not be treated as guarantees.
Applicable model versions: The author reports using GPT-6.2 Astra and GPT-6.2 Sol; the previous comparison setup was GPT-6 Astra and GPT-6.1 Sol.
Applicable client, agent, or API: The post is in a Codex context; it does not specify the exact version, execution mode, or agent configuration.
Recommended reasoning level and parameters: Not specified.
The post describes an adviser and three worker agents. The English translation below is of the editorial example based on those roles.
First inspect this code optimization task, propose measurable optimization directions, and explain the expected benefits and risks.
Have three independent worker agents implement candidate approaches separately. Each agent should change only its own approach and record its changes and verification results.
Compare the candidates' performance and regression results. Keep changes only when their benefits are clear and verification passes; report anything not verified and how to roll it back.Roles actually disclosed by the author: GPT-6.2 Astra provided advisory support, while three GPT-6.2 Sol agents did the work. The post says the work involved proposing and implementing optimizations, and that regression testing slowed development less; it does not explain each agent's separate responsibilities, parallelization, handoffs, testing gates, or acceptance criteria.
Independently assembled trial steps (not a reconstruction of the author's method):
Choose a code optimization target with a benchmark, and record the before-optimization performance and regression baseline.
Ask Astra to suggest candidate directions and risks; have three Sol agents implement separate candidate approaches, avoiding simultaneous edits to the same code.
Run the same benchmarks and regression checks on each candidate, compare performance gains, correctness, and manual review cost, then decide whether to adopt it.
The author wrote: “I'm using GPT-6.2 Astra as an advisor to run three GPT-6.2 Sol workers.” This directly supports the role relationship; “run” does not reveal the specific orchestration method.
The author said he kept the setup he'd used with GPT-6 Astra and GPT-6.1 Sol. With the new models, he reported completing optimizations about twice as fast and using about 25% less of his quota. The post gives no timing definition, quota accounting method, sample size, or raw records.
The author said that previously he would typically keep one or two of ten attempts, often with only modest speedups. He now feels that more optimizations succeed, the speedups are more noticeable, and regression testing slows development less. He gave no new success rate or quantitative regression-testing data.
In the comments, the author responded to one criticism only with a joke; no additional details appeared about the actual prompts, Codex configuration, or how the agents worked.
The results come from one user's experience with development optimization work. The effects of the model, task, codebase, agent setup, or other workflow changes cannot be distinguished.
“Twice as fast” and “about 25% fewer quotas” have no baseline period, task count, measurement method, or reproduction materials, so they should not be treated as expected gains for other projects.
The post does not say whether Astra directly called or scheduled subagents, or how the author organized the three GPT-6.2 Sol worker agents. It also does not disclose the models' reasoning levels, prompts, tool permissions, concurrency, test cases, or acceptance criteria.
The independent example in this article is only a draft division of roles for trial use. It does not reproduce the author's setup and is not a validated best practice.
To evaluate this division of labor, compare a single-agent baseline with an adviser plus three worker agents using the same codebase, task set, test conditions, and quota accounting method. Record completion time, quotas, the number of optimizations that pass regression checks, and manual review cost. The original post does not provide enough detail to reproduce its results.
GPT-6.2 Astra