openhands-cli

Delegate multi-step repository tasks to OpenHands CLI with structured JSON output.

5|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/amirkiarafiei/subagent-cli-skills --skill openhands-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openhands-cli
Source: https://github.com/amirkiarafiei/subagent-cli-skills/tree/main/skills/openhands-cli
Command: npx skills add https://github.com/amirkiarafiei/subagent-cli-skills --skill openhands-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

OpenHands CLI helps you offload large, multi-step repository work that would otherwise consume too much of your main agent’s context window.

Core Features & Use Cases

  • Autonomous long-horizon execution: Runs a separate pass over your repo for implementations, refactors, and batch edits with minimal supervision.
  • Stateless context handoff: Lets you include the original goal, prior decisions, scope, constraints, and verification steps so the isolated run stays aligned with the main thread.
  • Headless automation outputs: Uses programmatic headless mode with structured JSON output so results can be reviewed and reconciled safely.

Quick Start

Ask your agent to run OpenHands headless to refactor a specific part of your codebase while passing the original goal, prior decisions, scope, constraints, and a required verification command.

Frequently Asked Questions about openhands-cli

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

FAQPage Schema
How do I delegate large repository refactors to a headless agent without consuming my main context window?

You can delegate large repository refactors to a headless agent by passing the original goal, prior decisions, scope, constraints, and a verification command to OpenHands CLI, which executes the task isolated from your main thread.

What is headless automation for long-horizon codebase tasks and when do I need it?

Headless automation for long-horizon tasks is a non-interactive execution mode that runs a separate pass over your repository for autonomous implementations and batch edits, needed when multi-step work threatens to exhaust your main agent's context limit.

How do I pass context and scope constraints to an autonomous CLI agent for batch file writes?

To pass context and scope constraints to an autonomous CLI agent, you provide a full prompt-based context handoff including the original goal, prior decisions, scope boundaries, constraints, and mandatory verification commands before the headless run begins.

Does OpenHands CLI support structured JSON output for CI/CD pipeline reconciliation?

Yes, OpenHands CLI supports structured JSON output for CI/CD pipeline reconciliation, allowing programmatic headless mode results to be safely reviewed, verified, and reconciled by your main orchestration thread after automated changes.

Can I run non-interactive headless execution for autonomous codebase implementations?

Yes, you can run non-interactive headless execution for autonomous codebase implementations using OpenHands CLI, which handles broad refactors and batch file writes with minimal supervision while keeping work aligned through stateless context handoff.

What are the limitations of delegating repository tasks to a headless execution pass?

A key limitation of delegating repository tasks to a headless pass is the requirement for stateless context handoff; without explicitly providing the goal, decisions, scope, and verification steps, the isolated run may misalign from the main thread's intent.