session persistance-ish
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 271
- Forks
- 26
- Avg merge
- 21h 13m
- Merged PRs (30d)
- 3
Description
I was thinking we might wanna start a new conversation every time the extension loads (1 nvim session = 1 pi session)
The advantages would be
- making a quick edit AND then say something "actually, remove that" and it will have the context
- potentially faster responses: we can start the session at extension load time, so we remove that overhead when calling pi. Model response time would be the only time we care about
I'm not sure if it'd be too bad for long-running sessions
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
Review the extension-load path and the code that invokes pi to understand how sessions are currently created and reused. Determine how one session per Neovim session should behave for quick edits, context retention, startup latency, and long-running sessions; done requires an agreed lifecycle design and implementation that preserves the intended context without unacceptable session growth.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100