Understand the project
Practical overview
When it fits
Use Instar when a Claude Code agent needs continuity beyond one session, durable context, scheduled work or a messaging interface. The documented setup path is also relevant when you want to start from a guided CLI wizard rather than assemble these elements separately.
Who it is for
- Developers building persistent Claude Code agents
- Users who need an agent to retain context across sessions
- Builders creating recurring-task or scheduled agent services
- Users seeking phone-based interaction with an agent through Telegram
Documented uses
- Preserve agent memory and identity across restarts and session boundaries
- Run recurring agent jobs through scheduling infrastructure
- Provide a messaging interface for a persistent Claude Code agent
- Organize multiple Claude Code sessions for interactive and scheduled work
Before you choose
Requirements & limits
The repository is public and lists an MIT license. The documented setup requires Node.js 20 or later, the Claude Code CLI, and either an Anthropic API key or a Claude subscription.
- It is built around Claude Code sessions rather than a generic model API.
- Memory, identity and session continuity are central to the framework’s design.
- Scheduling is supported, but the available material does not specify syntax or trigger configuration.
- Telegram is explicitly identified as an integration surface; the setup wizard also describes WhatsApp and iMessage configuration.
- The project is TypeScript-based and can be used through a CLI setup flow.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Evidence and transparency
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 3 October 2026
- Original website title
- JKHeadley/instar · Official homepage title · retained in its source language