Galangal Orchestrate
Turn AI coding assistants into structured development workflows.
Galangal wraps Claude Code CLI to execute a deterministic, multi-stage development pipeline with approval gates, validation, and automatic rollback.
Why Use This?
Instead of open-ended AI coding sessions, you get a structured workflow:
- PM - AI writes requirements, you approve before code is written
- Design - AI proposes architecture, you approve the approach
- Dev - AI implements according to approved specs
- Test/QA/Review - Automated validation with rollback on failure
- Docs - AI updates documentation
If anything fails, the workflow rolls back with context about what went wrong.
Quick Start
# Install (lean core)
pip install galangal-orchestrate
# Optional: semantic mistake tracking (adds sentence-transformers/torch, ~hundreds of MB)
pip install "galangal-orchestrate[full]"
# Initialize in your project
cd your-project
galangal init
# Start a task
galangal start "Add user authentication with JWT"
# Run non-interactively (CI/scripts, no TUI)
galangal start "Fix the login bug" --type bugfix --headless
# Check status / resume
galangal status
galangal resume
Requirements
- Python 3.10+
- Claude Code CLI (
claudecommand) - Git
Commands
| Command | Description |
|---|---|
galangal init |
Initialize in current project |
galangal start "desc" |
Start new task |
galangal status |
Show task status |
galangal resume |
Continue active task |
galangal list |
List all tasks |
galangal index stats |
Show task index DB stats |
galangal index rebuild |
Rebuild task index from task folders |
galangal index migrate-artifacts |
Import legacy artifact files into DB and delete file copies |
galangal index compact-done |
Keep only PLAN.md and SUMMARY.md in tasks/done/* |
galangal complete |
Finalize & create PR |
Interactive controls during execution:
^QQuit/pause^IInterrupt with feedback^NSkip stage^BGo back^EPause for manual edit
Galangal Hub
Monitor and control workflows remotely across multiple machines.
# Deploy hub server (Docker)
docker run -d -p 8080:8080 \
-e HUB_USERNAME=admin \
-e HUB_PASSWORD=your-password \
-e HUB_API_KEY=your-api-key \
-v galangal-hub-data:/data \
ghcr.io/galangal-media/galangal-hub:latest
# Enable in your project (.galangal/config.yaml)
hub:
enabled: true
url: ws://your-server:8080/ws/agent
api_key: your-api-key # Must match HUB_API_KEY on server
See Hub Documentation for full setup instructions.
Documentation
| Topic | Link |
|---|---|
| Getting Started | docs/getting-started.md |
| Configuration | docs/guide/configuration.md |
| Workflow Stages | docs/guide/workflow-pipeline.md |
| Hub (Remote Control) | docs/hub/README.md |
| Troubleshooting | docs/troubleshooting.md |
| Architecture | docs/local-development/architecture.md |
Task Types
| Type | Stages | Use Case |
|---|---|---|
| Feature | All stages | New functionality |
| Bug Fix | PM → PREFLIGHT → DEV → TEST → TEST_GATE → QA → REVIEW → SUMMARY | Fixing bugs |
| Refactor | PM → DESIGN → PREFLIGHT → DEV → TEST → TEST_GATE → REVIEW → SUMMARY | Code restructuring |
| Chore | PM → PREFLIGHT → DEV → TEST → TEST_GATE → REVIEW → SUMMARY | Config, dependencies |
| Docs | PM → DOCS → SUMMARY | Documentation only |
| Hotfix | PM → DEV → TEST → TEST_GATE → SUMMARY | Critical fixes |
License
MIT License - see LICENSE file.
1 maintainer
Metadata
1 maintainer
Release files for galangal-orchestrate 0.58.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| galangal_orchestrate-0.58.0.tar.gz | 530.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| galangal_orchestrate-0.58.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.0 MB
Release files / galangal_orchestrate-0.58.0.tar.gz
| Download URL | galangal_orchestrate-0.58.0.tar.gz |
|---|---|
| Size | 530.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1ea85bf1135204a3c1e9d3a8f0d4ac3f2513e418dd1d96b29c65b0264e3f4d44
|
|
BLAKE2b-256 checksum How to use checksums |
e07d52ef385f0f294b05bc8a789d60b763f236b90614a8b42a90eb0188aa3a5b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 9, 2026.
Transparency logRelease files / galangal_orchestrate-0.58.0-py3-none-any.whl
| Download URL | galangal_orchestrate-0.58.0-py3-none-any.whl |
|---|---|
| Size | 507.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
65755bda3bea659b6dab103cc51ad6b198a62e145761387f00cd141c5049c49f
|
|
BLAKE2b-256 checksum How to use checksums |
e536bf11cc379d6a1ade7bfd6984ab7f15f70be6b67ef50505104179c45f0a6d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 9, 2026.
Transparency log
