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

AI/agent terminal sessions pollute PSReadLine history

Abierto
#5,123 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
55/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
csharp, powershell
Área
cli

Línea de trabajo

Start by locating PSReadLine initialization and the AddToHistoryHandler/history persistence path, including the text and SQLite modes mentioned in the issue. Confirm that PSREADLINE_HISTORY_SAVE=0 selects MemoryOnly before history writes, preserves current-session recall, and avoids persistent saves regardless of profile loading.

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

Descripción

Needs-Triage :mag:

Summary

When AI agents (e.g., GitHub Copilot, VS Code terminal agents) execute commands in PowerShell terminals, those commands are saved to PSReadLine history indistinguishably from user-typed commands. This pollutes history recall with commands the user never typed, inflates frequency counts, and degrades the usefulness of history recall.

Problem

AI coding assistants routinely run commands like Get-ChildItem, dotnet build, git status, etc. in integrated terminals. These get recorded to PSReadLine history (both text file and SQLite modes) as if the user typed them. Over time this means:

  • History recall is noisy — Up arrow surfaces agent commands the user didn't type
  • Frequency-based ranking is skewed — location-aware recall ranks agent-repeated commands higher than user favorites
  • HistoryNoDuplicates doesn't help — the commands are real commands, just not user-initiated

Current Workaround

Users can add this to their $PROFILE:

# Requires the agent to set this env var before launching pwsh
if ($env:PSREADLINE_HISTORY_SAVE -eq '0') {
    Set-PSReadLineOption -AddToHistoryHandler { [Microsoft.PowerShell.AddToHistoryOption]::MemoryOnly }
}

But this is fragile because:

  1. The agent must set the env var — requires cooperation from VS Code / Copilot
  2. Agents that use pwsh -NoProfile bypass the check entirely
  3. Users must manually add the snippet

Proposal

Add a built-in environment variable check in PSReadLine's initialization, so that agent-spawned terminals can opt out of persistent history without requiring profile configuration:

// During PSReadLine init, before any history writes
if (Environment.GetEnvironmentVariable("PSREADLINE_HISTORY_SAVE") == "0")
{
    Options.AddToHistoryHandler = _ => AddToHistoryOption.MemoryOnly;
}

This way:

  • Any agent framework just sets PSREADLINE_HISTORY_SAVE=0 as a process environment variable before launching pwsh
  • Works regardless of -NoProfile
  • No user configuration needed
  • Commands still available in the current session's memory (Up arrow works), just not persisted to disk

Environment

  • VS Code with GitHub Copilot agent terminals
Lenguaje dominante
C#
Estrellas
4.4k
Forks
341
Métricas de merge de PR
Sin PR fusionados en 30 d

Guía de contribución

Abrir la 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 PowerShell/PSReadLine

Todos los issues de PowerShell/PSReadLine

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.