I build stuff that builds stuff.

— Jonny Asmar, Staff / Principal Software Engineer

Ask anything about his work. Answers land here, and the receipts open alongside.

Answers come from an agent grounded in Jonny’s actual history. It will tell you when it doesn’t know.

Case study

Agentic Development Environment

A development environment built for fleets of coding agents.

A native macOS app where terminals, agent chats, notes, browsers, and source control tile together into rooms — across every project you work on — and where the agents running inside can see each other, take assigned work, and pick it back up after a reboot.

One room of one project — a Claude Code session mid-turn, sixteen more agents on the activity rail.

Agent tools are built one session at a time. Real work is many agents, many projects, many days. atrium is built at that scale.

Why it exists

atrium started as a CLI-only tool. Agent CLIs die with the terminal that spawned them — lose the window or restart the machine, and your running sessions are gone until you dig out the right resume command.

I lost a bunch one day, I got pissed, and that's actually what prompted me to start building atrium.

Jonny, in the demo

The shape of it

Built: Solo, 2026 – present
Stack: Rust + Tauri 2, TypeScript
Agent CLIs: 10 first-class adapters
Built for: Dozens of concurrent agents
Stage: Early Access, macOS
Users: ~30 daily, free and unadvertised

Four principles

the demo's own framing

Organization

A hierarchy that survives many projects

Workspaces group projects, projects group wings of rooms, and every room is a mosaic of panes — terminals, agent chats, browsers, notes, search, git, tasks — split, stacked with sub-tabs, and resized however the work demands. Client work and side projects stay separate, each with its own rooms and its own state.

Split a pane and the launcher offers an agent session — or any other pane type.

Persistence

Close the app. Everything comes back.

Every session — CLI or chat — resumes automatically after a quit, a crash, or a reboot. Write-ahead journaling reconstructs layout, scrollback, working directories, branch context, and live agent sessions; a background daemon keeps agents working with the window closed. Everything lives on your disk, and the vault keeps git snapshots of workspace history — on an interval, and always right before an update.

After a restart: fourteen agents and a build process, ready to pick up where they left off.

Visibility

You always know what the fleet is doing

An activity sidebar sorts every agent by state — waiting on you, working, dismissed — with the last exchange inline. Message, dismiss, mark-for-later, pop out, or close any of them without leaving what you're doing; and anything an agent does anywhere animates its tab and its project icon, so no agent waits in silence.

The detailed view — density scales down to ultra-compact, and each card acts on its agent.

Control

Agents drive the environment too

The atrium CLI is the control plane, and agents speak it as fluently as people do: create tasks, launch rooms and projects, spawn or message other agents, define launch profiles and skills. Canvas and HTML notes speak the same protocol, so an agent can build you a live dashboard — or a questionnaire — that itself drives atrium. The app bends to you, too: sidebar orientation, activity density, wallpapers, icon sets.

One CLI covers every object in the app — panes, rooms, worktrees, tasks, agents, themes.

Past the pillars

Tasks that run themselves

A full kanban board where cards repeat on a schedule or loop until done — the loop that publishes his videos and triages his email lives here.

Scheduled REPEAT cards with their next run times, docked as a sub-tab beside a chat.

Any harness, any model, any effort

Launching a task card means picking the agent: Claude Code, Codex, or any installed adapter, with a launch profile down to model and effort — in an isolated git worktree if you ask.

A task card about to launch Claude Code on its own worktree.

Code review that becomes work

Inline comments in the Git pane — and annotations in the browser pane — hand off to a running agent as a generated task; the agent addresses each item and replies with a summary.

One comment on a diff, one click from becoming an agent's task.

Notes agents can inhabit. The notepad holds markdown, Excalidraw sketches, and canvas and HTML notes that agents create and patch live — users have built agent-made dashboards and questionnaires he never anticipated.

Overnight without babysitting. Hit a Claude usage limit mid-run and atrium can switch accounts automatically and nudge the agent to continue — long jobs survive the night.

Ten agent CLIs, none reimplemented. Claude Code, Codex, Cursor, Grok, Antigravity and five more run as their real vendor CLIs — in a PTY, or driven over the tool's own protocol as a native chat pane. A declarative manifest is all a new adapter takes.

62 achievements as onboarding

Every capability in the app is an achievement to earn, so the tour of what atrium can do is a game you play inside it.

All 62 earned on his own install — level 5, Architect.

A vault of workspace history

Git snapshots of the whole workspace on an interval and before every update, plus recoverable history for any closed session or pane.

337 snapshots, 906 MB on disk, cleaned up on its own.

Also in the box

Per-project memory of decisions, gotchas, and conventions
A timeline of agent turns, commits, and task transitions
Monaco, a rich Markdown editor, and a Chromium browser pane
@-mention any pane straight into an agent conversation
Omni-search over every room, task, and project
Workspace run-commands started and stopped from the sidebar
QA capture for recording what just happened

Why it belongs on a résumé

Conceived, designed, built, shipped, and supported alone — product decisions, Rust backend, React frontend, docs, release engineering, and the users who now want to pay for it. It is the clearest single piece of evidence for how he works.

Best agent UI I ever seen.

YouTube

I use atrium and I freaking love it.

Watch the demo9 minutes, narrated by Jonny getatrium.devProduct site What users sayPulled from Reddit, Discord, and YouTube