Asyncly

One command center.
All your agent work.

Direct Codex and Claude work, follow several tasks at once, and review the results in one local-first desktop app.

For founders, engineers and consultants working across Projects.

The actual Asyncly Command dock and its message controls
Scroll down to see every problem we solve

Build at scale

Parallel work, orchestrated with minimal overhead.

Each coding task works in its own managed worktree: a separate copy of the code. It runs its own dev server, validates its own change, and can carry the pull request through review.

When it’s ready, it waits for you. Add one change to the project while another task keeps working, and Asyncly surfaces any conflict before the integration can finish.

Working separatelyEach thread’s changes stay isolated while it runs.
Ready to addValidated work waits for your call, not the other way around.
Added to projectThe reviewed change joins your project; other tasks keep their place.
Real thread #1 in Asyncly: Ready to add, in storefront, with its finished answer and three changed files
The Ready to add menu on thread #1: storefront, 3 commits ahead of main, 0 uncommitted files, Add to project and Close worktree
Worktree details on thread #1: branch asyncly/task/pricing-tiers, add to main, its own folder, update from main, Checks passed
Thread #1 carrying pull request #482: Open, Checks passed, Review pending, with Convert to draft
Thread #1 after its change was added: the Ready to add badge has cleared

Real Asyncly thread states with fictional work. The camera move is part of this website, which does not merge code.

Always know what’s moving

Every running task, one glance away.

The top bar counts what’s waiting on you, what’s working and what finished while you were elsewhere, across every Project. Open a count to see each thread with its model and how long it has run, then pick one to go straight to it.

Asyncly All Workspaces with the top bar’s 8 working list open: Manager #13 and seven threads across Lumen Commerce, Harbor Press, Beacon Platform and Atlas Mobile, each with its model, effort and run time
The 4 awaiting list: Manager #13 asks “Ship Apple Pay with the pricing launch, or hold it a week?”, with #11 in Lumen Commerce, #2 in Harbor Press and #3 in Beacon Platform waiting on you
The 4 unread list: finished results not opened yet, from Beacon Platform, Lumen Commerce and Atlas Mobile, with when each finished
Claude usage for the connected account: 64% of the 5-hour window and 58% of the weekly limit left, with when each resets

Real Asyncly top bar with fictional work. The last step is a real-time screen recording of the product.

Your attention, on a need-to-know basis.

Running work stays in the background. Only the decisions that need you come forward, into a free position, while what you’re already reading stays put.

Guided product demonstration
Lumen Commerce in Attention: working threads behind occupied foreground positions
Lumen Commerce Attention
Work is moving.Pricing, Apple Pay and funnel events are progressing in Lumen Commerce.

Real Asyncly decision controls, with fictional work. The camera close-up is part of this website. No agents run when you try it.

Find your most effective layout.

Four ways to see the same Project. Oversee it all, settle into one thread, let the questions come to you, or lay the work out on a board.

Real Asyncly views with fictional work. Transitions between them are authored for this website.

Work Boards

The whole launch on one board.

A Work Board is a canvas for a Project. Put thread cards beside the notes, checklists, tables and charts they depend on, group them into frames and connect them with arrows. The threads keep working while they sit on the board.

The Spring launch Work Board in full screen: Pricing launch, Checkout reliability, Design system and Launch metrics frames with thread cards, notes, a live table and charts
The Pricing launch frame up close: a Decision note connected to #1 Rebuild the pricing page, Ready to add, a Launch checklist, and #2, #3 and Manager #13 working
The Launch metrics frame: the Checkout health by week table with linked charts for p95 checkout latency, checkout conversion and orders, and a Weekly p95 arrow from thread #4
A thread card opened at full size over the dimmed Work Board

A real Asyncly Work Board with fictional work and data. The last step is a real-time screen recording of the product.

Thread types

The right kind of thread for the work.

Pick a mode when you start a thread. A Task changes things, a Discussion thinks it through with you, and a Manager watches other threads and coordinates what comes next. Default runs the provider as it is.

  • Task thread #1 Rebuild the pricing page for the new tiers, Ready to add in storefront

    Task

    Works on it and makes changes

    #1 rebuilt the pricing page in its own worktree and is ready to add.

  • Discussion thread #7 Explore three hero directions for the spring campaign, with three directions ready to compare

    Discussion

    Talks it through, no changes

    #7 explored three hero directions and is waiting for you to pick one.

  • Manager thread #13 Keep the pricing launch on track, watching #1, #2 and #3

    Manager

    Watches work and coordinates follow-ups

    #13 keeps the pricing launch on track across #1, #2 and #3, and brings you the calls that are yours.

A new Lumen Commerce thread with its Mode menu open: Task, works on it and makes changes; Discussion, talks it through, no changes; Manager, watches work and coordinates follow-ups; Default, uses the provider as-is
The model picker on Claude: Smart, Opus 5.5 at XHigh effort with Fast, Sonnet 5.5, Haiku 5.5 and Fable 5.1
More options: Helpers, Independent review, When finished (Review, Add to project, Open PR), Worktree (Auto worktree or Root checkout), Mode and Answer length

Real Asyncly thread cards and menus with fictional work. The Manager step is a real-time screen recording of the product.

A Manager keeps the work moving.

Give it an objective. It follows the threads, starts follow-ups, and brings you the decisions that are yours.

Manager #13, Keep the pricing launch on track, watching #1 pricing page, #2 funnel events and #3 Apple Pay. Its header shows Website, 2 running and 3 threads.
The Manager’s own thread holds the brief, progress and work it is watching.

Real Asyncly captures with fictional work. These show separate moments in the product.

Building with Jev

In development

In our internal workflow, Jev, TypeSafe’s decision model, checks whether follow-up work still belongs in the same context. We’re building toward a wider role in keeping agent work organized.

About Jev at TypeSafe

Where we’re taking it

Classification
Recognize the kind of work so each request gets the right treatment.
Internal tags
Match work to consistent tags, making related threads easier to find.
Context mapping
Connect a request to the relevant context already in your Project.
Worktree assignment
Spot when the Source or checkout needs another look, respecting your choices and permissions.

Everything has a place

Every project in one platform.

A Workspace contains Projects. A Project holds related work and its threads. Sources are the repositories, folders or other material a Project uses. A thread can use zero, one or several Sources.

A thread can use no Source, one, or several. The pricing work reaches storefront and design-system while staying in Lumen Commerce, and the other businesses stay in view.

running completed needs you
Personal Workspace
Atlas MobileLumen CommerceBeacon PlatformHarbor Press

Project threads

#1 Pricing page#2 Funnel events

Project Sources

storefrontdesign-system

#1 uses both Sources. It still belongs to Lumen Commerce.

Asyncly All Workspaces: Lumen Commerce, Atlas Mobile, Beacon Platform and Harbor Press side by side, each listing its running and completed threads

All Workspaces · four Projects · real capture

Show it instead of typing it

Record it. Say what’s wrong. Hand it over.

Some problems are faster to show. Start a capture, use the site or app that’s misbehaving, and talk through what you see. Asyncly turns the recording into evidence an agent can work from.

lumencommerce.example/pricingAsyncly’s REC indicator
Asyncly’s Stop capture control, six seconds into a recording
When I switch to Monthly, the Growth card jumps. Keep the cards still in both billing periods.
Asyncly Review Capture: the recorded pricing page beside its captured context (clicks on Monthly and Annual, a selected price and pricing.module.css), sent to #1 Rebuild the pricing page for the new tiers with Opus 5.5 XHigh, ready to submit
Thread #1’s composer holding the recording, its context file and the request to review the capture and carry out the recorded request
Thread #1’s answer: at 0:02 the Growth card drops 14 pixels in Monthly, fixed in pricing.module.css and validated at both widths

Real Asyncly capture screens with a fictional storefront. The video is a real screen recording of a demo page; the spoken line is shown as a caption, and no agent runs on this website.

Work with people too

Share the thread, not a screenshot.

When a decision needs someone else, send them the work itself. They see what the agent did, answer in the same place, and you carry on.

Asyncly Start conversation: a teammate’s address, a question about thread #1, the Thread context choice and a preview of the shared context with 1 turn and 3 files
An Asyncly Team conversation in progress: the question, the shared pricing thread with Clone, a teammate’s replies and the thread’s transcript alongside
The same Team conversation marked Resolved, with You resolved this conversation and an Undo control
The Team conversations list: one in progress with Mia Contreras and one resolved with Jonas Reidel

Real Asyncly Team screens with fictional people and work. Team is in private preview.

More of your work.
Less to hold in your head.

From a first question to an ongoing responsibility, give each kind of work the support it needs.

The Checkout reliability System in Lumen Commerce: its working memory with a baseline, a finding, a false positive, a lesson and a next check, above its required quality checks
The Library’s Skills tab for Harbor Press: Project skills house-voice and fact-check-pass, each available and invoked by name in a task
The Automation workstation across all Projects: Weekly subscriber newsletter, Nightly error budget report, Monday crash triage, Release notes draft, the Checkout reliability automations and the Checkout reliability System
Studio comparing two spring campaign hero directions for Lumen Commerce, Conversation first and Editorial split, with the third direction, A bigger canvas, in the direction bar
Stats for the last 30 days: share of tokens by model across Codex and Claude, and the rhythm of work by day and hour

Real Asyncly screens with fictional work. The Studio designs are fictional pages made for this demonstration.

The next thing starts with you

What will you speak into existence?

14-day trialLocal-firstCodex and Claude

Asyncly is local-first. The desktop hosts work and local context; selected AI providers receive task context, while hosted account and enabled sharing services handle their own data.