How it fits the family
Same four jobs as every other space.
Your AI does the reasoning and the outside work. Code keeps the durable record and ships the loops for its kind of work. You decide who and which AI can read or change any of it.
All spaces
In the works · not open yet
Assist With Code
Assist you and your AI with what you're building — the plan, the decisions, and the threads the next session picks up.
Every coding session starts by rebuilding context the last one already had. Assist With Code will keep the plan, the decisions and the open threads so the next session — with you or with your AI — starts where the last one stopped.
assist with the planassist with decisionsassist with the next sessionassist with what's still open
No sign-up, no waitlist, nothing to click yet — this page exists so you can see where it’s going. The thirteen open spaces are here →
What it will be good at
Written down now so the product has something to be held to later.
01
The plan, not just the diff
What you're building, what you decided and why — the part that lives in your head and dies with the chat window.
02
Threads the next session picks up
The half-finished refactor, the thing you noticed but didn't fix, the question you parked — waiting and still legible.
03
Context your AI can start from
So a new session opens with the decisions already made instead of relitigating them.
Research loops
Good ideas your AI will be able to borrow.
Short playbooks for a kind of coding work — the right questions, in a sensible order. Written now, so the space opens with them rather than bolting them on later.
Pick up where you left off
4 steps- read the last decision before the last commit
- confirm the branch and what's half done
- restate the goal in one sentence
- record the next step before you start
Plan a change worth making
5 steps- state the problem, not the solution
- list what it touches
- name the approach and what you rejected
- decide what would prove it works
- record the plan before you write anything
Debug something properly
5 steps- reproduce it reliably before you theorise
- narrow to the smallest failing case
- check what changed most recently
- fix the cause, not the symptom
- record the cause so it's findable next time
Review your own work
4 steps- read the diff as if someone else wrote it
- check the edge case you avoided
- confirm a test would catch the regression
- record what you deliberately left out
Write a decision down
4 steps- state what was decided
- name the alternatives and why they lost
- record what would make you revisit it
- date it
Where it is today
Still being built.
No account and no date we're promising yet. The day it opens it appears in the family list with a live label and a real link, exactly like every other space.