Step 1 of M3.5: the shared mechanism. M3.4 and M3.5 build on it. - Engine: `Outcome.pending: Option<Pending>`. `Pending::new(rx, timeout, finish)`; `Pending::wait()` is called without the engine lock and returns at the answer, a dropped sender or the deadline (timeout + 1 s). `Engine::resolve(answered)` then runs `finish(state, reply)` inside the guard, under the lock. `run_waiting(lock, cmd, params, publish)` does all three steps for hosts. - Hosts: `Host::run`, `testkit::EngineBackend` and the control test backend use `run_waiting`. - New IPC `engine_execute_waiting` (`#[tauri::command(async)]`, off the main thread) with `runWaiting()` in `ui/src/ipc.ts`. Only `lsp.*` requests use it. Ordering guarantee: - `engine_execute` stays synchronous on the main thread, so ordinary commands (`buffer.edit`) still run in call order. - The order towards the server is fixed under the engine lock: `buffer.edit` queues its didChange on the session's FIFO queue before it returns, and `lsp::submit` queues the request on the same queue. A request therefore sees every edit whose `buffer.edit` returned first, and the UI awaits the sync's `idle()` before sending one. Failures: - A stall is caught by the request timeout, with the deadline as backstop. - On restart, close, quit or crash the request is dropped or resolved as stopped, so the waiter gets an error, never a hang. Tests: `crates/engine/tests/pending.rs` (answer, lock free while waiting, dropped sender, deadline, resolve, lsp.restart while a request is pending) and Vitest for `runWaiting`. Gate: 13 steps, 321 s, Vitest 443 + 1 skipped. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|---|---|---|
| .cargo | ||
| .claude/agents | ||
| .github/workflows | ||
| apps | ||
| assets | ||
| contributors | ||
| crates | ||
| docs | ||
| ui | ||
| xtask | ||
| .gitattributes | ||
| .gitignore | ||
| AGENTS.md | ||
| ASSETS.md | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CLAUDE.md | ||
| clippy.toml | ||
| deny.toml | ||
| LICENSE-APACHE | ||
| LICENSE-MIT | ||
| NOTICE | ||
| README.md | ||
| ROADMAP.md | ||
Lutra
A fast, open-source, clean-room PHP IDE in the spirit of the PhpStorm workflow. Rust core, Vue interface, native on macOS, Windows and Linux.
Lutra is the Latin name of the otter. Sea otters are among the few animals that use tools: they crack shells open with a stone. Lutra is that stone for your PHP code.
Why Lutra
- Familiar. Project view, tool windows, Search Everywhere-style navigation, Go to Class, Find Usages, refactorings: the workflow PHP developers already know.
- Fast. A Rust core with an incremental index, search off the UI thread and a lightweight Tauri shell.
- Robust. No panics in shipped code, a crash-recovery journal for unsaved buffers, property-tested protocols.
- Open. MIT OR Apache-2.0, no account, no telemetry.
- Agent-native. Every action is a command that a JSON control channel and an MCP server expose, so Claude and other agents can work in the IDE the way a person does.
- PHP-first. Symfony, Laravel, Shopware and WordPress support are on the roadmap from the start.
Quick start
The foundation (M0) is built:
cargo xtask devopens an empty themed window andcargo xtask ciruns the quality gate. Thelutracommand below is the target of milestone M3.
git clone <repo-url> lutra
cd lutra
cargo xtask dev # desktop app in development mode
cargo xtask dev -- --control 7979 . # + JSON control channel
cargo xtask ci # fmt, clippy, tests, layers, assets, clean-room, frontend checks
The lutra command
Works today (M3.7): opening folders and files (at a line) in the running Lutra or starting it, and --wait. The rest arrives with M3 and later.
lutra . # open the current folder as a project
lutra src/Kernel.php:42 # open a file at a line
lutra diff a.php b.php # open the diff viewer
lutra --wait FILE # wait until the tab is closed (git config core.editor "lutra --wait")
lutra mcp # MCP server on stdio
lutra perf # check the performance budgets
Use it from Claude Code
claude mcp add lutra -- lutra mcp
Status
Pre-alpha (2026-10-17): M2 done. You can open a folder, browse it in the project tree with live updates from disk, and edit and save files in tabs with syntax highlighting for PHP (and HTML, CSS, JS/TS, JSON, YAML, Markdown), with every command in a palette (Mod+Shift+P) and settings and the light or dark theme in a settings dialog (Mod+,); unsaved text survives a crash and is offered back on the next open; M2 added find in files (Mod+Alt+F) and go to file, class or symbol (Mod+P, Mod+Alt+C, Mod+T); M3 has begun with an integrated terminal (Mod+Shift+T); PHP language features come next. About 12 agent hours remain to the MVP (M3: language server, terminal, CLI and MCP). ROADMAP.md has the stage and what's next,
docs/target-app-parity.md the parity assessment and docs/gaps.md the ranked work list.
First target (MVP, M1–M3): open a project, project tree, tabs, editor with highlighting, find in files,
go to definition, completion and diagnostics via a language server, command palette, integrated terminal,
the lutra CLI, light and dark themes.
Agent and contributor rules (clean-room, asset policy, no panics, quality gates) are in AGENTS.md.
Every bundled asset is listed with its licence in ASSETS.md.
License
Lutra is dual-licensed under MIT or Apache-2.0, at your option. Copyright (c) 2026 Daniel Diekert and the Lutra contributors. Required notices are in NOTICE.
PhpStorm, IntelliJ IDEA and JetBrains are trademarks or registered trademarks of JetBrains s.r.o. Lutra is an independent, open-source project and is not affiliated with, sponsored by or endorsed by JetBrains s.r.o.; these names are used only to describe the workflows it is compatible with.