AI Decision System
Replayable, offline-verifiable records for AI-assisted go/no-go decisions: experiment promotions, typed model answers and human-approved actions.
The friendly AI dev tool: chat with the agent you already have, then turn what works into a Flow that runs on its own.
Developer toolsTypeScript · JavaScriptGitHub @benord-labsOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
A friendly AI development tool for everyone.
Translation pending
Taken from the repository README
Loading the full README. The saved excerpt is shown below.
A friendly AI development tool for everyone.
Start with a chat, save it as a Flow, run agents side by side — each on its own copy of your project.
Describe it the way you would to a colleague. The agent builds it and shows its work as it goes — no setup, no jargon.
Turn a one-off chat into a repeatable automation: what sets it off, what the agent does, what happens next. Then it runs itself.
Start a Flow from a schedule, a Linear or Shortcut ticket, a Sentry error, a PostHog event or any webhook. Add a condition, and a step where it stops and asks you.Read the full README ↗Split the window into up to four panes and give each agent a different job. They work at the same time, and each pane keeps its own model and its own diff to review. Put each one on its own git worktree and they never touch the same files.
Type the routine the way you would say it: "Every weekday at 9am, run the tests. If any fail, have an agent fix them, then wait for my approval before it opens a PR." Frink builds it as a Flow and lists every step, so you can read it and change it before it runs.
A new ticket in Linear, Shortcut or ClickUp, an error in Sentry, an event in PostHog or Vercel, any webhook, or a time of day. The Flow checks a condition to pick its path, and waits at an approval step until you say yes.
Every run from every project shows up in the Work Queue as running, ready for review or queued. A badge appears when a Flow stops for approval or an agent has a question. Read what it did, then approve it or reply to send it back.
Every file the agent changes shows as a diff. Open it in the built-in editor, change a line and save, run a command in the terminal, or roll the chat and its code back to an earlier point.
Also in the box:
Bring your own subscription or API key — Frink runs the agent, you keep the account.
Download the AppImage or the .deb from frink.dev/download, or directly: x64 AppImage · .deb, arm64 AppImage · .deb. Both update themselves.
chmod +x Frink-X.Y.Z.AppImage && ./Frink-X.Y.Z.AppImage, with X.Y.Z the version you downloaded. It does not need libfuse2: it mounts itself with fusermount3 from the fuse3 package. If it will not start, install fuse3 or start it with --appimage-extract-and-run. Keep it in a folder you can write to, such as ~/Applications, so updates can replace it.sudo apt install ./frink_X.Y.Z_amd64.deb (_arm64.deb on arm64). Updates ask for your password in a system prompt.Frink saves API keys and MCP credentials only when it can encrypt them with a desktop keyring (GNOME Keyring or KWallet). Without one it does not save them, so install one and relaunch Frink before adding accounts.
Want to contribute or run locally? See our CONTRIBUTING.md guide.
Frink is licensed under the MIT License. Copyright 2026 Benji Norval.
Third-party licenses are listed in THIRD_PARTY_LICENSES.md.