Recurring failures
Capability Balance Sheet
Evidence-backed Skill, Execution, Memory, and Quality positions at one statement date.
Kernel awareness
AwarenessWhat Workweaver has learned to do well
Objectives and key results.
Workspace objectives, key-result progress, and generated draft OKRs — inside Mission Goals.
We keep notes you can delete. When Workweaver joins, observations appear here — video stays in the meeting service.
Looks stay off until a share or camera is on. No tape is kept here.
We keep notes you can delete. Everyone in the room agrees before it speaks.
Never a silent skip. If seats are full, the calendar says so.
Two rooms. Workweaver is the colleague.
Old links to /voice land here. Add ?to=phone or ?to=meetings to skip the door.
Inbound, outbound, and meetings each pick a ladder. Empty uses the founder default. Missing provider keys do not block this page. This is not a live call.
This call can use a catalog voice. Standing routes stay as they are.
Every human affordance has a machine affordance
This page is for developers and connected agents.
/home?alt=hour&hour=<now>Hour zoomminute ruler for one hour/home?card=<id>Cardsame as the drawer on Home/home?filter=judgment:pendingNeeds youthe retired Inbox, as a filter/skills?skill=<id>#checksSkill · disclosurehash opens one disclosure/memory/?vault=team&q=<q>Memory search in this vault/members?member=<id>#departureMember · departure plan/settings#models · #wallet · #supportSettings entriesevery canonical tab is addressable/voice?call=<id> · /meetings?card=<id>Call · meeting/<workspace>/homeNamed workspace URLsadditive · #13193Rule: if a human can open it, the URL alone reproduces it — after refresh, on another device, or pasted to an agent. Availability rules may hide an entry; direct routes still resolve.
Their time is recorded on Home as dashed cards; what was asked is fingerprinted, never stored as prompt text. wall-clock timesheet partial · fingerprinted sessions live
The agent card what any agent learns in one call
GET /.well-known/agent-card.json The agent card loads from this workspace after sign-in.
ww on your machines state, sync, alerts
Three commands, then ww doctor. The in-product guide carries the sheet your IT team asks for.
ww edge devices register on your laptop to join it to this workspace.Alerts from the edge — surfaced here and as Needs-you cards when they need a decision:
$ ww status No live status until a machine is registered. Run ww doctor on a laptop that has joined this workspace.
POST /mcpOne door for every harnessyour pass is the bearer credentialww acp card --json · ww acp tools --jsonFrom the terminalsame card, same verbsww.memory.recall · ww.goals.create · ww.skills.run · ww.context.wakeAgent toolsthe same catalog the screens readRecommended first call for any agent that resumes work: ww.context.wake — objective, decisions, open loops, blockers, budget, and a resume action, reconstructed from the ledger and bounded.
Install in one line
ww connect claude-codeww connect codexww connect cursorww connect --print-configEdge jobs cloud → your laptop
Workweaver dispatches coding jobs to a registered device; the device claims the job, runs it in an approved isolation backend, and reports back onto the Home card. No approved backend means the job fails closed — it never falls back to your bare host.
Screens, ww, and agents all show the same status.
The screens, ww and agent tools — and the API — read one source; none of them invents a status the others cannot see. A greyed-out named substitute beats a button that raises. ww doctor says exactly which capability is degraded and why.
Who works here — humans, one Workweaver, and the agents you let in
People, one Workweaver, and the agents you let in.
Every dial in one place.
Workspace, models, identity, trust, notifications, wallet, support, data, agents, experiments — in plain language.