Model or dataset
openyak/openyak avatar
openyak/openyak

OpenYak puts Codex and Claude Code in one local window, and main has already moved past its own release tags

One chat. Every agent. A universal interface for AI agents running on your computer.

696 stars60 forksTypeScriptApache-2.0

At a glance

What is it?
An Electron and React desktop shell over a Rust and SQLite core, driving Codex through its App Server and Claude Code through the Agent SDK, with local transcripts and a shared browser. The build on main reports 2.0.0-alpha.0 while the newest release tags still sit in the v1 line.
Who is it for?
Judge this project on the two things it already does: one local workspace holding both agent runtimes with real file tabs, and a shared browser whose control handoff is written down as blocking behaviour rather than best effort. Everything else on its own list is labelled alpha, installers and Linux or Windows GUI validation are unfinished, and installing by tag gives you the v1 line rather than the code on main.
Can I use it commercially?
Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 78 days ago.
What is it written in?
Mainly TypeScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 21, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • openyak/openyak696 ★ · -12
Star history
Repository2026-09-102026-11-21
openyak/openyak708696

-12 Stars in the last 72 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

main reports 2.0.0-alpha.0 while the newest tag is still v1.5.0-rc.3

The version numbers inside this repository do not line up. package.json declares version 2.0.0-alpha.0, and the opening note says this is v2, on main, and still alpha, with the original v1 preserved on the legacy/v1 branch and in the v1.5.0 release. The three most recent releases attached to the repository are v1.5.0-rc.3 and v1.5.0-rc.2, both dated 2026-08-05, and v1.4.0 dated 2026-07-24. A reader who installs by tag therefore lands in the v1 line, while anyone who clones main gets an untagged alpha whose package version has already moved to 2.0.0-alpha.0. The release names are more descriptive than the tags themselves: v1.5.0-rc.3 is labelled Focused Computer & Browser Workspaces, and v1.5.0-rc.2 Native Computer Use & Managed Browser. Nothing in the visible text maps the v2 tree back onto a release.

One npm workspace, one cargo crate, and a check chain that stops at the first Rust failure

The root package.json declares workspaces as app only. core/ is not an npm workspace, it is a Rust crate reached through cargo, and every top level script reaches it first. build:core runs cargo build --release --manifest-path core/Cargo.toml, and both dev and build prepend that command, so any JavaScript start compiles the Rust core before Electron appears. The contributor entry points run the same chain:

bash
npm run check
npm run build

Underneath, check is three stages in a single line: cargo test --manifest-path core/Cargo.toml && npm run test -w app && npm run check -w app. Because the Rust tests come first, a failing core test ends the run before one TypeScript check executes. Under allowScripts there is exactly one entry, [email protected] set to true, so postinstall approval is granted to that pinned Electron release and to nothing else. The root package is marked private, and the pinned toolchains live in mise.toml rather than in any documented per-OS installer.

OPENYAK_AGENT_TRANSPORT=acp trades away the shared browser

Four environment variables change how the app finds or talks to an agent. OPENYAK_CODEX_BIN and OPENYAK_CLAUDE_BIN select compatible local CLI binaries when the default resolution is wrong. OPENYAK_DATA_DIR points the whole app at a new, empty directory for an isolated test instance, which is the cheapest way to keep a scratch run away from real transcripts. OPENYAK_AGENT_TRANSPORT=acp opts into the ACP path, and that switch has a stated cost: native host integrations such as the shared browser are not automatically available on it. On the default path Codex runs through its App Server over stdio and Claude Code through the Claude Agent SDK driving its own CLI, with ACP appearing in the provider table only as an optional compatibility path. Agent dependencies are pinned inside the app, and authentication stays with the account you already hold.

Taking control of the shared page blocks new agent actions and waits for work in flight

The shared browser runs on Playwright MCP and a dedicated Chrome session, and the agent and the user operate the same page. The handoff is defined rather than best effort: taking control blocks new agent browser actions and waits for in-flight work, and resuming returns browser access without sending another chat prompt. What you see is described as lossless HiDPI frames, a shared remote view that is not an embedded native browser and explicitly not a promise of 60 fps. The README narrows its own screenshot too: the pictured flow was exercised through Codex in the real GUI, and external computer-use tools and native desktop control are separate capabilities that the image does not certify. None of this is reachable without Google Chrome installed next to the Node 26 and Rust 1.90 toolchains.

Local SQLite storage is not offline inference

Storage is local, and that is the full extent of the claim. The layout puts chat, file workbench, native workers and host integrations in app/ as Electron and React, and projects, tasks, transcripts and normalized runtime events in core/ as Rust with SQLite. That split does not make the application offline, because provider requests and browser navigation can still use the network. Model availability, usage limits and provider features depend on your account and on the installed runtime versions, and OpenYak states plainly that it does not supply model access. Switching providers inside a task replays conversation context rather than a provider's private internal state, which is why transcripts survive a switch but carry nothing the other runtime never said. Local first describes where bytes are kept, not whether a packet leaves the machine.

The Orbit project in the screenshots is demo data, and the dashboard is hand authored

The two pictures on the front page carry their own disclaimers, and reading them closely prevents a wrong impression of output quality. The demo conversation uses Orbit, a fictional project with isolated demo data, and Codex generated the report during the capture. The dashboard shown under the files section is a hand-authored fixture rendered by the real app, described as neither a generated screenshot nor a claim that the agent built it. What the images do document is the surrounding interface: persistent tabs for Markdown, HTML, PDF, DOCX and syntax highlighted code, light and dark appearance, resizable workbench panels, a macOS Dock icon and a menu bar shortcut. Beneath the surface, the runtime boundary normalizes supported structured artifact and file outputs so the frontend never has to guess tool names or turn arbitrary code blocks into artifacts, while ordinary file references resolve through a separate opening path.

The alpha boundary list names the work that is not done

Before planning around this project, the unfinished list is printed in the README itself under Alpha boundaries. Packaged installers, broader agent support and Linux or Windows GUI validation are still in progress. Runtime-reported subagents are not a complete workflow-orchestration UI. Claude integration exists, but the browser screenshots validate Codex rather than a Claude browser acceptance run. Private Desktop-only tools and full computer-use parity are not guaranteed. The note at the top adds that OpenYak integrates supported runtime interfaces and does not reproduce every private feature of Codex Desktop or Claude Desktop. Running it means working from source, since nothing installable is published:

bash
git clone https://github.com/openyak/openyak.git
cd openyak
npm install
npm run dev

That step builds the Rust core and launches Electron with hot reload. The v2 CI workflow checks runtime contracts, production builds and real desktop or browser regressions without paid model calls, and documentation-only changes skip the heavy checks. The last push on the repository is dated 2026-09-05.

Seven questions get handed to files outside the front page

A lot of the substance lives in files the front page only points at. docs/native-agent-runtime.md is linked twice, once for runtime architecture and once for how the binary environment variables work. docs/shared-browser.md covers the browser boundaries. docs/core-protocol.md covers the app and core contract. docs/images/README.md is a screenshot provenance and reproduction guide. docs/ci.md explains the workflow, brandkit/README.md holds the visual guidelines, and CONTRIBUTING.md carries the invitation to try a real task, switch agents and inspect the output. A Simplified Chinese version sits at README.zh-CN.md, and the project homepage is open-yak.com. The visible text stops at a single sentence of summary for each, so which runtime interfaces count as supported, what the protocol actually covers and how the desktop and browser regressions are exercised all stay in those files. The root also carries CONTEXT.md and CHANGELOG.md without a mention in the visible README.

Editorial conclusion

Judge this project on the two things it already does: one local workspace holding both agent runtimes with real file tabs, and a shared browser whose control handoff is written down as blocking behaviour rather than best effort. Everything else on its own list is labelled alpha, installers and Linux or Windows GUI validation are unfinished, and installing by tag gives you the v1 line rather than the code on main. Before committing, confirm you can install Node 26 and Rust 1.90, that a Codex or Claude Code sign-in already exists on the machine, and that Chrome is present if the shared browser matters to you.

Frequently asked questions

Which agent runtimes can OpenYak drive?

Codex runs natively through its App Server over stdio, and Claude Code runs through the Claude Agent SDK driving its own CLI. ACP is offered as an explicit compatibility path for both rather than as the default.

Does OpenYak supply model access?

No. Model availability, usage limits and provider features depend on your own account and the installed runtime versions, and the project states that it does not supply model access.

What happens to the shared browser on the ACP transport?

Setting OPENYAK_AGENT_TRANSPORT=acp opts into the compatibility path, and native host integrations such as the shared browser are not automatically available there.

Where does OpenYak keep conversations, and is it offline?

Projects, tasks and transcripts live locally in a Rust core backed by SQLite, next to an Electron and React app layer. That storage is local, but provider requests and browser navigation can still use the network.

Which version does the main branch actually run?

The package version on main is 2.0.0-alpha.0 and it is described as alpha v2, while the three most recent releases attached to the repository are v1.5.0-rc.3, v1.5.0-rc.2 and v1.4.0.

Official sources

  1. License: Apache-2.0
  2. openyak/openyak on GitHub
  3. Project website
  4. README
  5. Releases
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/openyak-openyak.svg)](https://hysenlabs.com/projects/openyak-openyak)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/openyak-openyak.svg)](https://hysenlabs.com/projects/openyak-openyak)

Was this useful?