instar-session

Spawn and manage persistent Claude Code background sessions with tmux.

75|18|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/JKHeadley/instar --skill instar-session
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: instar-session
Source: https://github.com/JKHeadley/instar/tree/main/skills/instar-session
Command: npx skills add https://github.com/JKHeadley/instar --skill instar-session

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the bottleneck of single-threaded agent work by letting you spawn, monitor, and communicate with persistent Claude Code sessions that keep running after the current conversation moves on.

Core Features & Use Cases

  • Background Execution: Start long-running tasks without blocking your active session.
  • Parallel Workflows: Run multiple research or analysis sessions at the same time with separate context windows.
  • Session Control: Check status, read output, send follow-up instructions, and stop sessions when they are done.
  • Use Case: Ask one session to research a topic, another to audit code, and a third to draft notes, then review their outputs when each finishes.

Quick Start

Ask the agent to set up Instar if needed, then spawn a persistent background session for your task and tell it how you want the results reported back.

Frequently Asked Questions about instar-session

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run Claude Code sessions in the background without blocking my active conversation?

You can run Claude Code sessions in the background by spawning persistent, tmux-backed sessions that operate independently. This allows long-running work to continue with its own context window and lifecycle while you keep interacting in your current conversation.

Can I run multiple parallel research tasks using Claude Code at the same time?

Yes, you can run multiple parallel research tasks by spawning separate persistent background sessions. Each session receives its own context window and lifecycle, enabling simultaneous research, code audits, and drafting tasks.

Do I need tmux to manage persistent Claude Code background sessions?

Yes, tmux is required to manage persistent Claude Code background sessions. The system relies on tmux-backed sessions to maintain server health checks, authenticated API access, output capture, and input relay for long-running tasks.

How do I check the status and read the output of a background Claude Code task?

You check the status and read the output of a background Claude Code task by using session control features. These allow you to monitor active sessions, capture output, send follow-up instructions, and stop sessions when the work is finished.

What is the best way to manage long-running delayed audits with Claude Code?

The best way to manage long-running delayed audits is to spawn a persistent background session. This isolates the audit task into its own context window, allowing it to run independently until you are ready to review the captured output.