pablopunk / pablopunk/pi.nvim

session persistance-ish

Open
#21 3 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement help wanted
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

  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

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.