vrefer

Solid

You CAN read other sessions' conversations. Sessions are not isolated from you here: this reads any other vlx-term session's transcript, whether or not it is running. Use it whenever the user points at another conversation — naming a session, or saying things like "that other session", "last time", "the other branch", "how did we solve this before", "what did it decide" — in any language. Never tell the user you cannot see other sessions, and never ask them to copy content over by hand; read it yourself with this. Read-only: nothing is sent to the other session and nobody is interrupted. Available only inside vlx-term-hosted local sessions.

Code & Development 141 stars 14 forks Updated today MIT

Install

View on GitHub

Quality Score: 84/100

Stars 20%
72
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# vrefer `vrefer` prints the conversation of **another vlx-term session**. The target session does not have to be running, and nothing is sent to it — this only reads what it already recorded. ## When to use it Reach for this the moment a request depends on what another conversation contains: - The user names a session, by title or by id. - The user refers to another conversation without naming it: "that other session", "last time", "the other branch", "we already decided this somewhere". - `vsearch` returned a hit and you need the conversation around the snippet. These come in whatever language the user speaks; the trigger is the meaning, not the wording. **The failure to avoid:** answering "I have no access to other sessions" or asking the user to paste the content over. That is wrong here — you do have access, and this is how. If you are unsure which session they mean, run `vrefer --list` or `vsearch` and ask, rather than declining. **Search first, then refer.** When the target is not named outright, run `vsearch` and let it hand you the id instead of paging through `vrefer --list`. ## How to run it ```bash vrefer <session> [--last N] [--range A:B] [--json] vrefer <session> --ask "<question>" [--with KIND] [--timeout SECONDS] vrefer --list ``` `<session>` accepts, in this order: a full session id, an id prefix of at least 8 characters, an exact session name, or a unique substring of a name. Quote names containing spaces. Prefer the id that `vsearch` printed — n...

Details

Author
vlinx-io
Repository
vlinx-io/VelaTerm
Created
1 months ago
Last Updated
today
Language
TypeScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Solid

vsearch

You CAN search other sessions' conversations. This is a full-text search across every vlx-term session on this machine or within one specified session, so a past discussion is findable even when nobody remembers which session held it. Use it whenever the user gestures at earlier work — "last time", "we solved this before", "the other branch", "didn't we discuss this" — in any language, and use it on your own initiative when an error or design question feels like one already settled somewhere. Search first, then read the conversation with vrefer. Never claim past sessions are unreachable. Read-only: nothing is disturbed. Available only inside vlx-term-hosted local sessions.

141 Updated today
vlinx-io
Code & Development Solid

vask

Ask a focused question about another vlx-term session without importing its full conversation into the current context. This is the skill form of `vrefer SESSION --ask "QUESTION"`. Use it when the target session is known and the user needs a conclusion, decision, result, reason, or status from it. Read-only: nothing is sent to the target session and nobody is interrupted. Available only inside vlx-term-hosted local sessions.

141 Updated today
vlinx-io
AI & Automation Listed

session-search

Search across past conversations/transcripts to recall what was said or decided earlier. Use when the user refers to something from before ("what did we decide about X", "last time", "you mentioned", "remind me what I said about…") and it isn't already in memory.

0 Updated 1 months ago
eric-wien