Skip to content
Blink

Blink once. See everything.

Orchestrate your agent fleet. Turn ambitious ideas into shipped projects, in days.

Project management for coding agents. Plan a milestone once, hand the whole thing over, and get it back shipped.

npm install -g @weloin/blink
Read the docs

The problem

An ambitious project does not fit in one session.

Context windows end. Sessions reset. Agents multiply. The plan lives in scrollback nobody re-reads, and last week's architecture call went with the transcript it was made in.

Decisions get re-argued

The reasoning was in someone else's session. Nobody can produce it, so the team settles it again, differently.

Work happens twice

Two agents, two sessions, one task. Nothing outside a transcript remembered it was already assigned.

Nobody can answer what is blocked

Not without interrupting three people and reading eighty markdown files.

The shape of a project

Plan it once. Hand over the milestone.

  1. Say what you want, out loud

    You describe the ambition. Your agent asks what it actually needs to know, one question at a time, and writes nothing until the plan on screen is the plan you meant.

  2. Settle how it should look

    The design language gets decided before the building starts. You look at a prototype, not a description, and you keep looking until it is right.

  3. Hand over the whole milestone

    Not a task at a time. Blink sizes the work, takes your sign-off once, then runs it and lands it. Stop it halfway and it resumes from where it stopped.

  4. Never start from zero again

    The second milestone begins with everything the first one learned. Every choice already made, already explained, already on disk.

Where your day goes

You are the bottleneck

You are in every loop. Explaining the project on Monday, explaining it again on Wednesday, dispatching one task at a time and reviewing each one before the next can start. The work moves at the speed of you being available.

You are in it twice

Once to agree the plan, once to sign off the run. Between those two moments the milestone moves without you, and it does not need you to remember anything.

Ambition stops being a context problem.

The skills

You are not filling in a form. You are talking to your agent.

blink init puts these in your repo. There is no board to maintain.

/blink:project
“plan this project”
Surveys the codebase, derives milestones, asks up to ten questions one at a time, and writes the plan on your confirmation.
/blink:tracking
always on
The contract every agent follows: create the task before the work, in_progress when starting, done when it ships, a decision file when a real choice is made.
/blink:sync
“did we forget to close anything”
Compares the tracker against git history and reports where they disagree. Repairs only what you confirm, one at a time.
/blink:setup
“adopt this repo”
Surveys tracking you already have, whether that is TODOs, ADRs or a PLAN.md, and converts it after asking once.
/blink:pause and /blink:resume
“park the auth work”
Puts work on hold with a recorded reason, and brings it back without losing the thread.
/blink:design
“how should this look”
Interviews for design context once, then iterates on a prototype served locally.

The dashboard

Every project you have, on one screen.

Pending, doing, blocked and open risks, totalled across all of them, above a card per project showing what needs attention and what is in flight right now. A project that has gone quiet is visible as quiet. One that is blocked says so without being opened.

127.0.0.1:7777
3 projects
52% · 41/79 tasks done
31
Pending
7
Doing
3
Blocked
5
Open risks
papayments-apiactive
m-04 settlement64% · 18/28
8
Pending
3
Doing
0
Blocked
1
Risks
  • Idempotency keys on capturet-0c14ma
  • Reconcile partial refundst-0c14mb
  • Backfill the ledger exportt-0c11xk

12 min ago

Read-only by design. Nothing in the browser can edit a file: your repo is written by your agents and by you, never by a web page you left open.

Decisions are first-class

Six weeks later, why is still there.

A real choice becomes a file, sitting next to the code it explains. Reviewable in a pull request, readable by a teammate who has never installed Blink.

.blink/decisions/d-014-token-rotation.md
---
id: d-014
title: Rotate refresh tokens on use
status: accepted
date: 2026-07-02
---

## Context
Long-lived refresh tokens survive a leaked backup.

## Decision
Rotate on every use. The old token is good for 30
more seconds, so a racing retry still succeeds.

The next session starts where the last one stopped.

So does the next agent, and the next teammate.

npm install -g @weloin/blink

Ships as a native binary, so nothing needs a Node runtime to run it.