Feature request: Connect to an already running sandboxed pi
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 271
- Forks
- 26
- Avg merge
- 21h 13m
- Merged PRs (30d)
- 3
Description
It would be useful to have an option to connect to an already running sandboxed, headless pi instance instead of having pi.nvim start pi as a subprocess.
Motivation
If Neovim is sandboxed as well, it would be convenient to run Neovim and pi in separate sandbox profiles (nono in my case).
For example:
Neovim runs in one nono sandbox profile.
Headless pi --mode rpc runs in another, more restrictive nono sandbox profile.
pi.nvim connects to the already running pi instance instead of spawning it itself.
This would allow the Neovim and pi sandboxes to have independent permissions while still providing the same pi.nvim UI and workflow.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading pi.nvim's current subprocess startup path and how it communicates with pi --mode rpc. Add an option to connect to an already running headless pi instance while preserving the existing UI and workflow; done means Neovim can use a separately sandboxed process without spawning another one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua, vim
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100