frink

<h1 align="center"> <a href="https://frink.dev"><img src="build/icon.png" alt="Frink" width="64" valign="middle" /></a> Frink </h1> <p align="center"> <a href="https://github.com/benord-labs/frink"><img src="https://img.shields.io/github/stars/benord-labs/frink?style=flat&amp;label=%E2%98%85&amp;color=8B5CF6" alt="GitHub stars" /></a> <img src="https://img.shields.io/badge/license-MIT-8B5CF6?style=flat" alt="License: MIT" /> <img src="https://img.shields.io/badge/macOS%2013%2B%20%7C%20Linux-4493F8?style=flat-square" alt="Supported platforms: macOS 13 or later, and Linux" /> </p> <p align="center"> <strong>Fine-tuned automation for everyone.</strong><br/> A ticket arrives, an error fires or the clock hits 9am: your Flow runs the steps you chose and stops where it needs you. </p> <p align="center"> Triggers from Linear, Jira, Shortcut, ClickUp, Sentry, PostHog, Vercel and more, plus any webhook or a schedule.<br/> Stuck agents wait in the Work Queue for your yes, on your Mac or from your iPhone (beta).<br/> It runs on your machine with your own Claude Code or Codex login. No Frink account. </p> <p align="center"> A friendly AI development tool for everyone: start with a chat, save it as a Flow, run agents side by side. </p> <h3 align="center"><a href="https://frink.dev/download"><ins>Download Frink</ins></a></h3> <p align="center"> <a href="user-docs/getting-started.md"><picture><source srcset="docs/assets/readme/overview.webp" type="image/webp"><img src="docs/assets/readme/overview.jpg" alt="A sentence typed into Frink becomes a Flow with a schedule and an approval step, a finished task is reviewed from the Work Queue, and four agents work side by side" width="960" /></picture></a> </p> ## Features <table> <tr> <td width="50%" valign="middle"> ### Run four agents side by side 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. [Docs →](user-docs/worktree-setup.md) </td> <td width="50%"> <a href="user-docs/worktree-setup.md"><picture><source srcset="docs/assets/readme/agents.gif" type="image/gif"><img src="docs/assets/readme/agents.jpg" alt="Four panes, each with an agent working on a different task in the same project at the same time" width="100%" /></picture></a> </td> </tr> <tr> <td width="50%" valign="middle"> ### One sentence becomes an automation 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. [Docs →](user-docs/flows.md) </td> <td width="50%"> <a href="user-docs/flows.md"><picture><source srcset="docs/assets/readme/flow.gif" type="image/gif"><img src="docs/assets/readme/flow.jpg" alt="Asking the agent to save a weekday test-and-fix routine as a Flow" width="100%" /></picture></a> </td> </tr> <tr> <td width="50%" valign="middle"> ### It starts when something happens A new ticket in Linear, Jira, Shortcut or ClickUp, an error in Sentry, an event in PostHog, 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. [Docs →](user-docs/plugins.md) </td> <td width="50%"> <a href="user-docs/plugins.md"><picture><source srcset="docs/assets/readme/triggers.gif" type="image/gif"><img src="docs/assets/readme/triggers.jpg" alt="Choosing a Flow trigger, then a condition step and an approval step" width="100%" /></picture></a> </td> </tr> <tr> <td width="50%" valign="middle"> ### Everything that needs you, in one queue 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. [Docs →](user-docs/task-lifecycle.md) </td> <td width="50%"> <a href="user-docs/task-lifecycle.md"><picture><source srcset="docs/assets/readme/queue.gif" type="image/gif"><img src="docs/assets/readme/queue.jpg" alt="Reviewing a finished task from the Work Queue and marking it complete" width="100%" /></picture></a> </td> </tr> <tr> <td width="50%" valign="middle"> ### Check the work and fix it yourself 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 back to an earlier checkpoint. [Docs →](user-docs/changes.md) </td> <td width="50%"> <a href="user-docs/changes.md"><picture><source srcset="docs/assets/readme/editor.gif" type="image/gif"><img src="docs/assets/readme/editor.jpg" alt="Opening a file from the tree, editing it and saving, with the change shown inline" width="100%" /></picture></a> </td> </tr> </table> **Also in the box:** - **[Permissions](user-docs/permissions.md)** — every tool call passes a per-project gate first; `~/.ssh`, `~/.aws` and `.env` are always off-limits. - **[Plugins & MCP](user-docs/mcp-servers.md)** — connect Linear, Shortcut, ClickUp, GitHub, Notion, Slack, Sentry, PostHog and more, as chat tools and Flow steps. - **[Your own AI sign-in](user-docs/ai-accounts.md)** — uses your existing Claude Code or Codex login. Frink never stores the token. - **Local-first** — chats, Flows, tasks and permissions live in SQLite on your machine. No account needed. Official builds send anonymous usage counts and crash reports: [everything Frink sends](user-docs/telemetry.md). --- ## Supported Agents <p> <a href="https://docs.anthropic.com/claude/docs/claude-code"><kbd><img src="https://www.google.com/s2/favicons?domain=anthropic.com&sz=64" alt="Claude Code logo" width="16" valign="middle" /> Claude Code</kbd></a> &nbsp; <a href="https://github.com/openai/codex"><kbd><img src="https://www.google.com/s2/favicons?domain=openai.com&sz=64" alt="Codex logo" width="16" valign="middle" /> Codex</kbd></a> </p> Bring your own subscription or API key — Frink runs the agent, you keep the account. --- ## Install - **[Download from frink.dev](https://frink.dev/download)** - Or grab a build directly: [macOS Apple Silicon](https://pub-c942ee0fa0a549ef8d66096bd831507b.r2.dev/Frink-0.3.0-arm64.dmg) · [macOS Intel](https://pub-c942ee0fa0a549ef8d66096bd831507b.r2.dev/Frink-0.3.0.dmg) - Or build from source — see [CONTRIBUTING.md](CONTRIBUTING.md). ### Linux (x64 and arm64) Download the AppImage or the `.deb` from [frink.dev/download](https://frink.dev/download), or directly: x64 [AppImage](https://pub-c942ee0fa0a549ef8d66096bd831507b.r2.dev/Frink-0.3.0.AppImage) · [.deb](https://pub-c942ee0fa0a549ef8d66096bd831507b.r2.dev/frink_0.3.0_amd64.deb), arm64 [AppImage](https://pub-c942ee0fa0a549ef8d66096bd831507b.r2.dev/Frink-0.3.0-arm64.AppImage) · [.deb](https://pub-c942ee0fa0a549ef8d66096bd831507b.r2.dev/frink_0.3.0_arm64.deb). Both update themselves. - **AppImage** (any distro): `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. - **.deb** (Debian/Ubuntu): `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. --- ## Community & Support - **Bugs & ideas:** [open an issue](https://github.com/benord-labs/frink/issues). - **Changelog:** [frink.dev/changelog](https://frink.dev/changelog). - **Show support:** [star](https://github.com/benord-labs/frink) the repo to follow along. --- ## Developing Want to contribute or run locally? See our [CONTRIBUTING.md](CONTRIBUTING.md) guide. ## License Frink is licensed under the [MIT License](LICENSE). Copyright 2026 Benji Norval. Third-party licenses are listed in [THIRD_PARTY_LICENSES.md](THIRD_PARTY_LICENSES.md).