lkn
/
ollie
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Clarify Kate chat ownership

This commit is contained in:
Ollie Agent 2026-08-18 12:22:23 +02:00
parent baf75702d1
commit fc6b9afd47
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/architecture-ide.md
View File

@ -145,7 +145,7 @@ Its context-menu actions are concrete examples:
Kate also provides an optional one-shot completion path. It sends a bounded prefix and suffix around the cursor to the root `generate` operation and displays the returned code as ghost text. This is separate from the project agent’s prompt stream.
The Kate implementation is a native plugin, but the integration boundary is unchanged: obtain editor context, write a 9P prompt, and interact with the agent through the KDE GUI by selecting the corresponding Kate session and using its chat stream. Other editors and IDEs can use shell commands, plugins, key bindings, or automation APIs with the same operations.
The Kate implementation is a native plugin, but the integration boundary is unchanged: obtain editor context and write a 9P prompt. The plugin does not provide an integrated chat or prompt window; select the corresponding Kate session in the KDE GUI and use its chat stream to interact with the agent.
## Summary
@ -155,6 +155,6 @@ An editor integration is a 9P client:
editor context → agent/.../prompt → Ollie agent → files/chat/state
```
Read context from the editor, select an agent for the project, construct a prompt, and write it to `prompt`. For Kate, select the corresponding session in the KDE GUI and use its chat stream to interact with the agent. Other integrations can observe the agent with `o`, `ollie-9p`, `ollie-gui`, or a terminal.
Read context from the editor, select an agent for the project, construct a prompt, and write it to `prompt`. The Kate plugin does not provide an integrated chat or prompt window; select the corresponding Kate session in the KDE GUI and use its chat stream to interact with the agent. The KDE GUI and TUI are the agent interaction surfaces.
A shell command is sufficient when the editor exposes the needed context and command execution. Otherwise, use its extension or plugin mechanism. Vim, Emacs, Acme, Kate, and other editors can use the same pattern through whatever integration mechanism they provide. The editor need only provide context and a way to issue a 9P request.