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

[FEATURE] Agent teams

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

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
lua
Área
devtools

Línea de trabajo

No se nombra ningún archivo, prueba ni punto de entrada. Empieza trazando el servidor WebSocket, la gestión del archivo de bloqueo y la ruta provider="none"; un posible primer hito es disponer de varios servidores por worktree con archivos de bloqueo separados, mientras que las cuestiones más amplias sobre el alcance por pestaña y el protocolo siguen sin resolverse.

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

Descripción

Feature Description

Support for agent teams

As far as I can tell from the docs and the code, there would be issues when using agent teams with interacting with the worktrees and the neovim instance.

Use Case

Parallel worktrees with agents assigned to them via agent teams for larger projects

Proposed Solution

We could have a separate tab for each parallel worktree, where the tab's buffers are scoped to that worktree.

Main issue here is, how do we organize our directory structure so that when you are navigating between files, it is easy to see what is in what worktree? The only way I can think to do this is if you spawn your nvim instance from the parent directory. For example, if I have a project directory for my main work (without worktrees), I would need a project_wrapper directory (terrible name, but you get the idea) that has the project dir and the worktree dirs that the agents are spinning up as siblings.

The tab-per-worktree UI is one problem, but the bigger issue is probably the WebSocket server itself. Right now the plugin runs one server with one lock file. Even if we get tabs working perfectly, the worker agents spawned by agent teams would all be hitting the same server, and the diff/context routing has no concept of "this diff belongs to this worktree's tab." That's a pretty fundamental architectural thing to solve.

Also worth noting — the lock file convention (~/.claude/ide/[port].lock) is Anthropic's, not this plugin's. If agent team workers don't know how to look for separate lock files per worktree or per session, there's only so much the plugin can do here. Might be worth checking if this is actually something Anthropic needs to address on the CLI side first (maybe the lock file protocol needs a worktree discriminator or something).

One possible incremental step: support spinning up multiple WebSocket servers (one per worktree), each with its own lock file, under provider = "none". That way people using the tmux approach (like me) could at least get IDE integration per-pane without needing the full tab-scoping solution. Less ambitious, but probably more realistic as a first pass.

Has anyone looked at how the VS Code extension handles agent teams? That would tell us a lot about whether the protocol already supports this or if it's a gap everywhere.

EDIT: Turns out Anthropic doesn't support agent teams in the VS Code extension! So that's telling...

Alternatives Considered

What I do now is just...not use agent teams. I have to coordinate in separate tmux windows a separate nvim + agent.

Lenguaje dominante
Lua
Estrellas
3.1k
Forks
217
Sin PR fusionados en 30 d

Preparar el entorno

Aún no hemos revisado los archivos de configuración de este proyecto. Empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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/claudecode.nvim

Todos los issues de coder/claudecode.nvim

Issues similares

Más issues de Lua

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.