Tool Open source · GPL-3.0
Pake is an open-source tool for turning webpages or local web build output into desktop applications for macOS, Windows, and Linux. Its CLI packages a URL or local directory into a native app using Rust and Tauri, with options for application names, icons, window dimensions, title-bar behavior, styles, shortcuts, drag and drop, and ad removal; it also offers online building and ready-made application packages.
Pake is distributed under GPL-3.0. The repository states that generated applications can be used and distributed by their creators. CLI installation uses the `pake-cli` package, and local development requires Rust and Node.
Waku is a native desktop app for working with local coding agents. Built in Rust with GPUI, it keeps projects, sessions, transcripts, and application state on the user's machine, while detecting supported agent CLIs and using each provider's native structured protocol and session continuity. Its interface supports independent project sessions, model and reasoning settings, queued or directed follow-up messages, and Git-backed task rewind with conversation-aware checkpoints. The desktop app communicates with a standalone waku-daemon over an authenticated, versioned WebSocket protocol. The daemon manages task data in SQLite, attachments, provider-native session forks, workspace files, and Git operations; a browser client uses the same generated protocol. Waku is distributed for macOS, Linux, and Windows, with no Waku account or remote service required.
PI-Desktop is a local-first desktop workspace for AI coding agents, built with Electron, a Rust host core, and the pi Agent Harness. It lets users open local projects, connect cloud or local models through providers such as OpenAI-compatible APIs, manage projects and long-running sessions, and review file changes and command output. Its architecture separates the React renderer, Electron desktop orchestration, Rust-managed permissions, filesystem access, SQLite persistence and secrets, and a pi Agent sidecar responsible for the agent loop, model interaction, and streaming. Agent, Plan, and Goal modes provide different approval boundaries; agents can read and edit files, run commands, and delegate exploration, implementation, research, testing, or review to background Subagents. The workspace supports MCP servers, Skills, installable Plugins, model and provider switching, session imports, notifications, context checkpoints, and a plugin marketplace. Conversations are stored locally as JSONL with a SQLite index, settings and logs remain on the machine, credentials use the operating-system keychain, and model requests go directly to the configured provider or endpoint. Plugin processes are permission-gated and isolated from the renderer, but plugins remain user-trusted code rather than a complete operating-system sandbox. It is an early-preview cross-platform application distributed for macOS, Windows, and Linux under the GNU Lesser General Public License v3.0.
Apache Maka (Incubating) is a local-first agent workspace developed under the Apache Software Foundation. It inspects projects and runs tools through a shared Runtime Host within a sandbox boundary; tools that leave the sandbox require approval. Model messages, tool calls, tool results, and how a turn ended are stored as recoverable execution facts on the user's machine, while older tool output can be omitted from later prompts without deleting the saved history. Model connections can use cloud APIs, local models, or compatible gateways, with sessions, settings, and run records kept local by default. Maka provides an Electron and React desktop application with streaming sessions, tool timelines, branching, search, recovery, artifacts, and model and sandbox settings. Its TUI/CLI supports work in a project directory and non-interactive turns, while its evaluation surface runs declarative multi-arm experiments across Maka and external subjects. Built-in tools include Read, Write, Edit, Bash, Glob, and Grep; Computer Use and catalog skills are optional. The project is under active development and Apache incubation; the README describes the macOS Apple Silicon desktop build as an early public release and notes that data formats, CLI commands, and experimental capabilities may change.
Mr. Mak Workspace is a local Windows desktop workspace for Codex CLI and Claude Code CLI. It combines real CLI chats with a project workspace for folders, research, images, files, Markdown documents, project reports, and saved project materials. The application provides chat history and tabs, agent activity indicators, file and folder insertion, project cards, previews for media files, and a right rail for project skills, knowledge, workflows, MCP connections, settings, and help. The repository includes fourteen project skills covering areas such as planning, handoffs, image references, media generation, Three.js, Blender, video inspection, and dictation. It can also provide an optional voice coordinator using Codex CLI and an OpenAI API key; external providers and MCP connections are optional and use the user's own accounts. The Windows installer includes the local Node service but does not bundle the supported CLIs or provider accounts. The native application targets Windows x64, while browser report previews can run elsewhere. Application code and original workflow documentation are MIT-licensed, with third-party skill materials retaining their original licenses.
Paseo is a self-hosted platform for orchestrating multiple coding agents, including Claude Code, Codex, GitHub Copilot, OpenCode, and Pi. Its local daemon manages agent processes on users' machines, while desktop, mobile, web, and CLI clients connect to run agents in parallel, stream output, send follow-up tasks, and work in specified directories or worktrees. Paseo supports voice task dictation and control, agent handoffs, advisor and committee workflows, local tools, configurations, skills, and development environments, and provides an MCP server, WebSocket API, and TypeScript SDK for integrations, dashboards, and orchestration services. Remote connections use an end-to-end encrypted relay, TCP, Tailscale, or another VPN. Paseo can run as an installed application, headlessly, or as a Dockerized daemon with a self-hosted web UI. The repository is licensed under Apache-2.0 and states that Paseo has no telemetry, tracking, or forced log-ins.