agent-taskbayOperator handbook
Configure Taskbay, secure human access, connect protected agents, and understand the supported feature set.
Taskbay has two independent authentication boundaries: people sign in to the console through OIDC, and the server calls agents with a service credential. A successful sign-in does not give Taskbay permission to call an agent, and an agent credential does not grant a person access.
These walkthroughs complement the complete upstream documentation, checked against source revision a52de4c.
| Goal | Start here |
|---|---|
| Understand every variable, default, secret and loading rule | Environment map, then Configuration reference |
| Secure a shared console and provision its first administrator | Secure Taskbay with OIDC |
| Connect an agent protected by OAuth, API key, bearer token or mTLS | Connect an OAuth-protected agent |
| Find each feature, its prerequisites and its limits | Capability map |
For a first local run, use the quickstart. For production topology, migrations, shared artifact storage and worker supervision, use Production deployment.
The site at taskbay.allsrc.dev is documentation. The console origin in deployment examples is console.example.com; set it to the HTTPS origin of your own running Taskbay application.
Created and maintained by Shashi Kanth G S at allsrc.dev. Visit shashikanth.me.
Quickstart
someone who wants to see Agent Taskbay work on their own machine. At the end you will have run the console, connected a sample A2A agent, sent it a task, approved an action as a reviewer, and seen the result recorded.
Environment map
Find every Taskbay runtime variable, understand secret boundaries, and apply configuration consistently.