posit-dev / posit-dev/positron

multi-console: reconsider approach to console history (separate histories per session)

Open
#6,986 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area: console
Dominant language
TypeScript
Stars
4.3k
Forks
184
Avg merge
1d 11h
Merged PRs (30d)
206

Description

System details:

Positron and OS details:

Seeing it on

Positron Version: 2025.04.0 (Universal) build 109
Code - OSS Version: 1.97.0
Commit: 56a6c89ad24fbdeaa417ec9c03d05dbd9196c953
Date: 2025-03-17T11:31:23.496Z
Electron: 32.2.7
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Darwin arm64 24.3.0

but I think any multiconsole enabled console will see the same behavior.

Interpreter details:

Any Python interpreter.

Describe the issue:

No history is maintained (or maybe repopulated?) when Positron is shut down. IPython terminals have memory of historical commands, and I was expecting to be able to arrow up ⬆ into previously run commands. If I open another REPL via ipython in the Terminal pane, I'm able to see the commands I ran.

Steps to reproduce the issue:

  1. in a console, run foo = 'bar'
  2. shut down Positron
  3. reopen Positron
  4. in running console, press up arrow (or run %hist) and see nothing. I exp

Expected or desired behavior:

I expected to see the last run cell, foo='bar'

Were there any error messages in the UI, Output panel, or Developer Tools console?

None

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the shutdown and restart sequence with a Python console, then inspect how console history and sessions are handled. Done means previously entered commands remain available after reopening Positron and histories are separated appropriately for each console session.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, typescript
Domain
developer-experience, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.