create_session always creates a worktree -- no option for a local/in-place session
- Lenguaje dominante
- Sin datos de lenguaje
- Estrellas
- 2.1k
- Forks
- 153
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
**Mood:** 😕
**Category:** Bug
When spinning up a sub-session via the `create_session` tool, there is no parameter to choose a local/in-place (folder-backed) session -- it always creates a git worktree. For read-only workflows like `/m-code-review`, the worktree checkout adds unnecessary filesystem overhead, and there is no way to opt out. The tool exposes `project_id`, `base_branch`, `model`, `reasoning_effort`, `kickoff_*`, `name`, `notify_on_idle`, and `coordinate_with_creator`, but nothing to select session type.
**Expected:** a way to request an in-place/local session (e.g. a `session_type` field or a worktree toggle on `create_session`), with the resulting type reflected back in `get_session`.
---
| Field | Value |
| --- | --- |
| App version | 1.0.60 |
| OS | Windows 10.0.26200 |
| Theme | GitHub |
| Path | /agents |
| Tenure | Month 1 |
Guía de contribución
Línea de trabajo
Start by tracing the create_session tool and the get_session response, focusing on how worktrees and session metadata are currently selected and reported. Define the session-type option and verify that an in-place session avoids worktree creation while get_session reflects the resulting type.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- git
- Área
- desktop, tooling
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Tranquilo
- Claridad
- Bastante claro
- Aptitud para principiantes
- 48/100