AI Decision System
Replayable, offline-verifiable records for AI-assisted go/no-go decisions: experiment promotions, typed model answers and human-approved actions.
翻譯準備中
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證A friendly AI development tool for everyone.
翻譯準備中
取自儲存庫 README
正在載入完整 README。 以下為已儲存的摘錄。
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.檢視完整 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.