Feature: Add direct tool call API for E2E testing

[tryweb]

Problem

Currently, there's no way to directly call plugin tools like memory_remember for E2E testing. The available options are:

1. LLM-driven tool calls - Tools are only triggered by LLM decisions during conversation
2. HTTP Message API - Returns empty body (streaming issue)
3. Async API - Returns 204 but doesn't process messages properly

This makes it impossible to verify plugin functionality through automated tests.

Proposed Solution

Add a direct tool call API endpoint:

POST /experimental/tool/{toolId}/execute
{
  "args": { /* tool arguments */ },
  "context": {
    "worktree": "/path/to/worktree",
    "sessionID": "optional-session-id"
  }
}

This would allow:

• Direct verification of tool functionality
• Automated E2E tests without LLM dependency
• Consistent testing regardless of LLM availability

References

• OpenCode Server API: https://opencode.ai/docs/server/
• OpenCode Plugins: https://opencode.ai/docs/plugins/
• Current tool list available via: GET /experimental/tool/ids

Example Use Case

# E2E test for memory plugin
curl -X POST http://localhost:4096/experimental/tool/memory_remember/execute \
  -H "Authorization: Basic $(echo -n 'opencode:password' | base64)" \
  -H "Content-Type: application/json" \
  -d '{
    "args": {
      "text": "Test memory",
      "category": "testing"
    },
    "context": {
      "worktree": "/home/user/project"
    }
  }'

This would return the tool execution result directly, enabling automated testing.

[tryweb]

Analysis Result

This feature request is not appropriate for this plugin and should be directed at the OpenCode host application instead.

Why

1. No HTTP Server: lancedb-opencode-pro is a pure OpenCode plugin with zero HTTP server components. It cannot add API endpoints - that capability belongs to OpenCode's server layer.

2. Architecture Boundary: Plugin tools are executed via OpenCode's plugin hooks system (hooks.tool.{toolName}.execute()). The plugin only provides tool definitions; OpenCode handles execution and API exposure.

3. E2E Testing Already Works: This plugin already supports E2E testing through hook-based tool execution:

   const hooks = await plugin({...});
   await hooks.tool.memory_remember.execute({ text: "...", category: "testing" }, ctx);

   See scripts/e2e-opencode-memory.mjs for a complete example.

4. Plugin Cannot Intercept Tool Calls: OpenCode doesn't expose a tool.execute hook to plugins, so there's no way for this plugin to implement the requested endpoint.

Recommendation

Please file this feature request against the OpenCode repository instead:

• https://github.com/opencode-ai/opencode

If OpenCode adds /experimental/tool/{toolId}/execute, all plugins (including this one) would automatically benefit without any changes needed.

Existing Alternative

For E2E testing of this plugin, use the hook-based approach shown in scripts/e2e-opencode-memory.mjs. This works today and doesn't require any new API endpoints.

[tryweb]

Update: Found Working Solution

Thank you for the clarification! The hook-based approach works perfectly for E2E testing.

Solution

Using the plugin hooks directly allows direct tool execution:

const hooks = await plugin({
  client: { /* ... */ },
  project: { /* ... */ },
  directory: "/workspace",
  worktree: "/workspace",
  serverUrl: new URL("http://localhost:4096"),
  \$: () => { /* mock shell */ },
});

const ctx = {
  sessionID: "test-session",
  messageID: "test-msg",
  agent: "general",
  directory: "/workspace",
  worktree: "/workspace",
  abort: new AbortController().signal,
  metadata() {},
  async ask() {},
};

// Test memory_remember
const result = await hooks.tool.memory_remember.execute(
  { text: "Test memory content (>= 80 chars)", category: "testing" },
  ctx
);

Verified Working

Tool	Status
Plugin hook loading	✅
memory_remember	✅
memory_search	✅
memory_stats	✅

This approach works in the container environment without requiring HTTP API access.

Recommendation

This hook-based E2E approach can be documented for users who need to test the plugin functionality directly.