Code
IMPLEMENTATION
Jules
Add the theme preference and dark palette. Preserve the existing screens, navigation, and acceptance checks.
YOUR AI DEVELOPMENT STUDIO
Turn your next idea
into work you can review.
Bring an idea, feature, or bug. Your AI crew helps plan the work, make code changes, and present the result for your review in one Windows development studio.
Get launch and access details. No payment or purchase commitment.
Windows desktop · $15.99/month or $129.99/year · USD
Works with OpenAI Codex
Connect your own account for real coding missions.
The living studio · recorded office activityRECORDED IN CODEFLOOR · DEMO ACTIVITY
Six specialist perspectives.The right roles for the work at hand.
THE COST OF “I’LL GET TO IT”
Another week.
The same unfinished idea.
There’s always another bug, another deadline, another reason to push your own project back. Make room for the build you keep thinking about.
Be there when CodeFloor opensFROM THE FIRST BRIEF TO THE FINAL CLICK
Small request.
See the whole story.
One real mission, from a missing dark-mode preference to a working feature. Watch the work come together. Then try the result yourself.
Northstar / A theme that remembers✓ 8 / 8 checks · independently reviewed
LOOK A LITTLE CLOSER
Explore the handoff. Make the final click.
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.”
A focused change to theme.js and styles.css, with a clear acceptance contract.
- 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 transcript and mission context
00:00 — One choice. A workspace that remembers you. A full-screen light-to-dark reveal introduces the real Northstar sample. One request produces a working feature.
00:08 — A clear finish line. A close-up of the actual desktop brief shows the two allowed files, theme.js and styles.css, and the preserved screens and browser contract.
00:13 — A focused change. A fresh pair of eyes. Jules implemented the change; Remy reviewed it independently. The office image behind these role cards is illustrative product footage.
00:18 — The actual change. Close-ups of the reviewed theme.js show reading the saved preference, following the system until an explicit choice, and persisting that choice.
00:25 — The result has receipts. All eight recorded browser scenarios passed, up from two before the change. The actual desktop evidence shows accepted independent review. Manual approval applied the same revision, followed by a separate passing rerun.
00:33 — Choose. Navigate. Reload. Fresh browser footage of the unchanged applied app shows dark mode being selected, navigation to Activity, a reload retaining the preference, and a return to Overview. The camera and cursor highlights guide attention to the actual controls.
00:45 — From your idea. To your next step. Explore the evidence and try the finished feature below. This 50-second HD edit includes original instrumental music and synchronized sound effects, with no speech. All explanatory content is visible on screen and available here. A sample result does not guarantee the outcome or duration of another mission.
Imagine this handoff for your next build.
A clear goal. Work you can review. Your final decision.
A NEXT STEP FOR YOUR KIND OF WORK
What would you
move forward?
An existing codebase, an early idea, or a team backlog. Start with one result and a scope you can judge.
Solo developers
Fix the recurring bug. Add the next feature. Keep your attention on the decisions that need you.
Scoped changes with evidence to inspect.Nontechnical founders
Shape an early product idea into a technical plan and a bounded first feature, with setup and review support where needed.
A concrete starting point for your product.Small teams
Give a defined backlog task a clear brief. Follow specialist work, checks, and review in the same workspace.
A handoff your team can assess.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
You set the goal.
You make the call.
Define success and review the approach. Follow implementation, observed checks, and independent review before deciding what enters your project.
- 01
Define the result.
Pick your project and describe what a good result looks like.
- 02
Authorize the approach.
Set the scope and acceptance checks before authorizing implementation. Ask for a planning mission first if you want a separate plan to approve.
- 03
Follow the work.
Follow implementation, verification, and review in one place.
- 04
Approve integration.
Inspect the result and approve what goes into your project.
Manual review runs verification and independent review before you approve integration. Automatic checked applies changes after those gates pass; Fast can apply unchecked work. Choose the delivery mode deliberately. CodeFloor does not commit, push, or publish changes for you.
A WORKSPACE THAT CONNECTS THE WORK
One studio.
Context for the next mission.
Keep project conversations, specialist work, and retained knowledge together. Explore the studio behind the workflow. Office scenes show the visual experience; the mission above shows an actual result.
YOUR DEVELOPMENT STUDIO
Six available specialists. Missions use the roles they need; simple work can take a smaller path.
SMALL CREW.Big range.
AdaArchitecture
JulesFrontend
OttoBackend
SageResearch
KitQuality assurance
RemyCode review
01 / TEAM PLANNING
Your idea.
A clear plan to build it.
Bring the feature, bug, or side project. Your crew helps shape the scope, surface trade-offs, and turn the conversation into a mission you can review.
- Six specialist perspectives at one table
- A scoped plan you can review before authorizing work
The team table Installed app snapshot02 / SHARED PROJECT MEMORY
Less re-explaining.
More building.
Keep useful decisions, project notes, and lessons close. Give the next mission relevant context from the work that came before it, so you spend less time setting the scene.
- Project knowledge that stays with your project
- Relevant context for the next mission
The Brain archive Installed app snapshotA STUDIO FOR THE WORK AHEAD
Put a crew
behind your next build.
Your CodeFloor subscription covers the studio and its orchestration features. Both plans include the same six-specialist roster. Select an optional preference when you join the launch list.
Monthly
FIND YOUR RHYTHMThe complete studio, billed month by month.
$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%The same full studio, with a lower yearly cost.
$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
Keep $61.89 for your next big idea, every year.
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.
A few things to know about your future studio.
Why use this alongside Codex?
Codex performs the coding work. CodeFloor brings the surrounding workflow into a visual studio: project conversations, scoped missions, specialist coordination, retained context, observed checks, and review. You connect your own eligible Codex account; CodeFloor is a separate product.
Can I use it without being a developer?
You can bring an idea and work through a technical plan with the crew. Real coding missions still require a Windows computer, Git, a local repository, and a compatible signed-in Codex CLI. You may need technical help with setup, choosing acceptance checks, and reviewing the resulting code. Start with a bounded first feature and arrange the oversight your project needs.
What is CodeFloor?
CodeFloor is a desktop development studio built around six AI specialists in a living pixel-art office. It brings project conversations, planning, real coding missions, verification, review, and retained project knowledge into one workspace.
Does it actually write code?
Yes. Real missions use Codex to work with a local Git repository in a private workspace. CodeFloor can retain the resulting changes, command evidence, checks, and reviews so you can inspect the work before integration. The office also includes a simulation mode for exploring the experience.
Is Codex access included in the price?
Your CodeFloor plan covers the studio and its orchestration features. Connect your own eligible Codex account for real coding missions. Codex access, usage limits, and any provider charges are managed separately by OpenAI. CodeFloor is an independent product and is not affiliated with, sponsored by, or endorsed by OpenAI.
What do I need to run it?
The current desktop build is for 64-bit Windows. Real coding missions require Git, a local repository, and a compatible installed Codex CLI signed in with an eligible ChatGPT account. Optional local AI discussions require a one-time model setup. We’ll share onboarding details with early access.
Is everything running locally?
The studio, its saved state, and project workspaces live on your computer. Optional local-model conversations can run offline after setup. Codex coding missions connect to OpenAI and require internet access; they are not offline inference.
How much control do I have?
You choose the project, authorize missions, and set the boundaries for ongoing work. Manual review supports verification, independent review, and your integration approval. Automatic checked applies after those gates pass; Fast can apply unchecked work. Automatic modes must be enabled deliberately. CodeFloor does not commit, push, or publish your changes for you.
When can I get it, and what will it cost?
CodeFloor is $15.99 per month or $129.99 per year (USD). The yearly plan saves $61.89 compared with twelve monthly payments. Join the early-access list to hear about availability and access details. Joining does not require payment or commit you to a purchase.
YOUR NEXT STEP STARTS HERE
Give your next
build a crew.
Join the early-access list for launch news, availability, and access details. Leave your email, choose a plan preference if you like, and decide whether CodeFloor fits when access opens.
A clear next step.Launch and access details, straight to your inbox.