Sits beside the agent you already pay for

Your agent
keeps forgetting.

Every session, it starts blind. It rewrites the helper you wrote last week, retries the command that just failed, and spends your tokens relearning a codebase it already knew yesterday.You shouldn't have to keep explaining your own project. That's our job.

Free forever · Your own API key · Nothing you write passes through us

Good with

  • Claude Code
  • Cursor
  • Copilot
  • Gemini CLI
  • Windsurf
  • Cline

You know this one

Brilliant for ten minutes. Then it starts guessing.

It rewrites what you already wrote

It cannot see the 400 functions already in your repo. So you get formatDate() again, in a third file, subtly different. You catch it in review — or nobody does.

It tries the same thing, again and again

Build fails. It changes a type, runs the same command, fails the same way, changes another type. Each step looks sensible on its own. That is exactly why it never stops.

One compaction and your context is gone

Twenty minutes explaining your architecture. Then one /compact, and it is back — confidently wrong about where everything lives. So you explain it again.

It is working from a map that expired

It learned your structure sixty commits ago. Nothing tells it that. Nothing tells you either, until it edits a file that moved last Tuesday.

So what is that costing you?

One developer, one week. Put your own numbers in — it is the shape that matters here, not the decimals.

6h

Explaining your project all over again

about 35 minutes a day

4h

Finding and deleting the duplicates

only the ones that reach review

120k

Tokens spent relearning your layout

and every new session pays again

3x

Attempts at the same failing command

before someone steps in

Assumes one developer, using an agent daily, on a codebase past ~300 files. Yours will differ. But if one of those made you wince, that is the one to fix.

Not a mockup

Watch it catch one.

This is the real output, from this website's own codebase. The agent started writing a helper that already existed two folders away.

apps/web/app/api/auth/guest/route.ts

// agent is writing…

export function safeRedirectPath(value: string) {

FlowKy: this symbol already exists in this codebase.

• safeRedirectPath — already defined in apps/web/src/lib/safe-redirect.ts:14

Import and reuse the existing definition, or extend it.

// agent, corrected:

import { safeRedirectPath } from '@/lib/safe-redirect';

Caught before the file was written — not in review, not in production.

Here is where we come in

The guardrails your agent was never given.

01

You stop finding duplicates in review

We keep an index of every function and class you have. The moment your agent starts writing one that exists, it gets the file and the line — and imports it instead.

PreToolUse hook · fires on every write

02

You stop paying for the same attempt

Third time that command has failed? We step in, surface the error it kept skipping past, and make it try something else rather than spend your budget on attempt four.

Circuit breaker · per-session state

03

You always know how stale the map is

We check the map against HEAD and say how far it has drifted, before anything gets built on it. A stale map that reads as confident is worse than no map at all.

SessionStart hook · git-aware

04

Your context budget stays yours

Your tree, symbols and import graph sit in a skill your agent opens only when it needs them. Every session that does not, pays nothing for them.

On-demand skill · not a system prompt

05

Your CLAUDE.md stops working against you

Duplicated rules, dead weight, instructions that quietly stop applying after a compaction. We find them and tell you exactly what to cut.

Config doctor · 9 checks

06

Your keys never leave your machine

Claude, Gemini, GPT, or anything OpenAI-compatible. Your keys stay in your editor, and not one request passes through us.

BYOK · zero prompt logging

You do the thinking.
We keep watch.

Not another agent to manage.The one already watching your back.

Sound like your week?

The solo builder

“I ship fast, then spend Sunday deleting what the agent duplicated.”

FlowKy catches it at write time, so Sunday stays yours.

The team lead

“Every dev's agent invents its own conventions. Review is where I find out.”

One config, committed to the repo. Every agent on the team reads the same rules.

The agency

“Twelve client codebases. The agent knows none of them on Monday morning.”

A map per repo, refreshed on demand. Context switching stops costing an hour.

Start free. Stay free if you like.

You bring your own API key, so the guardrails cost us almost nothing to run. We would rather they were installed everywhere than gated.

Where to start

Free

€0 forever

Everything that stops your agent wasting your time.

  • Duplicate guard on every write
  • Project map as an on-demand skill
  • Staleness warnings each session
  • Loop breaker
  • Config doctor
  • 30 assisted requests a day
Start free

Pro

€19 per month

For people whose agent runs all day.

  • Everything in Free
  • 300 assisted requests a day
  • Multi-repo project maps
  • Priority support
Go Pro

Enterprise

€49 per month

Shared configuration across a team.

  • Everything in Pro
  • 2,000 assisted requests a day
  • Team-wide rules and guards
  • SSO and audit log
Talk to us

The things you are actually wondering

  • One command generates everything, and after that it maintains itself. The guard runs on hooks your agent already fires — you do not call it, remember it, or prompt it. If you never open FlowKy again, it keeps working.

  • No. The index lives in your repository, the guard runs on your machine, and your API key stays in your editor. Not one inference request passes through us. The only thing we ever receive is a count of requests, for your plan limit — no code, no file paths, no prompts.

  • No, and it would be a worse product if it tried. You keep the agent you like. We sit underneath it and stop it repeating itself — which is the part none of them do for you.

  • It asks, it never blocks. Overloads and re-exports are legitimate, so a hard block would produce false positives and you would turn it off within a week. You get the file and line, and you decide.

  • Yes — macOS, Linux and Windows. The hooks are Node rather than shell scripts precisely so there is no second-class platform.

  • The map records the commit it was built from. At the start of every session you are told how far it has drifted and which areas moved, so a stale map is never mistaken for a current one. Regenerating takes seconds.

In development

FlowKy helps you sell
what you build.

We help you ship it. Then we help you sell it. List your products and services — sites, apps, stores, rescues — and let buyers find you by what you actually deliver, not by who paid to be at the top.

Seller plan

$9.90/month

A flat fee to publish. We take nothing from what you earn.

  • Unlimited services listed
  • Public profile with your shipped work
  • Direct enquiries from buyers
  • Keep 100% of what you charge
  • A badge that grows as you deliver

Nothing is charged today. Profiles open once buyer messages and payouts actually work — we are not taking a monthly fee for a listing nobody can reach yet.

Get clients.

Buyers arrive knowing what they want built and roughly what it costs. You do not write a proposal to find out whether they are serious.

  • Briefs with a budget already attached
  • Your verified work does the convincing
  • Keep everything you charge

Join the FlowKy community

Builders sharing what actually ships — the rescues, the rates, the clients worth taking.

Reserve your handle now. Nothing is charged until profiles open.

Let's stop repeating yourself.

Install once, and we are there every session after — with whichever agent you already use, on macOS, Linux or Windows.

Bring us along — free

No card · Your own API key · Two minutes to set up

FlowKy — the sidekick for your coding agent | FlowKy