Web and desktop harness for OpenCode — a project sidebar, usage dashboard, runs, workflows, artifacts and routines, with a polished composer.
🌐 Website: flupcode.com · 🖥️ Web app: app.flupcode.com · 💻 Source: rldona/FlupCode · ⬇️ Download
FlupCode is a fork of OpenCode that takes its terminal-grade feature set and packages it into a first-class web and desktop experience: a harness layout with a project sidebar, usage dashboard, runs, workflows, artifacts, routines and a polished composer — modelled on the Anthropic Claude Code desktop app.
Requires the OpenCode engine. FlupCode is a client and does not bundle it: install the OpenCode CLI and the app connects to it. Without an engine reachable, the desktop app, the hosted web app and
flupcode remotecannot run.
Not affiliated with OpenCode or Anthropic. FlupCode is an independent fork. "OpenCode" is the upstream project by Anomaly, and "Claude Code" is a product of Anthropic. This fork is not built by, endorsed by, or affiliated with either of them.
OpenCode is already a client/server system: opencode serve exposes an HTTP + SSE API and every
front-end (terminal TUI, web app, desktop app, IDE plugins) is just a client. FlupCode reuses
that engine untouched and focuses entirely on the experience layer — the shell, the design
system and the harness features that OpenCode's default UI does not emphasise.
- Engine untouched. All OpenCode packages stay pristine so upstream changes can be pulled in.
- Isolated product code. Everything we build lives in
packages/harness(web) andpackages/harness-desktop(desktop), reusing@opencode-ai/ui,@opencode-ai/session-uiand the generated client/SDK. - Upstream-first.
devis a fast-forward mirror ofanomalyco/opencode; our work lives onpower. See docs/UPSTREAM.md. - Full TUI parity. Feature-for-feature mapping of the terminal UI to the web UI is tracked in docs/PARITY.md.
- Harness features. Usage dashboard, activity heatmap, multi-project workspaces, pinned items, artifacts and routines — see docs/ROADMAP.md.
- Runs that outlive the window. A harness server of its own keeps runs, tasks, routines and
artifacts: workflows written down as editable files and launched with
/feature …, checks the harness runs itself with the evidence kept, bounded retries when one fails, and human gates that hold a run until you let it through — see docs/USAGE.md. - Remote control. Drive your computer's sessions from your phone on any network, like Claude
Code's remote control: pair with a QR code, follow and start sessions, answer permission requests.
Traffic is end-to-end encrypted through a relay that cannot read it. Host it from the desktop app
or from a terminal with
flupcode remote— see docs/USAGE.md and ADR-0010.
v1.15.0. The web harness (Claude Code–style shell, TUI parity, dashboard, i18n), the Electron
desktop app and remote control (relay at relay.flupcode.com, phone view, flupcode remote) are
released, along with the harness server that owns runs: tasks, routines with history, verification
with evidence, workflows with human gates, and artifacts — now including the documents the agent
generates (kept in .flupcode/artifacts with the artifact_write tool, listed under Artifacts and
read by type: markdown, HTML, image, PDF). Editors for routines, agents and skills open in dialogs,
and Compare runs inside the chat layout. The upstream sync and release pipelines are in place.
Desktop builds are not yet signed by Apple or Microsoft (see Install). See
docs/ROADMAP.md for the live status.
packages/harness # FlupCode web app (SolidJS + Vite) — our product code
packages/harness-desktop # Electron desktop app (also hosts remote control)
packages/remote # remote control protocol and host (shared by desktop, CLI, web)
packages/relay # remote control relay server (Bun, deployed on Fly.io)
packages/flupcode-cli # the `flupcode` command (`flupcode remote`)
packages/landing # flupcode.com static site
packages/app # upstream OpenCode web app (pristine, reused for parts)
packages/tui # upstream terminal UI (pristine)
packages/ui # upstream shared UI primitives (reused)
packages/session-ui # upstream session/message rendering (reused)
packages/core | server | sdk # upstream engine (pristine)
docs/ # project documentation (this fork)
Install the engine first. FlupCode does not ship OpenCode. Get the OpenCode CLI so the desktop app can start it for you, or run it yourself:
env -u OPENCODE_SERVER_PASSWORD opencode serve --port 4096 # desktop env -u OPENCODE_SERVER_PASSWORD opencode serve --port 4096 --cors https://app.flupcode.com # hosted web app
Download the desktop app and the flupcode CLI from the
latest release:
| Platform | Desktop app | CLI |
|---|---|---|
| macOS (Apple Silicon) | FlupCode-mac-arm64.dmg |
flupcode-darwin-arm64 |
| macOS (Intel) | FlupCode-mac-x64.dmg |
flupcode-darwin-x64 |
| Windows | FlupCode-win-x64.exe |
flupcode-windows-x64.exe |
| Linux | FlupCode-linux-x64.AppImage, FlupCode-linux-x64.deb, FlupCode-linux-x64.rpm |
flupcode-linux-x64, flupcode-linux-arm64 |
The builds are not signed yet, so macOS shows "FlupCode Not Opened" / "No se ha abierto
FlupCode" and Windows shows SmartScreen. On macOS, click Done, then open System Settings →
Privacy & Security and click Open Anyway — or run
xattr -dr com.apple.quarantine /Applications/FlupCode.app. Details in
docs/USAGE.md.
Requirements: Bun 1.3+.
bun install
bun run dev:harness # start the FlupCode web app
bun run dev:web # start the upstream web app (reference)
bun run dev:desktop # start the upstream desktop app (reference)Corporate registry note. If your global
~/.npmrcpoints at a private registry, force the public registry for installs:npm_config_registry="https://registry.npmjs.org/" bun install --frozen-lockfile
Use the hosted UI at app.flupcode.com — it connects to an engine on your machine. First install the OpenCode CLI (see opencode.ai/docs for your platform), then start it with CORS enabled for the hosted origin:
env -u OPENCODE_SERVER_PASSWORD opencode serve --port 4096 --cors https://app.flupcode.com--cors is required because the page and the engine are different origins; the app connects to
http://localhost:4096 by default (change it in Settings → Server). env -u OPENCODE_SERVER_PASSWORD keeps that variable out of the engine's environment, so a shell that
exports it does not make the engine demand credentials a browser page cannot send.
The published OpenCode CLI tracks upstream and does not include FlupCode's core patches (GitHub Copilot OAuth in the v2 catalog, session permission modes). To get those, run the engine from this fork's source instead:
bun install env -u OPENCODE_SERVER_PASSWORD OPENCODE_DISABLE_CHANNEL_DB=1 bun run --cwd packages/opencode src/index.ts serve \ --port 4096 --cors https://app.flupcode.com
| Document | Purpose |
|---|---|
| docs/GETTING-STARTED.md | First run: install the engine per platform, start it and fix a blocked connection |
| docs/ARCHITECTURE.md | How the monorepo fits together and where FlupCode lives |
| docs/USAGE.md | Install, run, keyboard shortcuts and troubleshooting |
| docs/UPSTREAM.md | Branch model, syncing with anomalyco/opencode |
| docs/DESIGN.md | Design system and the Claude Code–style harness direction |
| docs/PARITY.md | TUI ↔ Web feature parity matrix |
| docs/ROADMAP.md | Prioritised, ticket-based roadmap |
| docs/COMMUNITY-FEATURES.md | Community-requested OpenCode features prioritised for FlupCode |
| docs/RELEASE.md | Versioning and release process |
| docs/CONTRIBUTING.md | Language, conventions, workflow |
| docs/adr/ | Architecture Decision Records |
| docs/tickets/ | Per-phase ticket breakdowns |
MIT, inherited from OpenCode. See LICENSE. Upstream copyright and attribution are preserved.