Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

ACP: first prompt can miss MCP tools supplied to session/new (2.0.18 / 2.0.22)

Abierto
  • ¿Algo no está bien?
#53,299 1 comentario 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@kitlangton ya está trabajando en esto.

Desde el 5/10/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

Description

MCP tools supplied through ACP session/new can be absent from the first model-visible tool catalog, even after session/new has returned successfully. A later prompt in the same session sees them.

Reproduced on 2.0.18 and 2.0.22 on macOS arm64. Two independent 2.0.18 runs both showed: immediate prompt = tools absent; prompt after 500 ms = tools present. A diagnostic control that waits for actual tool registration makes the first prompt include them.

The diagnostic observer records tool registration and model context, then deliberately stops before provider dispatch. These observations do not require a model/API request. Native permissions were ask, with the test MCP namespace allowed.

Expected: the first prompt should use the tools supplied for that session without the ACP client needing an arbitrary sleep.

Suspected location in v2.0.22: packages/core/src/tool/mcp.ts debounces subsequent updates by 100 ms, but flush only awaits the initial registration. packages/core/src/session/context.ts then takes the tool snapshot. This appears to leave a readiness gap for MCP servers added by ACP; please confirm the diagnosis.

Plugins

Custom diagnostic observer only; separate control adds a tool-readiness wait. No third-party plugin pack.

OpenCode version

2.0.18 and 2.0.22

Steps to reproduce
  1. Start opencode acp with a clean runtime/config directory.
  2. Complete ACP initialize.
  3. Call session/new with an absolute cwd and a local stdio MCP server exposing two fixed tools. Allow this MCP namespace.
  4. Wait for the successful session/new response, then immediately call session/prompt.
  5. Inspect the model-visible tool catalog: the supplied MCP tools may be missing, while the registry logs show them arriving shortly afterward.
  6. Send another prompt in the same session after 500 ms: the tools are now present.

Control: wait for the supplied tools to enter the registry before preparing the first prompt; the first context then includes them. This control is a diagnostic workaround, not an upstream fix.

Screenshot and/or share link

No response

Operating System

macOS, Darwin 27.0.0, Apple Silicon arm64

Terminal

ACP stdio client launching opencode acp (not the TUI)

Lenguaje dominante
TypeScript
Estrellas
212k
Forks
28.1k
Merge medio
9 h 58 min
PR fusionados (30 d)
373

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de anomalyco/opencode

Todos los issues de anomalyco/opencode

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.