Authorization notice. Star CLI is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.
Who it is forA developer who paused a multi-day coding task and needs to pick up the earlier context or share a written record.
The problemRestarting an agent task from scratch loses the context of earlier decisions and tool results.
The outcomeA resumed conversation and a Markdown file that records the session.
What you need first
- Node.js 20 or newer
- pnpm, only if you build from source
- An API key for an OpenAI, Anthropic, or OpenAI-compatible provider, set via /connect or config.toml
Steps
- Install the CLI with
npm install -g @cryer/star-cli. - Start the REPL in the project folder with
star, work on a task, and exit. - Reopen the saved session with
star -ror by typing/resumeinside the REPL. - Type
/exportin the REPL to write the session to a Markdown file.
Prompt for your agent
Using the cryer/star-cli repo, run `star -r` in <project-dir>, select the session for <task>, then run `/export`. Report the exported file path and verify that the file opens as Markdown.
Caveat. The README does not say where /export saves its file, so check the output location during your first run.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: 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