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

🤖 refactor: put the MCP modules that agent-loop files import behind Effect services

Abierto
  • ¿Algo no está bien?
#7,239 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
42/100
Tipo de issue
Refactorización
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
typescript
Área
backend, devtools

Línea de trabajo

Start with the phase 5 plan’s claim 3.5 and the four listed modules: workspaceMcpOverridesService.ts, mcpAppResultStore.ts, mcpServerManager.ts, and agentPlugins/mcpConfig.ts. Trace their imports from aiService.ts and turnRequestBuilder.ts, then inspect the Effect services and Node and test layers added in phase 5. Done means all listed host access goes through those services with behavior and persisted files unchanged, and the phase 5 end check reports only its specified follow-up modules and log.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Summary

Agent-loop files import these modules, and the modules still reach the host directly (fs, os, child_process, writeFileAtomic, a runtime class or a runtime builder). The local/no-host-imports rule checks only the agent-loop files themselves, so it does not see this host access. Phase 5 of the agent-loop refactor does not move these modules: its plan (claim 3.5, decision "reach") keeps one follow-up issue per group. This issue is the MCP group: MCP servers, overrides and app results.

Modules

Module Host refs Host imports Imported by agent-loop files at
src/node/services/workspaceMcpOverridesService.ts 44 fs/promises:2 fs:3 runtime/runtimeFactory:15 runtime/runtimeHelpers:16 aiService.ts:104 turnRequestBuilder.ts:158
src/node/services/mcpAppResultStore.ts 12 fs/promises:2 utils/fs:15 utils/writeFileAtomic:16 turnRequestBuilder.ts:87
src/node/services/mcpServerManager.ts 10 fs/promises:5 runtime/DevcontainerRuntime:88 runtime/RemoteRuntime:89 runtime/runtimeFactory:104 turnRequestBuilder.ts:149
src/node/services/agentPlugins/mcpConfig.ts 4 fs:7 fs/promises:8 turnRequestBuilder.ts:81

Total: 4 module(s), 70 uses of host bindings. Counts and lines come from reach.mjs --phase2 and reachRefs.mjs of the phase 5 plan, at ba9e451cab (phase 1 changed no file under src/).

Work

Move the host access of each module behind the Effect services that phase 5 adds (HostFiles, HostPaths, HostProcesses, RuntimeFactory, SessionFiles, SessionLocks), with a Node layer and a test layer, and no change in behavior or persisted files.

Trigger

After phase 5 ends (stacks 5a and 5b merged). Phase 5 end check 7 expects reach.mjs --phase2 to list only the 30 follow-up modules of these 8 issues and log.

Refs

  • Phase 5 plan v4 ("Host I/O Services for the Xum Agent Loop", artifact phase5-plan.html), claim 3.5.
  • Refs #7207 (the local/no-host-imports rule and its frozen pairs).

Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: high • Cost: $31.10

Lenguaje dominante
TypeScript
Estrellas
2.1k
Forks
140
Merge medio
3 h 24 min
PR fusionados (30 d)
954

Preparar el entorno

  • Incluye un Dockerfile o un archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

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 coder/xum

Todos los issues de coder/xum

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.