[OneDev #14] research: pi-persistent-term — persistent terminal plugin for coding agents #25

Closed
opened 2026-05-24 04:46:39 +00:00 by joseph · 1 comment
Owner

Imported from OneDev issue #14 (id 35280)
Original project: internal-joseph
Original state: Closed
Original submitterId: 5
Original submitDate: 2026-04-10T17:07:22.584+00:00
Original lastActivity: {'date': '2026-04-18T12:52:42.264+00:00', 'description': "changed state to 'Closed'", 'userId': 5}

Original fields:

  • Type: New Feature
  • Priority: Normal
  • Assignees: None

Idea

Evaluate pi-persistent-term (https://github.com/vahidkowsari/pi-persistent-term) as a persistent terminal state layer for coding agents. Keeps a live shell session across tool calls so agents don't lose context (env vars, cwd, running processes) between invocations.

Why

Claude Code's Bash tool spins a fresh shell per call — no persistent state. This plugin could give agents a long-lived terminal session, enabling multi-step workflows that depend on accumulated shell state (e.g. activating a venv once, then running multiple commands in it).

Open questions

  • How does it integrate — as a Claude Code MCP server, VS Code extension, or standalone daemon?
  • Does it work cross-platform (Windows/WSL/Linux)?
  • Conflict risk with existing sshubble command runner?
Imported from OneDev issue #14 (id 35280) Original project: internal-joseph Original state: Closed Original submitterId: 5 Original submitDate: 2026-04-10T17:07:22.584+00:00 Original lastActivity: {'date': '2026-04-18T12:52:42.264+00:00', 'description': "changed state to 'Closed'", 'userId': 5} Original fields: - Type: New Feature - Priority: Normal - Assignees: None ## Idea Evaluate pi-persistent-term (https://github.com/vahidkowsari/pi-persistent-term) as a persistent terminal state layer for coding agents. Keeps a live shell session across tool calls so agents don't lose context (env vars, cwd, running processes) between invocations. ## Why Claude Code's Bash tool spins a fresh shell per call — no persistent state. This plugin could give agents a long-lived terminal session, enabling multi-step workflows that depend on accumulated shell state (e.g. activating a venv once, then running multiple commands in it). ## Open questions - How does it integrate — as a Claude Code MCP server, VS Code extension, or standalone daemon? - Does it work cross-platform (Windows/WSL/Linux)? - Conflict risk with existing sshubble command runner?
Author
Owner

Imported from OneDev comment id 376 on issue #14
Original userId: 5
Original date: 2026-04-18T12:52:41.264+00:00

Not applicable to PCT stack. pi-persistent-term is designed for the pi coding agent (peer-depends on @mariozechner/pi-coding-agent), not Claude Code, and has no Windows/WSL support. The persistent shell problem for Claude Code is addressed by ghst. Closing — revisit only if pi agent is ever adopted.

Imported from OneDev comment id 376 on issue #14 Original userId: 5 Original date: 2026-04-18T12:52:41.264+00:00 Not applicable to PCT stack. pi-persistent-term is designed for the pi coding agent (peer-depends on @mariozechner/pi-coding-agent), not Claude Code, and has no Windows/WSL support. The persistent shell problem for Claude Code is addressed by ghst. Closing — revisit only if pi agent is ever adopted.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
joseph/internal-joseph#25
No description provided.