IKARUSpersonal ai os
Notes from the workshop.
IKARUS is built in public. Progress, design decisions and honest dead ends, posted as they happen, not as a highlight reel.
Two audits in one week
A full-codebase audit and a network egress audit. What they found, what got fixed, and why audits are a feature.
This site, same instrument
The marketing site was rebuilt in the app's own design language, with the same privacy posture.
IKARUS starts noticing
Adaptive Intelligence ships: pattern detection over real usage, with concrete thresholds and no silent automation.
Do it once, keep it
The Automation Recorder: record a task done with IKARUS, review it as a draft workflow, save it or don't.
The instrument gets its face
The Atelier design language ships across the entire app, and the codebase got smaller doing it.
Workflows: typed steps, one engine
The Workflow System ships: ordered typed steps, a full editor, and exactly one execution path.
Trust you can audit
The Trust Center ships: one gate for every tool call, four permission levels, a real emergency stop.
A vault of its own
The Knowledge Vault ships: notes, real files, collections, and a graph, all in local storage.
Hands on a real browser
Browser Attach closes its first phase: multi-tab control, always attended, verified live in five passes.
Why I'm building IKARUS
The busywork problem, the bet behind IKARUS, and why the whole thing is being built in public.
