headless

Launch ikigai headlessly and control it via ikigai-ctl commands and framebuffer reads.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/mgreenly/ikigai --skill headless-mgreenly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: headless
Source: https://github.com/mgreenly/ikigai/tree/main/.claude/library/headless
Command: npx skills add https://github.com/mgreenly/ikigai --skill headless-mgreenly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Driving interactive ikigai sessions from an agent without a live terminal, enabling automated testing and remote control.

Core Features & Use Cases

  • Headless launch: run ikigai in the background with no TTY required.
  • Interact via ikigai-ctl: send keystrokes, read frames, and observe LLM responses programmatically.
  • Deterministic loop: implement read, wait_idle, and framebuffer inspection to drive conversations in automation.

Quick Start

Start the ikigai headless session and connect your agent to drive and observe the UI.

Frequently Asked Questions about headless

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

FAQPage Schema
How do I control a headless CLI instance from an agent session?

You can control a headless CLI instance by launching ikigai in the background without a TTY and using ikigai-ctl to send keystrokes and read the framebuffer programmatically.

Can I automate LLM response observation without a live terminal?

Automating LLM response observation without a live terminal is possible by implementing a deterministic loop that reads the framebuffer and checks for idle states to drive conversations in automation.

What is the best way to drive interactive ikigai sessions for automated testing?

Driving interactive ikigai sessions for automated testing is best achieved using a minimal CLI workflow that exposes controlled headless operations, enabling remote interaction without a live terminal.

Do I need a local ikigai binary to use headless framebuffer inspection?

Using headless framebuffer inspection requires a local ikigai binary, as the Skill depends on this local executable to launch the instance and expose the CLI workflow for controlled operations.

How does framebuffer inspection work when issuing commands via ikigai-ctl?

Framebuffer inspection works by reading the current frame after issuing commands via ikigai-ctl, allowing the agent to observe LLM responses and determine idle states within a deterministic automation loop.