[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-92465":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":16,"stars7d":16,"stars30d":17,"stars90d":16,"forks30d":16,"starsTrendScore":16,"compositeScore":18,"rankGlobal":10,"rankLanguage":10,"license":19,"archived":20,"fork":20,"defaultBranch":21,"hasWiki":20,"hasPages":20,"topics":22,"createdAt":10,"pushedAt":10,"updatedAt":43,"readmeContent":44,"aiSummary":45,"trendingCount":16,"starSnapshotCount":16,"syncStatus":13,"lastSyncTime":46,"discoverSource":47},92465,"limboo","BotCoder254\u002Flimboo","BotCoder254","An Orchestrate multiple coding agent desktop app ","",null,"TypeScript",65,2,3,6,0,7,42.13,"MIT License",false,"main",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"agent","ci-cd","claude-code","desktop-app","electron","forge-app","full-stack","gitlab","harness","javascript","nodejs","open-source","openai","reactjs","sdk","sqlite3","typesafe","typescript","vite","windows","2026-07-22 04:02:06","\u003Cdiv align=\"center\">\n\n\u003Cimg src=\"assets\u002Ficon.png\" width=\"120\" alt=\"Limboo logo\" \u002F>\n\n# Limboo\n\n**The operating system for AI software development.**\n\nA local-first desktop workspace that gives a connected coding agent everything it\nneeds to do real engineering: projects, sessions, file watching, repository\nindexing, git, terminals, memory, permissions, and context. Limboo is not an AI\nmodel. It is the environment around one.\n\n[Documentation](docs\u002FREADME.md) ·\n[Architecture](docs\u002Farchitecture\u002Foverview.md) ·\n[Contributing](CONTRIBUTING.md) ·\n[Roadmap](ROADMAP.md) ·\n[Security](SECURITY.md)\n\n\u003Cbr \u002F>\n\n\u003Cimg src=\"assets\u002Fscreenshots\u002F01-main-shell.png\" alt=\"Limboo — sessions, the conversation-first workspace, and the composer on the pure-black shell\" width=\"920\" \u002F>\n\n\u003C\u002Fdiv>\n\n---\n\n## What is Limboo?\n\nLimboo is a desktop application (Electron + React + TypeScript) that acts as the\nworkspace *around* a coding agent. The agent already understands programming,\ndebugging, planning, and git. Limboo provides the environment where it can perform\nat its highest level: it manages the repository, watches the filesystem, runs the\nterminal, owns the database, holds durable project memory, and enforces a strict\nsecurity boundary, while the agent focuses exclusively on writing software.\n\nEvery unit of work is a **Session** — a bundle of a repository, branch, chat\nhistory, agent, terminal history, checkpoints, permissions, context, memory, tasks,\nand generated files. Instead of opening many windows, everything lives inside one\nworkspace.\n\n## Why it exists\n\nTraditional IDEs revolve around files. Limboo revolves around conversations. You do\nnot ask \"which file should I edit?\" — you say \"implement authentication,\" and the\nagent figures out the files while Limboo visualizes the process: the streaming\nreply, the tool calls, the file changes, the git diff, and the running commands.\n\nIt is **local-first** by design. There is no backend and no cloud sync. The only\nnetwork traffic is the connected coding agent talking to its AI provider. The\nproject, its history, and its memory belong to the developer.\n\n## Key features\n\n- **Session-centric workspace** — repo + branch + chat + agent + terminal +\n  checkpoints + memory, all in one place.\n- **Coding agent orchestration** — drives the Claude Code agent (plan and implement\n  modes) with risk-gated tool approvals, path-guarded to the workspace.\n- **Deep git engine** — status, diff, stage, commit, log, branches, tags, blame,\n  fetch, push, pull, plus lightweight per-session **checkpoints** for instant\n  recovery.\n- **Integrated terminal** — workspace-scoped PTY sessions; agent commands are\n  mirrored into the terminal view.\n- **File System Layer** — live watch + indexed tree + guarded reads, pushing live\n  git status into the session list.\n- **Local Memory System** — durable, provider-independent project knowledge with\n  fully offline FTS5 \u002F BM25 retrieval, injected into the agent prompt.\n- **Resume Pipeline** — reopening a session revalidates the repository against the\n  state it last saw and hands the agent a structured **repository delta** (commits,\n  files, symbols, dependency manifests) so it continues against current reality, not\n  a stale transcript. Fully local, bounded git, never blocks switching.\n- **Unified streaming timeline** — one continuous, turn-grouped event stream of the\n  conversation, tool calls, and status.\n- **Pure-black, dark-only UI** — a minimal three-pane shell tuned for a true\n  `#000000` background.\n\n## What makes Limboo different\n\nMost agent tools stop at \"resume the conversation.\" That restores what the agent\n*said*, but not the world it said it in. Limboo treats the environment as a\nfirst-class, continuously-maintained system that cooperates with the agent instead\nof leaving it to rediscover reality on every turn.\n\n- **The agent resumes against verified repository reality, not a transcript.** The\n  **Resume Pipeline** is the flagship of this idea. When you reopen a session — after\n  an hour or after three weeks of other people's commits, rebases, and dependency\n  bumps — Limboo revalidates the git worktree against the exact state the session\n  last saw and computes a structured *repository delta*: commits landed, files\n  changed (with dependency manifests and migrations flagged), symbols added or\n  removed, and which files import what changed. That delta is injected once, before\n  your next prompt, so the agent reconciles its assumptions up front instead of\n  burning turns re-reading the tree. It is fully local, uses only bounded argv-only\n  git, and never blocks you from switching sessions. See\n  [the Resume Pipeline](docs\u002Farchitecture\u002Fsubsystems\u002Fresume-pipeline.md).\n\n- **Isolation by default.** Every session can own its own git worktree — a real\n  isolated checkout and branch — so parallel work never collides, and \"continue where\n  I left off\" means a specific filesystem, not a shared one.\n\n- **The app owns the knowledge, not the model.** Durable project memory, the search\n  index, and now a symbol\u002Fdependency graph are platform services the app maintains\n  and injects — provider-independent and offline. Memory even references repository\n  symbols, so guidance whose code was deleted is automatically demoted until it\n  reappears.\n\n- **A hard security boundary you can trust.** The renderer performs nothing: all\n  filesystem, git, shell, and database access lives in the main process behind a\n  single typed IPC bridge with sender validation, deny-by-default permissions, and\n  parameterized SQL throughout. Git never runs through a shell; paths are guarded\n  against traversal; secrets are never stored.\n\nThe result: continuation feels genuinely intelligent, because the agent begins each\nresumed task with an accurate, up-to-date understanding of a living codebase.\n\n## Screenshots\n\nA tour of the shell: sessions on the left, the conversation in the center, and\nthe activity rail on the right — every panel below is one click on the rail.\n\n| | |\n| --- | --- |\n| **Files** — the indexed workspace tree with per-language icons\u003Cbr \u002F>\u003Cimg src=\"assets\u002Fscreenshots\u002F02-files-panel.png\" alt=\"Files panel — indexed workspace tree\" \u002F> | **Changes** — live git status with per-file diff stats\u003Cbr \u002F>\u003Cimg src=\"assets\u002Fscreenshots\u002F03-changes-panel.png\" alt=\"Changes panel — live git status\" \u002F> |\n| **Git** — stage, commit, history, branches, and checkpoints\u003Cbr \u002F>\u003Cimg src=\"assets\u002Fscreenshots\u002F04-git-panel.png\" alt=\"Git panel — staging and commit\" \u002F> | **Memory** — durable project knowledge with tiered proposals\u003Cbr \u002F>\u003Cimg src=\"assets\u002Fscreenshots\u002F05-memory-panel.png\" alt=\"Memory panel — project knowledge\" \u002F> |\n| **Tasks** — the agent's live plan and progress\u003Cbr \u002F>\u003Cimg src=\"assets\u002Fscreenshots\u002F06-tasks-panel.png\" alt=\"Tasks panel — agent plan\" \u002F> | **Terminal** — workspace-scoped PTY sessions\u003Cbr \u002F>\u003Cimg src=\"assets\u002Fscreenshots\u002F07-terminal-panel.png\" alt=\"Terminal panel — integrated PTY\" \u002F> |\n| **Command palette** — every command behind \u003Ckbd>Ctrl\u002FCmd\u003C\u002Fkbd>+\u003Ckbd>K\u003C\u002Fkbd>\u003Cbr \u002F>\u003Cimg src=\"assets\u002Fscreenshots\u002F08-command-palette.png\" alt=\"Command palette overlay\" \u002F> | **Global search** — files, symbols, docs, memory, commits, sessions\u003Cbr \u002F>\u003Cimg src=\"assets\u002Fscreenshots\u002F09-global-search.png\" alt=\"Global search overlay\" \u002F> |\n\n**Settings** — general, appearance, agent, git, memory, and advanced JSON editing\nin one modal:\n\n\u003Cimg src=\"assets\u002Fscreenshots\u002F10-settings.png\" alt=\"Settings modal\" width=\"920\" \u002F>\n\n## Architecture at a glance\n\n```\n Renderer (Chromium + React)   UI only — it asks, it never performs\n        |  window.limboo.*\n        v\n Preload (contextBridge)        the only bridge; contextIsolation on, sandbox on\n        |  ipcRenderer \u003C-> ipcMain\n        v\n Main (Node.js + OS access)     workspaces, sessions, git, terminal, fs, agent,\n                                memory, SQLite — every OS-touching capability\n```\n\nLimboo runs three Electron contexts with a hard boundary between them. The renderer\nholds no business logic; all filesystem, git, shell, database, and agent work lives\nin the main process and crosses a single typed IPC bridge. See\n[docs\u002Farchitecture\u002Foverview.md](docs\u002Farchitecture\u002Foverview.md).\n\n## Tech stack\n\n| Layer            | Choice                                          |\n| ---------------- | ----------------------------------------------- |\n| Shell \u002F desktop  | Electron 42 (via Electron Forge 7)              |\n| Bundler          | Vite 5 (`@electron-forge\u002Fplugin-vite`)          |\n| UI framework     | React 19                                        |\n| Language         | TypeScript                                      |\n| Styling          | Tailwind CSS v4 (CSS-first, no config)          |\n| State            | Zustand 5 (slice-per-domain stores)             |\n| Database         | better-sqlite3 (WAL, FTS5)                       |\n| Terminal         | node-pty (Node-API) + xterm                     |\n| File watching    | chokidar                                        |\n| Coding agent     | `@anthropic-ai\u002Fclaude-agent-sdk`                |\n| Icons            | lucide-react                                    |\n\n## Quick start\n\n**Prerequisites**\n\n- Node.js 20+ and npm.\n- A C\u002FC++ build toolchain for `better-sqlite3` (build-essential \u002F Xcode Command\n  Line Tools \u002F MSVC Build Tools depending on platform) — it may compile on\n  install if no matching prebuilt is published. `node-pty` (pinned to the\n  Node-API `1.2.0-beta` line) ships an ABI-stable prebuilt and never compiles.\n- The coding agent owns its own authentication. Limboo never stores credentials;\n  it reads the agent's existing sign-in (for example `ANTHROPIC_API_KEY` or the\n  Claude Code credentials file). See\n  [docs\u002Fguides\u002Fusing-the-agent.md](docs\u002Fguides\u002Fusing-the-agent.md).\n\n**Run in development**\n\n```bash\nnpm install     # installs deps and compiles native modules\nnpm start       # Electron + Vite dev server (renderer on :5173)\n```\n\nThere is no `npm run dev` — `npm start` drives both Electron and Vite. Full setup\nnotes live in [docs\u002Fgetting-started\u002Finstallation.md](docs\u002Fgetting-started\u002Finstallation.md).\n\n**Build installers**\n\n```bash\nnpm run package   # package the app (no installers)\nnpm run make      # platform installers (deb \u002F rpm \u002F zip \u002F squirrel)\n```\n\n## Documentation\n\nThe documentation is organized as a subsystem, not a single file. Start at the\n[documentation home](docs\u002FREADME.md):\n\n- **Getting started** — [installation](docs\u002Fgetting-started\u002Finstallation.md),\n  [quick start](docs\u002Fgetting-started\u002Fquick-start.md),\n  [configuration](docs\u002Fgetting-started\u002Fconfiguration.md).\n- **Concepts** — [sessions](docs\u002Fconcepts\u002Fsessions.md),\n  [workspaces](docs\u002Fconcepts\u002Fworkspaces.md),\n  [local-first](docs\u002Fconcepts\u002Flocal-first.md),\n  [conversation-first UI](docs\u002Fconcepts\u002Fconversation-first-ui.md).\n- **Guides** — [using the agent](docs\u002Fguides\u002Fusing-the-agent.md),\n  [git workflow](docs\u002Fguides\u002Fgit-workflow.md),\n  [memory system](docs\u002Fguides\u002Fmemory-system.md),\n  [terminal](docs\u002Fguides\u002Fterminal.md),\n  [keyboard shortcuts](docs\u002Fguides\u002Fkeyboard-shortcuts.md).\n- **Deep dives** — [the Resume Pipeline](docs\u002Farchitecture\u002Fsubsystems\u002Fresume-pipeline.md)\n  (\"continue exactly where you left off\") and the other\n  [subsystem docs](docs\u002Farchitecture\u002Fsubsystems\u002Fagent-manager.md).\n- **Reference** — [`window.limboo` API](docs\u002Freference\u002Fwindow-limboo-api.md),\n  [IPC channels](docs\u002Freference\u002Fipc-channels.md),\n  [settings](docs\u002Freference\u002Fsettings.md),\n  [design tokens](docs\u002Freference\u002Fdesign-tokens.md),\n  [commands](docs\u002Freference\u002Fcommands.md).\n- **Architecture** — [overview](docs\u002Farchitecture\u002Foverview.md) and per-subsystem\n  documentation under [docs\u002Farchitecture\u002F](docs\u002Farchitecture\u002Foverview.md).\n- **Operations** — release, CI\u002FCD, packaging, and maintenance under\n  [docs\u002Foperations\u002F](docs\u002Foperations\u002Frelease-process.md).\n\nTwo internal references predate this site and remain the deepest source of truth\nfor contributors: [`CLAUDE.md`](CLAUDE.md) (the code-level working contract) and\n[`project.md`](project.md) (the full product and architecture vision).\n\n## Project status\n\nLimboo is at `1.0.0`. The desktop foundation and platform services are built:\nworkspaces, sessions with per-session git worktrees, the git engine, the integrated\nterminal, the File System Layer, agent orchestration, the Local Memory System, the\nSearch Engine, the Resume Pipeline (\"continue exactly where you left off\"), and a\nhardened IPC layer over a local SQLite database. Planned work (repository clone\u002Ftrack\nUI, a standalone permission system, merge-conflict resolution, remote management,\nstash, and a tree-sitter \u002F vector-embeddings upgrade of the code-intelligence layer)\nis tracked in [ROADMAP.md](ROADMAP.md).\n\n## Contributing\n\nContributions are welcome. Read [CONTRIBUTING.md](CONTRIBUTING.md) for the\ndevelopment workflow, the process-boundary contract, theme discipline, and the\nverification steps every change must pass. Please also review the\n[Code of Conduct](CODE_OF_CONDUCT.md).\n\n## Security\n\nLimboo is local-first with a deliberately small attack surface and defense-in-depth\nhardening. To report a vulnerability, follow [SECURITY.md](SECURITY.md) — please do\nnot open a public issue for security reports.\n\n## License\n\nReleased under the [MIT License](LICENSE). Copyright (c) 2026 BotCoder254.\n","Limboo 是一款本地优先的桌面应用，为编程智能体（如 Claude Code）提供完整工程化工作环境。它以会话（Session）为核心，集成 Git 操作、文件系统监控、终端执行、本地持久化内存（SQLite FTS5\u002FBM25）、权限管控与上下文注入等功能，所有数据离线存储于本地，仅 AI 代理与外部模型通信。基于 Electron + React + TypeScript 构建，支持 Windows，强调安全边界与开发者对项目数据的完全控制。适用于需要高可信度、可审计、离线可用的 AI 辅助软件开发场景，尤其适合中大型代码库的增量式协作开发与调试任务。","2026-07-09 02:30:05","CREATED_QUERY"]