This documentation is intended for three audiences:
- Orchestrator / Agent developers: map your workflow (DAG) into ExecGo
TaskGraph, and handle failure + retry semantics correctly - Platform / Ops engineers: deploy ExecGo into your own Docker Compose or Kubernetes cluster (including persistence and health checks)
- Client developers: integrate with ExecGo via HTTP using Go/Java/Python (submit graphs, poll status, read results)
If you already read the root README.md quick start, continue from the sections below.
- Integration:Go example
- Integration:Java example
- Integration:Python example
- Integration:Node.js + TypeScript example
- Reference:API endpoints & errors
- Reference:Task DSL (task model & validation)
- Reference:executor parameters & built-ins
Docs reflect the current repository behavior. When upgrading ExecGo, double-check TaskGraph submission/validation and executor parameter compatibility.