jamminrebel/cdsr
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

cdsr: wire the omp harness into the IDE as a native agent panel over ACP

Browse Source 
Pin formulahendry.acp-client 0.2.0 (Open VSX, MIT, sha256-verified) and point
acp.agents at `omp acp`. OMP already ships an ACP v1 server, so no custom
extension and no marketplace exception were needed.

Verified in the running IDE: status bar `ACP: Oh My Pi`, session/list returns
real prior OMP sessions for the open folder, and a full prompt turn streams
text plus tool-call and plan cards.

Credentials never move: OMP authenticates from ~/.omp via its `agent` auth
method and the extension is given no key.
This commit is contained in:
Antigravity
2026-08-20 17:25:06 +02:00
parent c2d92d7b74
commit f52d7ba656
5 changed files with 58 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
q5vault/operations/verification.md
View File

@@ -76,8 +76,23 @@ Exit code: `0`
1. Open `https://cdsr.loca.zone` in a browser.
2. Complete Authelia one-factor login at `auth.loca.zone`.
3. Confirm code-server editor shell loads (activity bar, file explorer, terminals).
4. Open Extensions view (Ctrl+Shift+X): verify `Continue` and `Claude Code` are installed and enabled.
4. Open Extensions view (Ctrl+Shift+X): verify `Continue`, `Claude Code` and `ACP Client` are installed and enabled.
5. Open integrated terminal (Ctrl+`): run `whoami` -> output `loca`.
6. If the activity bar shows no third-party icons, the folder is in Restricted Mode: Command Palette → `Workspaces: Manage Workspace Trust` → Trust. Workspace Trust silently disables every third-party extension, which looks exactly like a failed install.
## 7b. OMP agent panel over ACP (manual)
Proves the `omp` harness is reachable as a native agent, end to end.
1. Activity bar → `ACP Client`. The `AGENTS` tree lists `Oh My Pi` alongside the extension's shipped defaults; only `Oh My Pi` is a pinned local binary.
2. Command Palette → `ACP: New Conversation` → pick `Oh My Pi`.
3. Status bar reads `ACP: Oh My Pi`. The chat header shows the open folder and OMP's own session controls: mode (Default/Plan), model, thinking level.
4. Send `Reply with exactly: IDE-ACP-OK`. Expect the reply text plus rendered tool-call and plan cards.
5. Agent-side check without the IDE, if the panel misbehaves:
```bash
printf '%s\n' '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":1,"clientCapabilities":{"fs":{"readTextFile":true,"writeTextFile":true}}}}' | omp acp
```
Expect one JSON line containing `"protocolVersion":1` and `"agentInfo":{"name":"oh-my-pi"`. If that works and the panel does not, the fault is the extension or `acp.agents`, not OMP.
## 8. dev-routing smoke (manual)