Local-first agent supervisor for builders

Run every Codex workspace from one local command center.

Asyncly keeps every agent thread tied to the repo where it belongs, turns blocked Codex output into the next executable step, and keeps approvals local before agents touch real code.

Download Mac Beta See routing demo

local registry active / 6 workspaces indexed / 24 threads imported / slack bridge ready / approvals local

Investigate duplicate Stripe subsAsyncly AI

blocked

Update Asyncly logo assetsAsyncly AI

follow-up

Restore quick-collapse carrotAsyncly AI

completed

Add Slack workspace mappingAsyncly AI

running

Identify key docsMeridianSpace

imported

Workspace routing

Workspace	Match	Action
Asyncly AI	Stripe + trial flow	active
Incite AI	billing context	reference only
MetPro	unrelated	ignore
MuseFlow	unrelated	ignore

Command input

Review the stalled Stripe trial work, identify the next step, and draft the Codex follow-up.

Next best action

Inspect webhook idempotency before polishing the billing UI.

Suggested follow-up

Open the Stripe webhook handler and trace checkout.session.completed through trial license creation.

Review checklist

Confirm duplicate event handling
Verify trial row creation
Add regression coverage

Workflow transformation

AI work is now parallel. Your workflow probably is not.

When every repo has its own agent thread, context becomes the bottleneck. Asyncly turns scattered requests and stalled sessions into routed, resumable work.

User request

"Clean up the trial flow, check Stripe subscription duplication risk, and prepare follow-ups for anything blocked."

Slack messageTrial checkout seems duplicated for one user.#support-billing / 9:42 AM

Codex threadInvestigate duplicate Stripe subsblocked / billing retry path

Terminalweb-clientpreview process still running

Backend repo~/AsynclyAIwebhook controller touched

Browser previewlocalhost:3020trial UI polish pass

Unknown stateDid webhook retry create a duplicate license?needs idempotency check

Asyncly route planAsyncly AI / billing-risk triage

Workspace context identified

Asyncly AI / ~/AsynclyAI / ports 3020, 8010

Stripe/billing thread selected

Investigate duplicate Stripe subs

Follow-up prompt generated

Trace checkout.session.completed through trial_license creation

Review checklist created

Duplicate event, retry logging, redirect refresh

Approval required before code changes

Hold webhook changes until local review

Thread remains resumable

Original Codex context retained

Guidance layer

Not just prompts. Next-step momentum.

Asyncly can summarize blocked threads, draft Codex follow-ups, generate implementation checklists, and keep every next step tied to the workspace where it belongs.

Stalled Codex thread

Investigate duplicate Stripe subsAsyncly AI / ~/AsynclyAI

Codex completed the UI pass, but billing state is still unclear.

Webhook handling may duplicate trial licenses on retry.

web-client touchedcheckout.session.completed unverifiedtest gap: duplicate event delivery

Asyncly structured action

Recommended next step

Run the Stripe sandbox event locally and verify trial_license creation before polishing the billing UI.

Codex follow-up prompt

Open the Stripe webhook controller, trace checkout.session.completed, confirm idempotency protection, and add a regression test for duplicate event delivery.

Review checklist

Duplicate event ignored
Trial license created once
Failure path logged
UI refreshes after redirect

Approval note

Hold before merge until webhook retry behavior is confirmed.

Separate project context

Every project keeps its own context.

Asyncly does not flatten your work into one giant assistant thread. Repos, aliases, ports, integrations, thread history, and safety policy stay separated by workspace.

local workspace registrycontext boundaries locked

Workspace	Repo	Threads	Ports	State	Last thread
Asyncly AI	~/AsynclyAI	6	3020, 8010	follow-up ready	trial flow + logo polish
Incite AI	~/InciteFrontendBackend	4	3000, 8080	stripe review	duplicate subscription trace
MetPro	~/metproadmin	5	3035	webhook imported	inspect webhook idempotency
MuseFlow	~/museflow-rn	3	19000	context validated	onboarding state validation
MeridianSpace	~/MeridianSpace	2	3036	docs mapped	deploy summary handoff
Aphelion Equity	~/AphelionFutures	4	5173	runtime armed	approval policy check

Thread supervision

Stay above every agent thread.

Launch, inspect, resume, and continue agent work without hunting through terminals or chat history.

WorkspaceIncite AI

Blocked

Duplicate subscription trace

Webhook retry path may create duplicate trial license rows.

4m ago / 3 files touched / follow-up ready

Original context retainedResume

WorkspaceAsyncly AI

Needs follow-up

Logo asset prompt ready

Generated updated brand asset instructions for dark and light themes.

15s ago / imported from Codex

Original context retainedOpen follow-up

WorkspaceMetPro

Running

Inspect webhook idempotency

Checking retry handling before the admin trial state is refreshed.

2m ago / webhook controller active

Original context retainedWatch

WorkspaceMuseFlow

Imported

Onboarding state validated

Thread imported with app state, branch name, and simulator notes intact.

11m ago / context retained

Original context retainedResume

WorkspaceMeridianSpace

Completed

Deploy summary available

Static deploy notes and DNS checks are attached to the workspace timeline.

23m ago / final answer captured

Original context retainedReview

WorkspaceAphelion

Waiting for approval

Billing path touched

Risky payment-path edits are staged behind a local approval checkpoint.

31m ago / approval required

Original context retainedApprove

Routed workflow demo

From idea to routed work.

A complex request becomes workspace-specific tasks, prepared threads, approval gates, and concrete next steps.

Input

"Clean up trial flow and check Stripe subscription duplication risk."

Parse request

Scope detected: website, desktop app, backend.

Split work

One command becomes repo-specific routes.

Website copy -> Asyncly site
Billing risk -> Backend webhook
Trial UX -> Desktop app

Prepare Codex follow-ups

Generate repo-specific instructions with existing context.

Gate risky changes

Hold billing and webhook changes for local approval.

Resume threads

Each workspace keeps original context and next action.

Local trust boundary

Local-first by default. Connected only when you choose.

Your repos, provider settings, credentials, logs, and workspace registry stay on your machine unless you explicitly connect an integration.

Inside your MacReposWorkspace registryProvider settingsCredentialsThread stateLogsApproval policy

Optional connectionsSlack mappingLicensingUpdatesHosted relay when explicitly enabled

Codex power users

Built for builders with too many active threads to babysit.

If your day spans multiple repos, clients, Codex sessions, Slack threads, and half-finished follow-ups, Asyncly gives that work an operating layer.

I have six repos and three agents running.

I need to resume yesterday's Codex thread.

I want Slack issues routed to the correct repo.

I want faster loops without losing approval control.

I need a status view across every project.

Start local, expand when ready

Start with your local workspaces. Add agents, Slack, and follow-ups when you are ready.

Download Mac Beta Read setup docs