anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

[FEATURE]: plugin API for side-effect-free LLM calls #9486

New Issue
Open
opened 2026-02-16 18:12:33 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 18:12:33 -05:00
Owner
Copy Link
Copy Source

Originally created by @wakamex on GitHub (Feb 16, 2026).

Originally assigned to: @thdxr on GitHub.

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

When implementing a memory plugin, I noticed there’s no first-class way to make a plugin-internal LLM call that is side-effect-free (doesn’t pollute session history).

Current plugin SDK exposes hooks + ctx.client, but no dedicated internal LLM primitive. Plugins currently either maintain provider adapter logic themselves, or route through session endpoints and add guard/cleanup logic.

In my WIP plugin (https://github.com/wakamex/opencode-observational-memory), I currently use worker-session orchestration (session.create + session.prompt) with recursion/cleanup guards. In supermemory (https://github.com/supermemoryai/opencode-supermemory), similar framework constraints show up in a different form (session.summarize, session.promptAsync, and compaction context injection).

Request: add a plugin API like ctx.llm.generate(...) for internal calls with:

  • no transcript persistence by default
  • no normal chat/event hook recursion by default
  • OpenCode-native provider/model routing
  • optional per-call model override (for example, Observer model != chat model)

Related plugin API discussion: #10868 (this request is narrower and focused on internal LLM execution).

If this direction is approved, I can open a small PR for ctx.llm.generate first (text-only + isolated by default), with tests for no message persistence, no chat/event hook recursion, per-call model override.

Originally created by @wakamex on GitHub (Feb 16, 2026). Originally assigned to: @thdxr on GitHub. ### Feature hasn't been suggested before. - [x] I have verified this feature I'm about to request hasn't been suggested before. ### Describe the enhancement you want to request When implementing a memory plugin, I noticed there’s no first-class way to make a plugin-internal LLM call that is side-effect-free (doesn’t pollute session history). Current plugin SDK exposes hooks + `ctx.client`, but no dedicated internal LLM primitive. Plugins currently either maintain provider adapter logic themselves, or route through session endpoints and add guard/cleanup logic. In my WIP plugin (https://github.com/wakamex/opencode-observational-memory), I currently use worker-session orchestration (`session.create` + `session.prompt`) with recursion/cleanup guards. In supermemory (https://github.com/supermemoryai/opencode-supermemory), similar framework constraints show up in a different form (`session.summarize`, `session.promptAsync`, and compaction context injection). Request: add a plugin API like `ctx.llm.generate(...)` for internal calls with: - no transcript persistence by default - no normal chat/event hook recursion by default - OpenCode-native provider/model routing - optional per-call model override (for example, Observer model != chat model) Related plugin API discussion: #10868 (this request is narrower and focused on internal LLM execution). If this direction is approved, I can open a small PR for `ctx.llm.generate` first (text-only + isolated by default), with tests for no message persistence, no chat/event hook recursion, per-call model override.
yindo added the discussion label 2026-02-16 18:12:33 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label discussion
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#9486
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?