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

[FEATURE] Multiple Named Terminal Layout Configurations

Abierto
  • ¿Algo no está bien?
#139 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
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
lua
Área
tooling

Línea de trabajo

Comienza leyendo la configuración de terminal existente y la API de Lua detrás de open(), focus() y el comando :ClaudeCode. Rastrea cómo se gestionan el búfer de terminal, las opciones de disposición, el proceso de Claude CLI y el servidor WebSocket. Se considera terminado cuando las configuraciones con nombre, el comportamiento con disposiciones predeterminadas y no válidas, el cambio de disposición y la compatibilidad con versiones anteriores funcionan sin crear instancias adicionales de Claude.

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

Descripción

Problem / Use Case

Currently, claudecode.nvim only supports a single terminal layout configuration. Users who want to interact with Claude Code in different contexts (e.g., floating window for quick queries, side split for longer sessions) must either:

  1. Reconfigure and reload the plugin to change layouts
  2. Create multiple independent Claude instances (which breaks the single conversation flow)
  3. Manually manipulate windows after opening

This limitation makes it difficult to have flexible workflow patterns while maintaining a single Claude conversation instance.

Proposed Solution

Support multiple named terminal layout configurations accessible via Lua API, allowing layout selection to be completely separate from Claude CLI arguments.

Configuration Example
{
  "coder/claudecode.nvim",
  opts = {
    terminal = {
      -- Define multiple named configurations
      configurations = {
        float = {
          snacks_win_opts = {
            position = "float",
            width = 0.8,
            height = 0.8,
            border = "rounded",
          }
        },
        split = {
          snacks_win_opts = {
            position = "right",
            width = 0.4,
            border = "rounded",
          }
        },
        drawer = {
          snacks_win_opts = {
            position = "bottom",
            height = 0.3,
            border = "single",
          }
        }
      },
      -- Optional: specify default configuration
      default = "float"  -- used when no layout is specified
    },
  },
}
Lua API Usage
-- Open Claude with specific layout and arguments
require("claudecode").open({
  layout = "split",
  args = "--dangerously-skip-permissions --continue"
})

-- Or just layout (uses default args)
require("claudecode").open({ layout = "float" })

-- Or just args (uses default layout)
require("claudecode").open({ args = "--continue" })

-- Focus with layout preference (switch to different layout)
require("claudecode").focus({ layout = "drawer" })
Keymap Examples
-- Floating window for quick access
vim.keymap.set({ "n", "i", "v", "t" }, "<C-M-S-a>", function()
  require("claudecode").open({
    layout = "float",
    args = "--dangerously-skip-permissions --continue"
  })
end, { desc = "Claude (floating)" })

-- Split for focused work
vim.keymap.set({ "n", "i", "v", "t" }, "<C-M-S-s>", function()
  require("claudecode").open({
    layout = "split",
    args = "--dangerously-skip-permissions --continue"
  })
end, { desc = "Claude (split)" })

-- Drawer for context checking
vim.keymap.set("n", "<leader>ad", function()
  require("claudecode").open({
    layout = "drawer",
    args = "--continue"
  })
end, { desc = "Claude (drawer)" })
Command Compatibility

The existing :ClaudeCode command should continue to work unchanged, using the default layout:

" Uses default layout configuration
:ClaudeCode --continue
:ClaudeCode --dangerously-skip-permissions

Benefits

  1. Single Instance: All layouts reference the same Claude conversation and WebSocket server
  2. Declarative: Layout configurations defined once, reused everywhere
  3. No CLI Conflicts: Layout selection completely separate from Claude CLI arguments
  4. Flexible Workflows: Different layouts for different contexts without reconfiguration
  5. Backward Compatible: Existing configurations continue to work
  6. Clean API: Simple, predictable Lua interface
  7. Composable: Easy to build complex keymaps and commands on top

Backward Compatibility

For backward compatibility, both configuration styles should be supported:

-- Old style (still works, becomes the default configuration)
terminal = {
  snacks_win_opts = { position = "float", ... }
}

-- New style (opt-in for multiple configurations)
terminal = {
  configurations = {
    float = { snacks_win_opts = { ... } },
    split = { snacks_win_opts = { ... } }
  },
  default = "float"
}

If configurations is not specified, the plugin behaves exactly as it does today.

Implementation Notes

  • The same Claude CLI process and WebSocket server instance should be reused across all layouts
  • When switching layouts, the terminal buffer could be moved to a new window with the requested layout
  • The layout parameter should be optional; if omitted, use the default configuration
  • Invalid layout names should fall back to the default configuration with a warning

Alternative Considered

Using command-line arguments like :ClaudeCode split --continue was considered but rejected because it would conflict with Claude CLI's native argument parsing and create an antipattern of mixing layout concerns with CLI flags.

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

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

  • Sin Dockerfile ni 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/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.