fledge

One CLI for the dev loop. Any language. JSON by default. Read the docs and go.

fledge templates init my-tool --template rust-cli
cd my-tool
fledge lanes init
fledge lanes run ci

Working with AI agents? See AGENTS.md. Every command emits {schema_version: 1, ...}, FLEDGE_NON_INTERACTIVE=1 silences prompts, fledge ask and fledge review are spec-aware, and fledge introspect --json dumps the full command tree. Talks to the Anthropic API, any OpenAI-compatible endpoint (OpenAI, OpenRouter, Groq, ...), or any Ollama endpoint (local, cloud, or self-hosted) over plain HTTP. No CLI required.

Install

cargo install fledge                       # crates.io
brew install CorvidLabs/tap/fledge         # homebrew

fledge plugins install --defaults          # curated plugin set

curl -fsSL https://raw.githubusercontent.com/CorvidLabs/fledge/main/install.sh | sh
nix run github:CorvidLabs/fledge
git clone https://github.com/CorvidLabs/fledge.git && cd fledge && cargo install --path .

GitHub Actions

- uses: CorvidLabs/fledge@v1
  with:
    version: v1.7.2

Pin version to a release tag and the action downloads that binary directly — no GitHub API call, so nothing to rate-limit on shared runner IPs. Leave it at the default latest and the action resolves the tag via an authenticated API call (using github.token unless you pass your own token). version accepts a release tag or latest and nothing else, since the value reaches a download URL.

Every download is verified against the release's .sha256 sidecar, and a checksum that is missing, unfetchable, or mismatched fails the step — the install never degrades to an unverified binary. Releases before v0.9.1 predate the sidecars and so cannot be installed this way.

Linux and macOS runners (x86_64/aarch64) are supported. Windows is not supported by the action yet, though fledge does publish fledge-windows-x86_64.exe in every release for direct download.

outputs:
  version: # the release tag that was installed
  path:    # full path to the installed binary

Quick start

Already have a project? cd into it, fledge auto-detects the stack:

fledge run test       # runs your language's test command
fledge run build      # same for build
fledge run test -- --release    # pass extra args through to the command after --
fledge review         # AI code review against the default branch
fledge review --with-model ollama:gpt-oss:120b-cloud,ollama:qwen3-coder:480b-cloud
              # multi-model panel, parallel critiques on the same diff

Starting fresh? Scaffold from a template:

fledge templates init my-app --template rust-cli     # built-in
fledge templates init my-app --template user/repo    # any GitHub repo
fledge templates init my-app                         # interactive picker

Switch AI providers without editing config:

fledge ai use                                  # interactive picker (live Ollama model list)
fledge ai use ollama qwen3-coder:480b-cloud    # scriptable
fledge ai status                               # show active provider/model and where each value came from

The six pillars

Pillar	Commands	What it does
Scaffold	templates (init, create, list, search, validate, publish)	Start a project from a template, local or remote
Run	run, lanes, watch	Task runner, composable pipelines, file-watch reruns
Spec	spec	spec-sync. Modules declare their contract, AI uses it as context
AI	ai, ask, review	Provider/model selection, spec-aware Q&A, single and multi-model code review
Ship	work, release, changelog	Branch and PR flow with AI-drafted bodies, version bump, tag, push
Extend	plugins, config, introspect, completions, doctor	Plugin protocol, global config, command-tree introspection, env health

That is the whole core. Anything else is a plugin.

Architecture

One Rust binary. clap sends each core command to its own module, and any verb it does not know is looked up as a plugin (fledge-NAME, native or sandboxed WASM). Tasks and lanes come from the project's fledge.toml, and every --json output uses the same envelope.

flowchart LR
    user["Developer or agent"] --> cli["fledge"]
    cli --> core["Core commands<br/>run, lanes, work, release, spec, ai, ..."]
    cli -->|"unknown verb"| plugins["Plugins<br/>fledge-NAME, native or WASM"]
    core --> toml[("fledge.toml<br/>tasks, lanes, work, release")]
    core --> tools["Project toolchain and git"]
    core --> net["GitHub API, LLM providers"]
    plugins --> reg[("plugins.toml<br/>registry and grants")]

The high-level design in docs/HLD.md covers command dispatch, fledge.toml, task and lane execution, the plugin system and protocol, work and release, hooks, and the trust model, with sequence diagrams for fledge run, fledge lanes run, and plugin install and invocation.

Plugins

Plugins extend fledge with community-built commands. Native plugins run as regular executables. WASM plugins run in a sandboxed Wasmtime runtime with no host access by default.

以上為 README 的開頭部分。其餘內容請閱讀原文。 檢視完整 README ↗