[FEATURE]: Desktop (V2): optional per-session prompt history
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
- 48/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- typescript
- Área
- desktop
Línea de trabajo
Start with packages/app/src/composer/history/store.ts and packages/app/src/composer/model.ts, then trace the Desktop settings surface and how the active session reaches the composer. The issue describes the desired scope and default, but does not identify the settings files or tests. Done means an opt-in current-session setting scopes ↑/↓ and Shift+↑ while preserving global behavior by default, with the new-session behavior documented.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Feature hasn't been suggested before.
- I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
What I'd like
Add an opt-in setting in OpenCode Desktop so prompt recall can be limited to the current session. Keep the current global behavior as the default.
Current behavior
In Desktop, the composer's ↑/↓ history and the Shift+↑ "Prompt history" picker are global. In an empty composer, ↑ recalls the last prompt sent in any session, and the picker lists prompts from every session and project.
With several sessions open, this makes recall unreliable and can pull text from an unrelated conversation into the current one. The global list is also capped, so a busy session can evict prompts from the session I'm actually working in.
Steps to reproduce
- Open two sessions in Desktop.
- Send
alphain session A. - Send
betain session B. - Go back to session A, focus the empty composer, and press ↑.
betais recalled instead ofalpha.- Press Shift+↑: the picker shows prompts from both sessions, and from other projects as well.
Environment
- OpenCode Desktop 2.3.2 (V2)
- Windows 10 22H2 (19045)
- Desktop app, not TUI
- No relevant plugins
Expected behavior
A Desktop setting, for example Prompt history scope:
- Global — current behavior, default.
- Current session — ↑/↓ and Shift+↑ only show prompts sent in the active session.
Scoping recall is enough; I'm not asking to change where history is stored. The new-session/home composer can keep global history or start empty, as long as the behavior is documented.
Notes
- This is the Desktop (
packages/app) counterpart of #52154, which tracks the TUI. Desktop has its own composer and settings surface and does not use the TUI'scli.json, so a TUI-onlyprompt.history_scopesetting would not cover it. I couldn't find an existing Desktop issue for this; if you'd rather track it in #52154, feel free to close this as a duplicate. - The current source stores this globally:
packages/app/src/composer/history/store.tsusesPersist.global("prompt-history")andPersist.global("prompt-history-shell");createComposerHistory()inpackages/app/src/composer/model.tsis called without session context. - Global history may be intentional — the TUI shipped per-session history and later reverted it (#43977 / #44416). I'm not asking to change the default; an opt-in Desktop setting is enough.
- Related: #52154 (open, TUI), #54505 / #63470 (closed duplicates), #55261 (closed TUI PR proposing an opt-in
prompt.history_scope).
- Lenguaje dominante
- TypeScript
- Estrellas
- 227k
- Forks
- 30.7k
- Merge medio
- 3 h 57 min
- PR fusionados (30 d)
- 484
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de anomalyco/opencode
-
[Site] Active section detection should respect scroll-margin-topPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abiertoarea/web reproduced type/bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
anomalyco/opencode#65384 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
area/cli type/feature version/v2
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
anomalyco/opencode#65379 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Shell tool: no upper bound on the timeout a model can ask for, so one call can hold a turn for hoursAbiertoarea/core platform/linux type/feature version/v2
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
anomalyco/opencode#65254 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
inference/go type/feature
Dificultad 1/5 1-3 horas Aptitud para principiantes 72/100
anomalyco/opencode#65148 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
area/providers type/feature version/v2
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
anomalyco/opencode#64845 · 1 comentario ·
Los mantenedores suelen responder en 1 día
Todos los issues de anomalyco/opencode
Issues similares
-
[Provider] antigravity-acp catalog omits gemini-4-hydrogen and gemini-4-neon that agy acp offersPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abiertocatalog provider provider-compatibility
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
lidge-jun/opencodex#9037 · 1 comentario · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
Project submission: xmcp DocsAbierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 62/100
slavakurilyak/awesome-ai-agents#1005 ·
-
kind/bug triage/unresolved
Dificultad 2/5 1-3 horas Aptitud para principiantes 60/100
Los mantenedores suelen responder en 1 día
-
effort:S P3 refactor
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
nightscout/nocturne#3735 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
wpilibsuite/systemcore-blocks-interface#641 ·
Los mantenedores suelen responder en 2 días