Code
IMPLEMENTATION
Jules
Add the theme preference and dark palette. Preserve the existing screens, navigation, and acceptance checks.
A LITTLE BACKUP FOR YOUR NEXT BIG THING
You’ve got the idea.
Let’s build it.
An AI development studio for the feature, fix, or side project on your mind. Your Codex account. A crew to work with. Code you can look over.
Get a heads-up when the first invites go out. No payment today.
The living studio · recorded office activityRECORDED IN CODEFLOOR · DEMO ACTIVITY
Six specialists. In your corner.A little help with the work ahead.
YOU KNOW THE ONE
That project in your tabs?
Let’s get it moving.
You know what you want to make. CodeFloor gives you somewhere to work it out, a crew to help with the code, and a clear look at what came back. Start with one thing.
Let me know when it’s readyTAKE A LOOK FOR YOURSELF
Don’t just watch it.
Try what we built.
A quick introduction, then one real feature from request to result. Look through the handoff or go straight to the working sample. No signup needed.
Northstar / A theme that remembers 8 / 8 checks · independently reviewed
YOUR TURN TO LOOK AROUND
Pick a stage. Go at your own pace.
THE REQUEST
Make one choice.
Let the app remember.
“Add a persistent dark-mode preference. Keep both screens and the navigation working. Follow the system theme until I choose.”
The change stays in theme.js and styles.css. Eight checks tell us whether it works.
- Remember an explicit preference
- Preserve both screens and navigation
- Keep keyboard controls working
BEFORE / LIGHT ONLY
AFTER / YOUR CHOICE, REMEMBERED
02 / THE CREW’S APPROACH
Two roles.
One focused change.
This mission used Jules for implementation and Remy for independent review. Other missions can use different roles; the full roster stays available.
INDEPENDENT REVIEW
Remy
Review the candidate revision and rerun the eight browser scenarios before accepting the change.
- 01Keep the scope bounded.
Two allowed files. The sample’s screens and test contract stay intact.
- 02Make the change inspectable.
Retain the actual file changes and executable verification results.
- 03Keep integration deliberate.
Independent review accepted the revision. Manual approval then applied it to the sample.
03 / THE HANDOFF
A result backed
by evidence.
8 of 8 browser scenarios passed, up from 2 of 8 before the change. Independent review accepted the same revision, then manual approval applied it to the sample project.
- Changed files
- 2 theme.js + styles.css
- Browser scenarios
- 8 / 8 passed after the change
- Independent review
- Accepted by Remy, before integration
Inspect the change and recorded checks
Reviewed revision 0092a6637e797e88577ec360fd5306602373364b
Two changed files: theme.js and styles.css. The acceptance contract and existing screens stayed unchanged during this run.
Observed checks · npm test ran the fixed eight-scenario browser contract. All eight passed in broker verification, independent review, and a separate rerun after integration.
- Default follows dark system preference · passed
- Default follows light system preference · passed
- Toggle works on Overview and Activity · passed
- Explicit preference survives reload and navigation · passed
- System changes apply before an explicit choice · passed
- Explicit choice wins over later system changes · passed
- Keyboard Enter and Space operate the toggle · passed
- Changing theme preserves layout and navigation · passed
Excerpt from the actual theme change
+(() => {
+ const key = 'northstar-theme';
+ const system = window.matchMedia('(prefers-color-scheme: dark)');
+ const button = document.querySelector('#theme-toggle');
+ let preference = null;
+
+ try {
+ const saved = localStorage.getItem(key);
+ if (saved === 'dark' || saved === 'light') preference = saved;
+ } catch {
+ // Keep the toggle usable when browser storage is unavailable.
+ }
+
+ function render() {
+ const dark = preference === null ? system.matches : preference === 'dark';
+ document.documentElement.dataset.theme = dark ? 'dark' : 'light';
+ button.setAttribute('aria-pressed', String(dark));
+ }
+
+ button.addEventListener('click', () => {The theme change also adds a dark palette in the existing CSS variables. Review: accepted by Remy. Integration: manually approved and applied. An earlier attempt was held when Edge could not launch in the command sandbox. The sample runner was configured to use installed Chrome before this fresh run; the eight behavioral scenarios and assertions were preserved.
04 / TRY THE RESULT
Don’t just watch it.
Put it to work.
Switch the theme. Visit Activity. Reload the sample. The preference stays with you.
The original sample · the theme preference is missing.
Sample project · presentation adapted for this demo. The reviewed theme and application code are unchanged.
Jules ImplementationRemy Review01 / 04
Read the film transcripts and mission context
Meet your new crew / 20 seconds. For the feature, fix, or side project you keep thinking about. Six specialists. In your corner. The opening shows agents walking around the installed CodeFloor app.
00:04 — Start with something small. Remember my dark mode. One useful fix. Two files. Clear checks. Use the project you already have.
00:08 — Talk it through. Give it a go. A plan. Some code. A fresh pair of eyes. All in one place, so you can follow along. Work out the next step. Watch it come together. Look it over. Make the final call.
00:13 — Go on. Try it out. The actual Northstar sample shows the finished feature in use.
00:15 — You’ve got the idea. Let’s build it. A little help with the work ahead. Join early access at codefloor.app.
This introduction uses recorded app activity and the retained Northstar mission, with original music and no speech. The office footage shows the experience; the mission evidence shows the actual work. It’s one small example. Your project will have its own scope and checks.
The portrait version follows the same story: Meet your new crew. Start with something small. Talk it through. Give it a go. Go on. Try it out. You’ve got the idea. Let’s build it. Bring that idea of yours.
Follow a real mission / 50 seconds. Take a closer look at the change and its evidence below.
00:00 — Pick your theme. Yep. It remembers. A real Northstar change, built and independently reviewed in CodeFloor.
00:04 — Small change. Pretty satisfying. One small thing, done properly. Two files. Eight of eight scenarios. Reviewed.
00:08 — Here’s what we asked for. Remember my theme. Switch screens. Reload. Still there. The original desktop brief is shown beside the summary. A clear ask. Two files. A feature you can try.
00:13 — Jules builds it. Remy takes a look. Jules makes the theme stick while keeping the app working. Remy reviews the same change and reruns all eight checks. One builds. Another checks. The office behind the role cards is illustrative recorded app footage.
00:18 — The actual code. Remember what you picked. Use your system theme until you choose. Come back. It’s still your theme. The film shows the real reviewed theme.js.
00:25 — Here’s how it held up. Eight browser scenarios passed, up from two before the change. The retained evidence shows accepted independent review and manual approval of that same revision. A separate rerun passed after it was applied.
00:33 — Pick a theme. Make it yours. Switch screens. It sticks. Hit refresh. Still there. You can see the whole sample, with a separate close-up of the actual control.
00:45 — Your next idea. Let’s build it. Have a go. Then bring something of your own. Join early access at codefloor.app.
The film uses the real sample and retained mission evidence, with original instrumental music and no speech. This is one verified mission. Other projects have their own scope, setup, and outcomes.
Now think about your next project.
One thing you want to build. A crew to help you get started.
SOUND FAMILIAR?
Lots to build.
Only so many hours.
If you build on Windows, use Codex, and like knowing what’s going into your code, this is for you. Here’s where CodeFloor can fit.
Solo developers
You’ve got the ideas. And the bugs. And a day job. Hand the crew one clear task, then come back to code and checks you can review.
Still your project. Just less on your plate.Founders who build
You want to see if the idea has legs. Start with one useful feature, work through it with the crew, and decide what’s worth building next.
Get something real in front of you.Small teams
There’s always one more ticket. Give a well-defined task to the crew and keep the plan, code, checks, and review in the same place.
Something the rest of the team can follow.Explore example briefs
EXPLORE AN EXAMPLE BRIEF
“Add a beautiful dark mode to my app. Match the existing design, remember the preference, and check that the key screens still work.”
Architecture · Frontend · QA · Review
ASK FOR A CLEAR HANDOFF
- A scoped implementation plan
- Changes in a private workspace
- Verification and review evidence
CHECKS, REVIEW, AND YOUR APPROVAL
Tell the crew what’s next.
You still call the shots.
Start with Manual review. You can look through the code, checks, and review before approving the change for your project.
- 01
Pick one thing.
Choose your project. Tell the crew what you want and how you’ll know it works.
- 02
Set the boundaries.
Set the scope and checks. Want a plan first? Ask for a planning mission before starting the code.
- 03
See it take shape.
Follow the code, checks, and review without piecing together a dozen tabs.
- 04
Make the final call.
Look it over. Approve the change when you’re happy with it.
Manual review requires your approval after verification and independent review. Automatic checked applies after those gates pass; Fast can apply unchecked work. Enable automatic modes deliberately. CodeFloor does not commit, push, or publish your changes.
YES, THE OFFICE IS PART OF IT
Meet the crew.
Have a look around.
There’s a place to plan, a crew with different strengths, and a Brain that keeps useful project knowledge around. Also, yes: little pixel people walking to meetings.
YOUR DEVELOPMENT STUDIO
Six available specialists. Missions use the roles they need; simple work can take a smaller path.
SIX DIFFERENT STRENGTHS
Who’s on your crew?
Pick a specialist. See where they fit.
Ada / Architecture
See how the pieces fit.
Talk through structure, boundaries, and trade-offs before a change gets bigger than it needs to.
“Where should this feature live?”
Jules / Frontend
Make the part people use.
Work on screens, interactions, and the details that make a feature feel at home in your app.
“Can this flow be clearer?”
Otto / Backend
Get the moving parts working.
Work through the services, data, and application logic behind the feature you’re building.
“What needs to happen behind this button?”
Sage / Research
Check the ground before you build.
Explore the codebase and compare practical approaches, so the next step has some context behind it.
“What’s already here, and what are the options?”
Kit / Quality assurance
Ask how we’ll know it works.
Turn the intended behavior and awkward edge cases into checks you can inspect.
“What happens when this goes wrong?”
Remy / Code review
Get a fresh pair of eyes.
Look over the candidate change independently and assess it against the agreed scope and checks.
“Does this change hold up?”
The mission chooses the roles it needs. The Northstar example used Jules and Remy.
01 / TEAM PLANNING
Not sure where to start?
Talk it through.
Bring the rough version of the idea. Talk through the trade-offs with the crew, work out a clear next step, then decide when to start building.
- Six specialist perspectives at one table
- A scoped plan you can review before authorizing work
The team table Recorded installed app02 / SHARED PROJECT MEMORY
Less re-explaining.
More building.
You’ve already explained why the project works that way. Keep the useful decisions and lessons with it, so the next mission has somewhere to start.
- Project knowledge that stays with your project
- Relevant context for the next mission
The Brain archive Recorded installed appA LITTLE BACKUP FOR YOUR NEXT BUILD
One studio.
Your kind of commitment.
Both plans include the whole studio and all six specialists. Pick a preference for your invite. You can decide when access is available.
Monthly
TAKE IT A MONTH AT A TIMEFor the next feature, fix, or “let’s see if this works.”
$15.99/ month
Billed monthly.
Join early access · monthly- All six AI specialists
- Your own living development studio
- Project planning and coding missions
- Shared memory, checks, and review
Yearly
SAVE 32%For the projects you know you’ll keep coming back to.
$129.99/ year
Billed yearly. Equivalent to $10.83/month.
Join early access · yearly- All six AI specialists
- Your own living development studio
- Project planning and coding missions
- Shared memory, checks, and review
Save $61.89 versus twelve monthly payments.
Your CodeFloor plan covers the studio.
Connect your own eligible Codex account for real coding missions. Codex access and usage limits are managed separately by OpenAI.
Prices in USD. Both plans include the same CodeFloor features.
Join early access for availability details. No payment is collected today.
BEFORE YOU JOIN
Before you
move in.
Fair questions. Here’s the honest version.
Why use this alongside Codex?
Codex does the coding. CodeFloor gives the work a home: a crew, project conversations, clear tasks, saved context, checks, and review. You connect your own eligible Codex account. CodeFloor is a separate product.
Who is the first early-access cohort for?
We’re starting with people building on Windows who already use Codex: solo developers, founders who code, and small teams. You’ll want a Git repo, one clear first task, and enough coding experience to review the result. Join the list and we’ll share the invite and setup details.
Can I use it without being a developer?
You can look around and work through an idea with the crew. For the first coding release, you’ll need to be comfortable with Git, Codex, and reviewing code—or have a technical collaborator help with setup, checks, and the result.
What is CodeFloor?
It’s a Windows development studio with six AI specialists and a living pixel-art office. You can talk through an idea, set a coding task, follow the checks and review, and keep useful project knowledge for next time.
Does it actually write code?
Yep. Coding missions use Codex with your local Git repo in a private workspace. You can inspect the changes, commands, checks, and review before bringing the code into your project. There’s also a simulation mode if you just want to explore the office.
Is Codex access included in the price?
Your CodeFloor subscription covers the studio. You’ll need your own eligible Codex account for coding missions. OpenAI manages Codex access, usage limits, and any provider charges. CodeFloor is independent and is not affiliated with, sponsored by, or endorsed by OpenAI.
What do I need to run it?
A 64-bit Windows PC, Git, a local repo, and a compatible Codex CLI signed in with an eligible ChatGPT account. If you want local AI discussions too, there’s a one-time model setup. We’ll walk through the setup details for early access.
Is everything running locally?
Your studio, saved state, and project workspaces stay on your PC. Local-model conversations can work offline once set up. Coding missions use Codex, connect to OpenAI, and need an internet connection.
How much control do I have?
You pick the project, approve missions, and set the boundaries. In Manual review, you get checks and independent review before you approve bringing the change into your project. Automatic checked applies after those checks and review pass; Fast can apply unchecked work. You have to enable automatic modes yourself. CodeFloor doesn’t commit, push, or publish your changes for you.
When can I get it, and what will it cost?
We’re getting the first early-access group ready. Leave your email and we’ll keep you posted on invites and setup. It’s $15.99 a month or $129.99 a year (USD), with $61.89 saved on yearly versus twelve monthly payments. Joining the list is free. You’re not buying anything today.
LET’S BUILD SOMETHING
Got a project
in mind?
Leave your email and we’ll let you know when the first invites go out. In the meantime, think of one thing you’d love to get off your backlog.
- 01
Join the list. Leave your email. A plan preference is optional.
- 02
Get the details. We’ll share invite and setup information.
- 03
Make your call. Decide whether it fits when you get access.
Your next build can start small.Windows + your own eligible Codex access.