One shared understanding.
People use the workspace. Coding agents connect through MCP (Model Context Protocol) with scoped credentials. They can work from shared project knowledge within the access granted to that credential.
CONTEXT THAT CARRIES FORWARD
Pick up where
you left off.
A private workspace for project knowledge that you and your coding agents can read and update. Keep decisions and handoffs, assemble context for a task, and carry what you learn into the next session. A recipe selects project sources and adds instructions for using them.
See how it worksFor people and the agents they work with. About access
AN EXAMPLE: FINISH AN API CHANGE
01 SELECTED PROJECT SOURCES
Project briefrevision 4
Accepted decisionsrevision 7
Handoffrevision 2
02 INSPECT THE ASSEMBLY
Finish API retry behavior
Sources and revisions, ready to review.
03 WORK IN YOUR CODING TOOL
Complete the retry change with the assembled context.
04 SAVE THE RESULT AND HANDOFF
Saved: API retry fix · Next: verify on mobile
A little continuity.
A better place to begin.
- Project knowledge
- Task-specific context
- Human + agent contributions
01 / HOW IT WORKS
Less catching up.
More carrying forward.
Keep useful project knowledge, gather the sources for a task, and leave a clear handoff for the next person or agent.
-
Keep the knowledge.
Capture the brief, the decisions, the working practices, and the handoff. Keep shared knowledge in one place, connected to the projects that use it.
A home for the what, why, and what’s next. -
Bring the right context.
A recipe selects project sources and adds instructions for using them. Inspect the included sources and revisions, then work with that context in your preferred coding tool.
Explicit sources. An inspectable starting point. -
Leave the next session a head start.
Save what changed, what you learned, and what remains open. People and agents can update project knowledge; authorship and revision history stay visible.
The work ends. The useful parts stay.
Record concerns and discuss possible responses. Explicitly accept a chosen direction for future work; draft ideas stay outside ordinary project context.
02 / THE APPROACH
Your knowledge.
Your way of working.
Built around the project, with room for the people and tools that move it forward.
Context you can inspect.
Inspect the recipe’s selected sources and instructions. You and your agent decide what to do with that context.
Room to revise.
Knowledge changes as the project does. Keep its history, see who contributed, and return to an earlier revision when needed.
Work in your own tools.
Connect Codex, Claude Code, or Cursor. Build223 holds the context; the work happens in the tools you choose.
03 / CURRENTLY PRIVATE
A public introduction.
A private workspace.
Build223 is currently for approved accounts. Public registration is not open. Published by rydee.com; support: ryan@rydee.com.
Sign inConnector downloads and setup details
A
considered place for work in progress.
What belongs in Build223?
Project briefs, guides, decisions, practices, and handoffs—the knowledge that helps you understand the work and take the next step. Code stays in your repository.
Does Build223 run my agents?
No. Build223 stores knowledge and instructions for assembling context. Agents use their own tools and permissions to do the work and contribute what they learn.
How do people and agents connect?
Approved people sign in to the workspace with GitHub. Coding agents connect through MCP using scoped credentials issued from the workspace.