Who it is forA developer who wants a coding agent to edit a real repository while keeping plans, commands, and file changes visible in one window.
The problemCoding agents often run in separate terminals, so it is hard to see their plans, permission requests, and file edits in one place.
The outcomeA coding session bound to a project folder, with plans, tool steps, permission requests, and file changes shown in the workspace and kept after an app restart.
What you need first
- Git with submodule support
- Node.js and npm
- A current Rust toolchain
- Tauri 2 system dependencies for your platform (see https://v2.tauri.app/start/prerequisites/)
- An accessible OpenAI-compatible model endpoint, such as local vLLM
Steps
git clone --recursive https://github.com/Pinvou/pinvou-agent.gitcd pinvou-agent/pinvou3-appnpm cicd .../pinvou3-app/run-dev.sh
Prompt for your agent
Using the Pinvou/pinvou-agent repo, start the desktop app with run-dev.sh, open Code mode, and attach the project at <project-path> to a Codex or Claude Code session over ACP. Expected output: a session bound to that folder that shows a plan and at least one file change. Verify that the session still appears after restarting the app.
Caveat. The README names Codex, Claude Code, and Kimi as ACP agents but does not say how to install or sign in to them, so you must set those up separately.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page