lcode-cli 0.18.0__tar.gz → 0.19.0__tar.gz

{lcode_cli-0.18.0 → lcode_cli-0.19.0}/CHANGELOG.md

@@ -6,6 +6,22 @@ All notable changes to lcode are documented here. The format follows
 
 ## [Unreleased]
 
+## [0.19.0] - 2026-10-06
+
+### Added
+
+- `lcode acp`: lcode inside editors that speak the Agent Client Protocol (Zed, JetBrains IDEs,
+  Neovim, Emacs and others). The editor shows the answers and thinking as they stream, each tool
+  call with the files it touches and a diff for edits, and asks permission questions and plan
+  approvals in its own dialog. lcode's permission modes are the session's modes, the todo list is
+  the editor's plan, and saved sessions reopen with their conversation. The model reads the
+  editor's buffers (unsaved changes included) and edits through them, and MCP servers the editor
+  passes join lcode's own. See [Editors](https://nasser1941.github.io/lcode/editors/) for setup.
+
+### Fixed
+
+- Cancelling a request whose answer was cut off mid-stream no longer ends it as if it were done.
+
 ## [0.18.0] - 2026-10-06
 
 ### Added
@@ -434,7 +450,8 @@ First public release.
 - `AGENTS.md` project instructions and `/init` to generate them.
 - One-line installer for Linux and macOS.
 
-[Unreleased]: https://github.com/nasser1941/lcode/compare/v0.18.0...HEAD
+[Unreleased]: https://github.com/nasser1941/lcode/compare/v0.19.0...HEAD
+[0.19.0]: https://github.com/nasser1941/lcode/compare/v0.18.0...v0.19.0
 [0.18.0]: https://github.com/nasser1941/lcode/compare/v0.17.0...v0.18.0
 [0.17.0]: https://github.com/nasser1941/lcode/compare/v0.16.0...v0.17.0
 [0.16.0]: https://github.com/nasser1941/lcode/compare/v0.15.0...v0.16.0

{lcode_cli-0.18.0 → lcode_cli-0.19.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: lcode-cli
-Version: 0.18.0
+Version: 0.19.0
 Summary: A local-first terminal coding agent powered by open-weight models on your own GPU or Mac, via Ollama.
 Project-URL: Homepage, https://nasser1941.github.io/lcode/
 Project-URL: Documentation, https://nasser1941.github.io/lcode/
@@ -104,6 +104,8 @@ through [Ollama](https://ollama.com), and when it needs current information it c
 - **Git workflow.** `/commit` writes messages in your repository's style, `/review` checks the
   changes with `file:line` findings, `/pr` opens the pull request, each after you approve it, and
   `lcode --worktree` runs parallel sessions on one repository.
+- **In your editor.** Zed, JetBrains IDEs, Neovim and other editors that speak the Agent Client
+  Protocol run lcode with `lcode acp`, with diffs and approvals in the editor.
 - **Automation.** `lcode -p --output json` for scripts and CI, a Python API (`from lcode import
   Session`), and a GitHub Action that answers `@lcode` in issues and pull requests on your own
   self-hosted runner.
@@ -214,7 +216,6 @@ fills up. Details: [How it works](https://nasser1941.github.io/lcode/how-it-work
 
 See the pinned [Roadmap issue](https://github.com/nasser1941/lcode/issues/10). Next up:
 
-- [Editor integration through the Agent Client Protocol](https://github.com/nasser1941/lcode/issues/49)
 - [Long-running work: finish notifications and background commands](https://github.com/nasser1941/lcode/issues/51)
 - More models in the catalog, and test reports from your hardware ([report one](https://github.com/nasser1941/lcode/issues/new?template=model_request.yml))
 

{lcode_cli-0.18.0 → lcode_cli-0.19.0}/README.md

@@ -68,6 +68,8 @@ through [Ollama](https://ollama.com), and when it needs current information it c
 - **Git workflow.** `/commit` writes messages in your repository's style, `/review` checks the
   changes with `file:line` findings, `/pr` opens the pull request, each after you approve it, and
   `lcode --worktree` runs parallel sessions on one repository.
+- **In your editor.** Zed, JetBrains IDEs, Neovim and other editors that speak the Agent Client
+  Protocol run lcode with `lcode acp`, with diffs and approvals in the editor.
 - **Automation.** `lcode -p --output json` for scripts and CI, a Python API (`from lcode import
   Session`), and a GitHub Action that answers `@lcode` in issues and pull requests on your own
   self-hosted runner.
@@ -178,7 +180,6 @@ fills up. Details: [How it works](https://nasser1941.github.io/lcode/how-it-work
 
 See the pinned [Roadmap issue](https://github.com/nasser1941/lcode/issues/10). Next up:
 
-- [Editor integration through the Agent Client Protocol](https://github.com/nasser1941/lcode/issues/49)
 - [Long-running work: finish notifications and background commands](https://github.com/nasser1941/lcode/issues/51)
 - More models in the catalog, and test reports from your hardware ([report one](https://github.com/nasser1941/lcode/issues/new?template=model_request.yml))
 

lcode_cli-0.19.0/docs/editors.md

@@ -0,0 +1,85 @@
+# Editors
+
+lcode also works inside editors that support the
+[Agent Client Protocol](https://agentclientprotocol.com) (ACP), such as Zed, JetBrains IDEs,
+Neovim and Emacs. The editor starts `lcode acp` and shows lcode's work in its own UI: answers,
+tool calls, a diff for each edit, and permission questions.
+
+## Zed
+
+Add lcode to Zed's `settings.json`:
+
+```json
+{
+  "agent_servers": {
+    "lcode": {
+      "type": "custom",
+      "command": "lcode",
+      "args": ["acp"],
+      "env": {}
+    }
+  }
+}
+```
+
+Then open the Agent Panel and start a new thread with **lcode** from the new-thread menu.
+
+- **Zed can't start lcode:** use the full path in `command`, from `which lcode` (usually
+  `~/.local/bin/lcode`). An editor started from the desktop may not see your shell's `PATH`.
+- **Something goes wrong:** run **dev: open acp logs** in Zed's command palette to see the
+  messages lcode and Zed exchange.
+
+## JetBrains IDEs
+
+Add lcode to `~/.jetbrains/acp.json`, with the full path from `which lcode`:
+
+```json
+{
+  "agent_servers": {
+    "lcode": {
+      "command": "/home/you/.local/bin/lcode",
+      "args": ["acp"]
+    }
+  }
+}
+```
+
+Then pick lcode in the AI Chat tool window.
+
+## Other editors
+
+Any [ACP client](https://agentclientprotocol.com/overview/clients) works the same way: tell it
+to run `lcode acp`. That includes Neovim (CodeCompanion, avante.nvim), Emacs (agent-shell),
+VS Code extensions and more.
+
+## What the editor shows
+
+| In the editor | From lcode |
+|---|---|
+| The conversation | lcode's answers and its thinking, as they stream |
+| Tool calls | Each tool call, with its kind (read, search, edit, run, fetch) and the files it touches |
+| Edits | A diff of the whole file for each edit |
+| Open files | Edits go through the editor, so open files update right away. The model reads what's in the editor, unsaved changes included |
+| Permission questions | **Allow**, **Always allow** (for this session) or **Reject**, in the editor's own dialog |
+| Modes | lcode's [permission modes](usage.md#permissions): Ask, Auto-edit, Plan and Yolo |
+| Plans | In Plan mode, the plan is approved in the editor, which then switches to Ask or Auto-edit |
+| The plan list | The model's todo list |
+| Context | How much of the context window is in use |
+| Commands | `/review` and [your own commands](commands.md) |
+| Past threads | lcode's saved sessions: an editor that reopens a thread gets its conversation back |
+
+[Checkpoints](usage.md#undo-and-checkpoints), [hooks and permission rules](hooks.md),
+[memory](memory.md), [subagents](agents.md) and [MCP servers](mcp.md) work as in the terminal.
+MCP servers the editor passes to its agents are added to lcode's own.
+
+## Settings
+
+lcode uses your [configuration](configuration.md): the model, the context window, the
+[model server](servers.md) and the default permission mode. To use different settings in an
+editor, set them in the agent's `env`, for example `"env": {"LCODE_MODEL": "qwen3.5-9b"}`.
+
+A repository's own commands, skills, agents and hooks are used only after you
+[approve them](commands.md#approving-a-repositorys-commands-skills-and-agents). An editor can't
+ask, so run `lcode` in the repository once and approve them there.
+
+To see lcode's own output while it runs in an editor, set `LCODE_ACP_LOG` to a file in `env`.

{lcode_cli-0.18.0 → lcode_cli-0.19.0}/docs/quickstart.md

@@ -12,7 +12,7 @@ lcode
 
 ```text
 ╭──────────────────────────────────────────────╮
-│ lcode v0.18.0 — local coding agent           │
+│ lcode v0.19.0 — local coding agent           │
 │                                              │
 │ model    lcode-qwen3.6-35b                   │
 │ context  256K tokens                         │

{lcode_cli-0.18.0 → lcode_cli-0.19.0}/docs/usage.md

@@ -10,6 +10,7 @@ lcode doctor                 # check the installation (include this in bug repor
 lcode config [set|unset]     # show or change settings
 lcode bench [models]         # score models on small coding tasks on this machine
 lcode mcp [catalog|add|list] # connect MCP servers: Jira, GitHub, AWS, databases… (see MCP servers)
+lcode acp                    # run inside an editor over the Agent Client Protocol (see Editors)
 ```
 
 | Option | Meaning |

{lcode_cli-0.18.0 → lcode_cli-0.19.0}/mkdocs.yml

@@ -97,6 +97,7 @@ nav:
       - Commands and skills: commands.md
       - Git workflow: git.md
       - Automation: automation.md
+      - Editors: editors.md
       - Code intelligence: lsp.md
       - Repository map and code search: search.md
       - Models & context windows: models.md

{lcode_cli-0.18.0 → lcode_cli-0.19.0}/pyproject.toml

@@ -86,6 +86,7 @@ ignore = [
 "src/lcode/backends.py" = ["E501"]
 "src/lcode/gitflow.py" = ["E501"]
 "src/lcode/action.py" = ["E501"]
+"src/lcode/acp.py" = ["E501"]
 
 [tool.pytest.ini_options]
 testpaths = ["tests"]

{lcode_cli-0.18.0 → lcode_cli-0.19.0}/src/lcode/__init__.py

@@ -3,7 +3,7 @@
 From a program: `from lcode import Session` (see lcode.api).
 """
 
-__version__ = "0.18.0"
+__version__ = "0.19.0"
 
 API = ("Session", "Result", "Options", "SetupError")