DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to let agent sessions search and message each other with Vela Term

Use vsearch, vrefer and vtell so one agent can pull in work from another session.

Authorization notice. Vela Term is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Who it is forA developer whose agent needs context from earlier conversations in other sessions on the same project.

The problemRelevant decisions and findings are scattered across several agent sessions, and copying them by hand is slow and error-prone.

The outcomeAn agent can find earlier conversations, read or ask about them, and send a message to another running session.

What you need first

  • A computer running macOS, Windows or Linux
  • The VelaTerm installer from velaterm.com/download
  • A logged-in local Codex or Claude Code install for agent sessions and audits
  • A phone with the VelaTerm iOS or Android app for mobile access

Steps

  1. Start two sessions running Claude Code, Codex, OpenCode or Pi in the same project.
  2. In one session, use the vsearch command to search every session for earlier work on the topic you need.
  3. Use vrefer to read the matching conversation or ask a question about it.
  4. Use vtell to message the other session, adding --steer if the message should join a turn that is already running.

Prompt for your agent

In the VelaTerm project at <project-path>, have one agent session use vsearch to find earlier work on <topic>, then vrefer to read the best match. Expected output: a short summary of the matched conversation with its session name. Verify that the summary cites a real session from the tree before you act on it.

Caveat. The README names vsearch, vrefer and vtell but does not show their arguments, so check the user manual before scripting them.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page