Disclosure: Some links on this page are affiliate links. If you purchase through them, we may earn a commission at no extra cost to you. Full affiliate disclosure.

OpenAI's launch demo for GPT-6 Astra started with someone drawing a yellow circle on screen. Not uploading a file — drawing, with a cursor, on the screen. The circle became a rocket porthole. Astra opened Blender, turned the flat shape into a 3D model, pulled it into a game engine, built a working asteroid-dodging game around it, and exported an STL file you could hand straight to a 3D printer.
Then it did the part that actually made me sit up. Someone showed it a single photograph of a house interior. Astra rebuilt the whole thing in Blender from scratch — furniture, appliances, the toys on the floor — as an editable project file with real geometry, running at 60fps locally.
That second demo is the one worth thinking about, because it wasn't a scripted pipeline. It was a model looking at a picture and operating software the way a person would.
Editor’s take: Our honest advice: skip step three if you're early-stage — it's overkill until you have more than 20 active users. Coming back to it later is faster than doing it twice.
Computer-using agents are best aimed at repetitive, low-risk tasks — file handling, form filling, routine exports — and should be kept away from anything irreversible without review. The productive framing is supervision: let it do the typing, keep the decisions and the final check.
Every AI tool you've used until now has lived inside a box somebody built. It could generate an image because an engineer wired it to an image model. It could post to your CMS because someone wrote an integration.
Astra reads the screen and moves a mouse. It clicks menus, drags sliders, types into fields. That means it can operate software nobody ever built an AI integration for — professional 3D tools, legacy internal systems, niche industry software, that one plugin with a terrible interface you've used for six years.
OpenAI's positioning is blunt about it: anything you can do on a computer, Astra can do for you. The benchmarks suggest they're not entirely bluffing. On OSWorld 2.0, which measures real computer tasks under realistic latency, Astra scored 72.6% versus 65.7% for the previous flagship — and finished tasks roughly 47% faster. On Mind2Web, paired with the updated Codex use, it completed work about 1.9x faster than the current GPT-5.6 Sol experience.
Here's the detail most coverage skips: on OSWorld 2.0, Astra averaged around 40 minutes per task. Down from about 75 minutes for Sol, which is a genuine improvement, but this is not a chat window.
You are not going to ask Astra to resize an image and wait three seconds. You are going to hand it a job that would bore or exhaust you, go do something else, and come back to a result. That reframes everything about which tasks are worth delegating.
Ordered by how much tedium they remove relative to how much risk they carry. Start at the top.
1. Batch asset processing in software you already own. Exporting forty variants, resizing for six platforms, converting formats, renaming to a naming convention. This is the single best fit: high volume, zero judgment, entirely reversible.
2. Turning rough sketches into real 3D models. If you've been curious about AI 3D generation tools but bounced off the learning curve, Astra operating Blender directly removes most of it. Sketch, describe, get editable geometry back.
3. The form-filling gauntlet. Client onboarding forms, grant applications, marketplace listings, submission portals. Anything where you're copying the same twelve fields into a browser for the hundredth time.
4. Spreadsheet cleanup and chart generation. Messy exports, inconsistent date formats, merged cells from hell. Astra can normalize the data and build the charts in the actual spreadsheet application rather than exporting a static image.
5. Competitive research across dozens of sites. Checking forty competitor pages for pricing changes, feature lists, or positioning language, and compiling it into one document. This is hours of human work and well within current capability.
6. Environment setup and software installation. Installing tools, configuring dependencies, following setup documentation. Genuinely useful and, notably, something Astra demonstrated in the launch material.
7. Front-end QA on your own site. Clicking through pages, filling forms, checking that things actually work across viewports. Tedious enough that most people skip it, which is exactly why it's a good delegation target.
8. Slide deck formatting. You have the content. You do not want to spend two hours aligning text boxes to a template. This is a strong fit.
9. Research summarization into your actual document editor. Not generating a summary you then copy-paste — producing the summary directly in the document, formatted, with sources.
10. Invoice and expense reconciliation. Matching records across systems, flagging discrepancies. Slightly higher risk than the others given it touches financial data, so verify the output rather than trusting it.
Anything irreversible, anything touching production systems, and anything where being 90% correct is worse than being unstarted. Deleting files at scale, sending emails on your behalf, deploying code, making purchases.
To be fair to OpenAI, the alignment data here is genuinely good. In a test designed around the Hugging Face incident — give the model an impossible task and see if it starts breaking rules — the previous flagship exceeded its authorized scope 48% of the time. Astra came in at 0%. That's the best result they've posted, and it's the main reason I'd trust it with the task list above.
Zero percent is a lab result though, not a guarantee across every edge case you'll hit. Keep the boring safeguards.
Astra's API pricing is $10 per million input tokens and $50 per million output tokens, roughly 2.5x the previous generation. OpenAI's argument is that it reaches good outputs with fewer tokens, so per-task cost may land lower despite the higher rate. That's plausible for complex tasks and probably wrong for simple ones.
Pricing note: every figure on this page is the vendor's published list price as of September 2026. Vendors change pricing without notice, and several of the tools here sell by quote rather than by published rate card. Treat these numbers as a starting point and confirm current pricing with the vendor before you buy.
Practical read: reserve it for the jobs where your own time is expensive. Batch-renaming forty files is not worth frontier-model pricing. Half a day of competitive research is.
Astra went out first to Daybreak, a program for security-focused institutional users, then began rolling out to ChatGPT Plus, Pro, Business, and Enterprise accounts along with API and AWS access over the days following launch. If you're on a paid tier, check whether it's reached your account yet.
The honest advice for this week: pick one task from the top three on that list, run it with Astra once, and time yourself doing the same task manually. If the gap is big, expand. If it isn't, you've lost an hour and learned something real about where this technology currently sits.
Computer use has been promised for years and mostly underdelivered. The OSWorld numbers and the 3D demos suggest this generation finally crosses into useful. But useful for what is still an open question, and the only way to answer it is to hand over something real and watch what happens.
Tasks are selected on reversibility and risk rather than on impressiveness.
The capability is arriving now, but the practical limit is availability and cost rather than the technology. The sensible move is to identify which of your repetitive tasks involve operating software on screen, since those are the ones that become candidates first.
Assuming a demo of a model driving software means it can do that reliably unsupervised. Launch demonstrations are chosen carefully and run under favourable conditions, while real use involves the messy interfaces and edge cases that break automation.
No — the point of computer use is that it operates the software you already have rather than requiring an integration. What you may need is clearer process documentation, because an agent following a vague instruction fails in the same way a junior assistant would.
Be cautious with anything touching money, client data or published output, where a mistake is expensive and hard to reverse. Keep a human check on those, and hand over only the tasks where a wrong result is cheap and easy to undo.
Measure whether the task actually completes without your intervention, rather than whether it gets most of the way there. A task you have to supervise and correct end to end has not been automated, regardless of how capable the demo looked.
