Build at full speed.
Understand everything.
Collaborate with Humans.
FlumeCode is the most organized way to do agentic coding — keep track of every result your AI agents produce, and collaborate with other agentic coders on one platform.
A process that keeps you in the loop
Every change moves through three steps you can read and steer — not a black-box diff.
Request
Open a request and tell the agent what you want to build — a one-line idea or a detailed spec. It reads a frozen checkout of your code and issues, so it works from the real thing.
Add a dark-mode toggle to the nav bar. The user's choice should persist across reloads. Keep it simple — no external theming library needed.
Plan
Shape that request into an implementation-ready plan, together with the agent. You refine the approach until it is right — and nothing touches your code until you accept it.
A couple of questions before I plan:
Implementation plan
- Create
ThemeTogglecomponent — button with sun/moon icon, reads/writeslocalStorage. - Apply
data-themeattribute to<html>on mount and on toggle. - Add CSS tokens for
[data-theme="dark"]overrides intokens.css. - Mount
<ThemeToggle />inside the existing<Nav>component.
Acceptance criteria
- A toggle is visible in the nav bar.
- Preference persists across page reloads.
Open coding session →- Create
Delegate
Once you accept the plan, an AI agent implements it for you — running the changes in your machine, not on a remote box.
Sync
Get back a detailed report and understand exactly what the agent changed and why. Spot something off? Send it back for revisions — you stay in the loop the whole way.
Added a dark-mode toggle to the top navigation bar. The preference is persisted in localStorage and applied via a `data-theme` attribute on `<html>`.
Files changed
src/components/ThemeToggle.tsx(new)src/components/Nav.tsx(modified)src/styles/tokens.css(modified)
Acceptance criteria
✓ metA toggle is visible in the nav bar
ThemeToggle renders as a button inside Nav with a sun/moon icon.
src/components/Nav.tsxThemeToggle imported and placed in the nav.
@@ -12,6 +12,7 @@ +import { ThemeToggle } from './ThemeToggle'; ... +<ThemeToggle />✓ metPreference persists across page reloads
The hook reads and writes to localStorage on mount and on toggle.
src/components/ThemeToggle.tsx@@ -0,0 +1,22 @@ +const stored = localStorage.getItem('theme'); +document.documentElement.dataset.theme = stored ?? 'light';
Code quality
Clean implementation. The toggle is self-contained and the CSS token approach means no component-level style overrides are needed.
Caveats / follow-ups
None.
How FlumeCode helps you with agentic coding?
Fine-control agents, readable reports, organized work, and human-level communication — built around the way agents actually code.
Agents that actually listen
Tired of agents running off and writing code you never asked for?
FlumeCode double-checks what you really mean before it starts building, so you get exactly what you pictured — no surprises.
Add a dark-mode toggle and refactor the Nav #12
openmain frozen at da68575Add a dark-mode toggle to the nav and refactor the Nav component while we're at it. Persist the choice across reloads.
Add a dark-mode toggle and refactor the Nav
request #12Add dark-mode toggle #31
Refactor the Nav component #32
See exactly what changed
Drowning in a wall of agent-generated code?
FlumeCode hands you a friendly, easy-to-read recap after every coding session, so you always know what just happened.
Added a dark-mode toggle to the top navigation bar. The preference is persisted in localStorage and applied via a `data-theme` attribute on `<html>`.
Files changed
src/components/ThemeToggle.tsx(new)src/components/Nav.tsx(modified)src/styles/tokens.css(modified)
Acceptance criteria
✓ metA toggle is visible in the nav bar
ThemeToggle renders as a button inside Nav with a sun/moon icon.
src/components/Nav.tsxThemeToggle imported and placed in the nav.
@@ -12,6 +12,7 @@ +import { ThemeToggle } from './ThemeToggle'; ... +<ThemeToggle />✓ metPreference persists across page reloads
The hook reads and writes to localStorage on mount and on toggle.
src/components/ThemeToggle.tsx@@ -0,0 +1,22 @@ +const stored = localStorage.getItem('theme'); +document.documentElement.dataset.theme = stored ?? 'light';
Code quality
Clean implementation. The toggle is self-contained and the CSS token approach means no component-level style overrides are needed.
Caveats / follow-ups
None.
Keep everything tidy
Juggling a pile of issues at once and losing track?
FlumeCode keeps your work neatly organized and shows what's in flight, so you never lose your place.
Communicate with other people
Not sure how to collaborate with other people who also work with agents?
FlumeCode gives you a cozy space to talk things through with real people, all built on top of nicely-organized agent work.
Before I plan the change, where should the dark-mode preference be stored?
Gentle question, Ada — did we consider syncing the theme server-side so it follows users across devices? Happy to go with localStorage either way.
Build in public with an open process
Software engineering is shifting from writing good code to writing good instructions for AI agents. So "open source" can grow into "open process": anyone contributes prompts and ideas, not just code.
On public repositories, FlumeCode opens that space — sketch an idea, let the community vote it up, and talk it through with real people before an agent ever runs.
Persist the dark-mode choice across devices #7
promoted12Add keyboard shortcuts for the nav #9
5Tighter spacing on mobile cards #11
2