Notes from the build.
Product updates, engineering notes, and company thinking — including the parts that are unfinished.
Product
· 5 min read
Computer-use AI agents and human approval: what to ask before you trust one
AI agents that click and type on your computer are arriving fast. Here is a plain checklist for when an agent should stop and ask you first — and how ORION by iMpact handles it.
Company
· 3 min read
Introducing the ORION progress tracker
A single page that shows how far along ORION is, milestone by milestone, linked to our public GitHub repository.
Product
· 4 min read
ORION AI update: plans you can keep
This month's ORION AI update: why saved plans and a readable activity history matter more than new tricks, and what we are working on next.
Engineering
· 5 min read
AI work automation: measure one task before you automate ten
The second post in our monthly automation series: how to time a repeated task, define a good outcome, and decide if AI task planning is worth it.
Engineering
· 4 min read
Autonomous computer bots: design the permissions before the features
A desktop AI automation agent is only as safe as its permission model. How we think about capability grants for ORION's upcoming computer control.
Product
· 4 min read
ORION AI in October 2026: what works today
A plain account of what ORION AI can do right now, what is still in development, and how human-in-the-loop task planning works in practice.
Engineering
· 5 min read
AI work automation: where to start without losing control
Rule-based automation software and AI task planning solve different problems. Here is how to choose, and why a human should approve each step.
Engineering
· 4 min read
Autonomous computer bots: a safety checklist
Desktop AI automation agents can click and type anywhere. Four questions to ask before trusting one with real work.
Company
· 4 min read
Why we started iMpact
An independent company, one product at a time, and a standard we would rather be judged by than described with.
Engineering
· 5 min read
How ORION decides which model to use
Routing is not a model preference. It is a per-step decision about capability, latency, privacy, and cost — and it needs to be legible.
Product
· 3 min read
Permission-first design
Software that acts on your behalf should ask at the right moment, show every step, and stop the instant you say so.
We publish when something is worth reading, not on a schedule. Early-access members hear about significant changes by email first.