From 3c499e9295803a9b6b6e83352a2f8fd89d10941c Mon Sep 17 00:00:00 2001 From: Ollie Agent Date: Sun, 16 Aug 2026 20:25:06 +0200 Subject: [PATCH] Clarify editor integration message --- doc/architecture-ide.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/doc/architecture-ide.md b/doc/architecture-ide.md index 2dfa5c5..2f742b8 100644 --- a/doc/architecture-ide.md +++ b/doc/architecture-ide.md @@ -203,7 +203,12 @@ For an editor with a plugin API, use its native document and selection APIs, the The editor can use any language or integration mechanism. The only Ollie-specific dependency is the 9P namespace documented in [`architecture-9p.md`](architecture-9p.md). The agent, tools, prompt assembly, backend selection, and persistent state remain in Ollie rather than in the editor integration. +## The point is integration -Use Acme when you want small, inspectable shell commands that fit naturally into tags, pipes, and the Acme 9P namespace. Use Kate when you want persistent project selection, native context menus, diff review, syntax-aware completion, and a GUI workflow. +Acme and Kate are examples, not competing Ollie workflows. Acme serves a particularly specialized audience that prefers small, inspectable commands woven directly into the editor’s tag and 9P model. Kate serves people who prefer a powerful, full-featured editor that may already be part of their desktop environment. Neither audience needs a new Ollie interface. -Both integrations remain thin clients. They do not duplicate session state, prompt assembly, tool execution, or backend configuration. See [`architecture-9p.md`](architecture-9p.md) for the namespace and [`architecture-kde.md`](architecture-kde.md) for the KDE build and plugin layout. +The important fact is that both tools already integrate with Ollie. The same is true of other editors, IDEs, shells, desktop environments, and local automation. If a tool can obtain a file, selection, cursor, project, or diff and can run a command or speak 9P, it can add Ollie capabilities without embedding the agent runtime. + +The integration can be tiny or polished, manual or automated, quiet or highly interactive. It can use a shell script, a native plugin, a key binding, a context-menu action, an editor command, or a background observer. All of these are clients of the same Ollie namespace. + +Both Acme and Kate remain thin clients. They do not duplicate session state, prompt assembly, tool execution, or backend configuration. See [`architecture-9p.md`](architecture-9p.md) for the namespace and [`architecture-kde.md`](architecture-kde.md) for the KDE build and plugin layout.