Forge - The coding agent that keeps you in the loop

by•
Forge is an open-source desktop coding agent that shows its plan before touching your code and asks before every edit or command. Provider-flexible, with a plan agent, three edit modes, and apps for macOS, Windows and Linux. A fork of OpenCode.

Add a comment

Replies

Best

Hey Product Hunt, I’m Divyanshu, the maker of Forge.

I like open coding agents, but I wanted one that felt more like Claude Code. I wanted it to stop and show me what it was about to do, rather than quietly doing it. So I forked OpenCode and changed how it looks and behaves.

What’s different from OpenCode

  • Edit modes: Forge asks before every file edit and shell command by default. You can switch to Accept Edits, Auto or Plan. Anything you set to deny in config stays denied in every mode.

  • Plan review: The plan agent writes a Markdown plan in a side panel. You can comment on specific passages, then accept, revise or deny it. Proposed edits show up as diffs before you approve them.

  • Chapters: Pin a message to start a titled chapter and jump around from a rail beside the transcript. Forge also adds chapters automatically after compaction or when you link an issue or PR.

  • PR tracking: Sessions remember the GitHub PRs and GitLab MRs they open, with their state and CI status. Auto-fix is opt-in and tries up to three CI repairs. Forge never merges, closes or pushes on its own.

  • Run in terminal: One click runs a shell block from a reply in the session terminal. The exit code and output go back to the agent.

  • Local memory: Per-project notes live in a MEMORY.md file you can edit.

  • Git and browser: Git actions live in the review panel. There’s also a built-in browser that shares tabs with the agent for screenshots and debugging.

What’s inherited from OpenCode: providers and models, MCP, skills, plugins, and the and subagents.

Yes, a lot of this could have been a feature request on OpenCode. But I mostly work with agents through desktop apps now. OpenCode is a large project with several product lines, so it moves a bit slowly. I also like Claude Code’s design philosophy for building a harness. So I forked it rather than push my preferences onto upstream.

Caveats

  • Forge is a personal project, not a supported product, and it isn’t affiliated with OpenCode, Anthropic or Claude Code. It’s a fork, so OpenCode’s changes and fixes keep flowing downstream into Forge. That means general bug reports and feature requests are best sent to OpenCode, where they’ll help everyone. If there’s a Claude Code-style quirk you’re missing, though, I’d be happy to build it into Forge. Issues and PRs are welcome.

  • Installers aren’t code-signed yet. macOS and Windows will warn on first launch, and the README has the workarounds.

  • No terminal UI. Forge is desktop-first, so I removed OpenCode’s TUI client. If you mostly work in a terminal, upstream OpenCode is the better fit.

It’s MIT licensed and a fork, so upstream OpenCode releases keep getting merged in. I’d love to hear which approval flows feel too noisy or too loose. What would make you trust an agent with your project?