Browse / General-purpose / inav-claude

inav-claude

sensei-hacker

Claude Code workflow infrastructure for INAV development

Open sensei-hacker/inav-claude → Does not match the four rules.

Works with any agent

ships AGENTS.md, the cross-tool instruction file.

In its own words

README.mdsensei-hacker/inav-claude

Claude Code workflow infrastructure for INAV flight controller development using a multi-role AI agent system.

Overview

This repository provides a structured workflow for using Claude Code to develop INAV firmware and configurator features. It implements a role-based system where different Claude instances take on specific responsibilities (Manager, Developer, Release Manager), communicating through an email-like message passing system.

Quick Start

(tell Claude to read this readme and follow the steps here to set it up for you)

2. Clone the Required Repositories

This workflow requires the INAV firmware, configurator, and mspapi2 repositories. Clone them into the appropriate directories:

3. Set Up Context Files for Claude Code

Create symlinks so Claude Code automatically reads context when working in the third-party repos:

Symlink to your root inav-claude repo:

These symlinks allow Claude Code to automatically load context when working in those directories, while keeping the actual context files version-controlled in this repository.

4. Start Claude Code

Start Claude from the project root directory:

Claude will read CLAUDE.md and ask which role you want to work in (Manager, Developer, or Release Manager).

Roles and Workflow

Development Manager
  • Directory: manager/
  • Responsibilities: Project planning, task assignment, progress tracking
  • Read: manager/README.md

Quoting 31% of the README. Read the rest on GitHub ↗

Read from the repository's git tree on 2026-08-17.