aisixteen/fantastic_team

Program: fantasticteam. The long install guide is docs/install.md.
Unattended team work on fantastic. You queue tasks; a team of AI workers takes them one by one, does the work on its own, and hands back finished results for you to review. You come back to done work, not to a chat.
It is not only for code. A task is any piece of work that can be described exactly and checked: code, documentation, research, triage, data, review, translation or ports.
## Install
You need git, a Rust toolchain with cargo, and Linux or macOS. gh is optional. CI unit-tests on Linux, macOS and Windows; the run was verified on Linux only (docs/install.md).
git clone https://github.com/aisixteen/fantasticteam
cd fantasticteam
sh scripts/build.sh
./target/release/fantasticteam --help
The script ends with two lines: sha256: and built: . The built: path is a versioned copy, target/release/fantasticteam- - , with the same bytes as the plain binary. scripts/build-github.sh prints the same two lines for fantasticteam-github- - .
There are two builds. The general build (Team, the default) gives workers stock exec. The GitHub build (Team GitHub) applies patches/github-exec.patch to a copy of the tree, so workers cannot reach forge CLIs, git push or credentials: sh scripts/build-github.sh makes target/github/release/fantasticteam-github. The github connector is in both builds.
The general binary is target/release/fantasticteam. There are no releases yet, so build from source. On macOS the build needs MACOSXDEPLOYMENTTARGET=14.0; .cargo/config.toml.example sets it under [env].
For the step-by-step version, with the GitHub App registration and troubleshooting, see docs/install.md. The builds are reproducible in intent: rust-toolchain.toml pins the toolchain, scripts/checksums.sh writes SHA256SUMS, and scripts/verify.sh checks a binary against it (docs/install.md, Reproducible builds).
## Configure
A team is a folder with a team.yaml. The file names the worker templates the team may start, the connectors it may use, the queue, and the credential store.
yaml
templates:
writer:
handlermodule: anthropicbackend
model: example-model
endpoint: https://api.example.com/v1
credentials:
store: credentials
ref: EXAMPLEKEY
priceinputpermtok: 1.0
priceoutputpermtok: 5.0
firstagent:
id: lead
template: writer
directivefile: lead.md
connectors:
git:
kind: teamgit.tools
directivefile: git.md
queue:
id: queue
credentials:
id: credentials
backend: env
refs:
EXAMPLEKEY: EXAMPLEKEY
templates: each is an agent template (model, endpoint, credential ref, prices per million tokens).
firstagent: the lead, made from a template, instructed by its directivefile.
connectors: GitHub, a plain git remote, or others, each with its own directive.
queue: where tasks wait.
credentials: the store the team creates when it has none. The values are never in this file; only the ref names are.
Each repo that the team serves can opt in with .github/team.yaml:
yaml
tasklabels: [team-ready]
paths: [src/, docs/.md]
build: cargo build
test: cargo test
review:
approvals: 1
approvers: [alice]
Every key is optional. An empty file gives the defaults: the label team-ready, any path, and one approval from any reviewer.