返回资讯中心
外部精选
软件工程
#开发者实时流

Show HN: Frink – Desktop-first app for multi-step workflows and parallel agents

What’s up HN?! I'm Benji, and I’ve been building Frink since ~April this year.Frink is a desktop-first, open-source (MIT) app for running coding agents in parallel and multi-step workflows that start on their own. It ru…

Hacker News 最新norvalbv2026/10/20 · 26 天前6 分钟阅读

以下正文同步自 Hacker News 最新,版权归原站所有,已转换为易读排版。

What’s up HN?! I'm Benji, and I’ve been building Frink since ~April this year.Frink is a desktop-first, open-source (MIT) app for running coding agents in parallel and multi-step workflows that start on their own. It runs on your machine (macOS and Linux) with your own provider login. It currently supports Claude Code, Codex, Cursor, Copilot, and OpenCode, but the latter 3 are in preview. No Frink account to use the app.The biggest USP of Frink is workflows: think n8n for agents. You describe a routine in a sentence, for example: "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." Then, Frink builds it as a workflow (or simply, Flow): a list of steps you can read and change before it runs. A Flow can start on a schedule, from any webhook, or from an event from a third-party such as Linear, Shortcut, ClickUp, Sentry, PostHog, etc. Steps can be agent turns, shell commands, conditions, approval steps that stop and wait for you, or steps you write yourself in code (or ask the agent to write one). Everything that needs you (an approval, an agent's question, a finished task to review) lands in one Work Queue.Other stuff:

  • Up to four agents side by side, each on its own git worktree if you want. Or, many agents out of direct view.
  • Every change shows as a diff; there's a code editor, a terminal, etc.
  • Local-first: chats, Flows and tasks live in SQLite on your machine.
  • Easier provider parity: currently working on and improving the tooling setup between providers. Once inside Frink, irrespective of what provider you use, the hooks, MCPs, and other tooling work out of the box between providers.Why I built it: I started building it when there weren’t many other competitors; now the industry is swamped with ADEs and harnesses. However, in my opinion, each still lacks good automation for more fine-tuned scenarios. I doubled down on the flows to help me with my actual day-to-day job as a SWE, and over time it’s helped me automate most of the PRs being shipped across my personal projects, team, etc., to the point that it’s a continuous loop and helps a whole ton.Notes: Windows isn't supported yet. Flows only run on Claude Code and Codex for now. It's a solo project, so expect sharp edges. Comments URL: https://news.ycombinator.com/item?id=50169829 Points: 1

Comments: 0

正文由 探How 从来源站点 RSS 同步,内容未经改写;遇到排版缺失或需要图片、视频时请以原文为准。

打开原文
去社区讨论 →