harness-development

Develop and debug Rust harness-server backends normalizing CLI output into Codex App Server V2 protocol.

4|2|Updated Jun 10, 2026
One-click install
npx skills add https://github.com/useatrium/atrium --skill harness-development
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness-development
Source: https://github.com/useatrium/atrium/tree/main/centaur/.agents/skills/harness-development
Command: npx skills add https://github.com/useatrium/atrium --skill harness-development

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers add, modify, and debug harness-server backends while preserving a consistent Codex App Server V2 protocol and reliable streaming behavior.

Core Features & Use Cases

  • Harness Backend Development: Implement Rust backends for Claude Code, Amp, Codex, and other harness CLIs.
  • Protocol Normalization: Convert native harness events into typed OpenAI Codex App Server V2 events without introducing Python or TypeScript normalizers.
  • Streaming and Steering Debugging: Investigate turn completion, session resume, multi-turn conversations, tool use, steering, and cancellation semantics.
  • Differential Testing: Compare real harness stdout and stderr with normalized protocol output using unit tests and ignored real-binary cargo tests.

Quick Start

Use the harness-development skill to add or debug a harness-server backend and validate its streaming, steering, and resume behavior with differential tests.

Frequently Asked Questions about harness-development

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

FAQPage Schema
How do I normalize CLI output for the Codex App Server V2 protocol?

You normalize CLI output by developing a Rust harness-server backend that performs typed Rust event conversions, translating native harness events into protocol-compliant stdout without needing Python or TypeScript normalizers.

How do I debug session resume and steering behavior in a Rust harness backend?

Debug session resume and steering behavior by investigating turn completion, multi-turn conversations, and cancellation semantics within your Rust harness backend, validating session continuity through real differential tests against native harness stdout.

What is differential testing for coding-agent harness streaming?

Differential testing for harness streaming compares real harness stdout and stderr with normalized protocol output using unit tests and ignored real-binary cargo tests to validate streaming behavior and session continuity.

Can I add harness support for Claude Code and Amp using only Rust?

Yes, you can implement Rust backends for Claude Code, Amp, and Codex CLIs by applying typed Rust event conversions to produce protocol-compliant stdout, completely avoiding the need for Python or TypeScript normalizers.

Why does my harness server lose session continuity during multi-turn conversations?

Session continuity drops during multi-turn conversations when native harness events are not properly converted into typed Codex App Server V2 events, requiring debugging of steering semantics and validation through differential testing.

Does harness backend development require external normalizers for protocol compliance?

No, harness backend development relies entirely on typed Rust event conversions to achieve Codex App Server V2 protocol compliance, explicitly avoiding the introduction of Python or TypeScript normalizers in the data pipeline.