your ai writes it. but does it know it?

download for free

self improving coding

stay in your app

claude code
codex
cursor
gemini cli
github copilot
windsurf
cline
kiro
roo code
opencode
amp
goose
junie
kilo code

stay in your app, tell your agent “use wayari”, and let coding become magical

standing.md

a persistent thread. from any app

claude code, codex or any app that speaks mcp can tell you. say "never touch main" once and every agent hears it.

wayari thread4 apps reading

threadacme/web

pr #1204 ready for you
finding: zero seats unhandled
gate green: typecheck, tests
gate red: tests
note: seats live in billing/
#team-billing opened
pr #1204 ready for you
finding: zero seats unhandled
gate green: typecheck, tests
gate red: tests
note: seats live in billing/
#team-billing opened

standing order: never touch mainstanding.md

wayari mcp serves it to any app

claude codewayari_threadcliuse wayari, what shipped last night?reads what shipped

codexwayari_statusappuse wayari and pick up team billingreads what is shipping

claudewayari_statusappuse wayari, anything waiting on me?reads what waits on you

cursorwayari_standingappuse wayari before you touch this reporeads the standing orders

acme/webwayari mcpask wayari

prompt.txt

you ask. wayari listens.

say "use wayari" in whatever app is already open, then ask for the thing. the crew fills in the rest.

use wayari, from anywherelistening

claude codeacme/web

use wayari, add team billing with seat limits

wayari_start

opened #team-billing and staffed it.

use wayari, add team billing with seat limitsask for the next one

acme/webjust now

plan.md

a swarm maps the plan

the crew reads your repo first, and leaves you a note on anything the code can't answer, like whether to prorate mid-cycle.

team billing1 note for you

read by 3 scoutsabout a day left

#schema

a team of focused builders

one builder takes the schema, another the api, and nobody trips over anybody.

build2 building

#schema · #api · #settings12m

taste.md

it designs to your taste

it looks at its own work on a laptop and a phone before it says done, and a critic that didn't make it checks it against your taste.

wayari look2 screens

wayari.com.wayari/taste.md

roles

every agent gets a role

yari splits the job and hands each agent one thing to do. a reviewer can't edit, and a builder can't approve.

#team-billing6 roles

6 agents3 read only

review-notes

a specialised review swarm

reviewers go through every line and catch things like an 11th seat on a 10-seat plan. the builder doesn't get a vote.

#479 review3 reviewers

meter-rates3 reviewers on #479reviewingmerge#479 passed reviewmerge

correctnessthe limit comes from the plan nowreadingok

edge casesat 10 of 10 seats, an 11th gets inreading1 findingfixed

tests142 unit tests, and seats.spec in e2ereadingcovered

billing/seats.ts+2−1#479

40export function addSeat(org, plan) {

− const max = Infinity

41+ const max = plan.seats

42+ if (org.used > max) return block() if (org.used >= max) return block()

43 org.used += 1

44 return save(org)

45}

11th seat on a 10-seat plan · seats.ts line 42edge cases: at 10 of 10 seats, used > max still lets one more in.the builder made it used >= max. e2e now adds an 11th seat and expects a no.send back to builderfixed by the builder

typecheckunit 142/142e2elintrepo checksbuilderwrote this difffixed line 42can't sign its own work42

billing/seats.ts5 gates

gates

it runs self improving loops

it runs your tests, then opens the app and clicks around like you would. anything red goes back to the builder, error and all.

auth-redirectlooping

auth-redirectrunning the checkse2e failede2e failed twicea reviewer is lookinggreen, in reviewsee why

typecheckunit 38/38e2eopened the appsign-in.spec: expected /dashboard, got /loginsign-in.spec: lands on /dashboard

builder is stuck on auth-redirecte2e failed twice. a reviewer can look before it tries again.send a reviewerreviewer sent

typecheck · unit · e2eopens the app

pr-1204.diff

a merge, on your word

you get one pull request with the review attached, to read over coffee. nothing merges until you say so.

#479 meter-ratesone pull request

3 reviewsgates green

everything is recorded on the graph.

every run writes down what it learned, like where seats live, or which test broke on tuesday and what fixed it.

how acme/web works

wayari's map of the repo, filled in one run at a time.

run1notes01

app/

billing/

tests/

db/

page.tsxseats.tsxseats.ts101seats live in billing/, not settings/plans.ts202seat types come from here. never anyprorate.tsnew303prorate mid-cycle, never at renewalseats.test.tsschema.prismapr #214merged

01seats.ts seats live in billing/, not settings/
02plans.ts seat types come from here. never any
03prorate.ts prorate mid-cycle, never at renewal

start working before paying.

one week free.

monthlyyearlysave 58%

first-week.plan

first week

give it a real job.

a week free, no card, no signup

then $49 a month, if you keep it

start free

the whole crew, on your own repo
use it from claude code, codex or any mcp app

after the first week

wayari.plan

wayari

for when you'd miss it.

stop after any month

the crew, on call every night
keeps everything it learned about your repo

< bring your own agent >

the crew runs on the claude code or codex plan you already pay for, so you never pay twice for the same tokens.

will it run up my bill?

if your post about wayari gets 10,000 views, the year's on us.

any platform counts. send us the link and we'll send you a key for the annual plan.

send us the postjawad@wayari.com

your questions, answered.

questions.md68 answered

on your machine, each agent in its own worktree and branch. their branches merge into one channel branch, and the pull request runs from there to main.

typecheck, build and tests, plus any check your repo adds. their exit codes decide, and a check that can't run counts as a fail.

an agent claims a file before it edits it. a second agent asking for that file is refused with the holder's name, and a crashed agent's claims are freed.