Executor vs. Agent Client
Executor and Agent Client can both run on a user’s computer or inside a private network. They solve different problems, plan work in different places, and use different identities.
Core differences
Section titled “Core differences”| Dimension | Agent Client | Executor |
|---|---|---|
| Main purpose | Let a local agent discover and invoke limited capabilities as an authorized business subject | Let a local or private runtime claim a Job that BailingHub has already created |
| Who plans | The local agent | The Hub has already selected a target and dispatched the task |
| Identity | A revocable Agent Session created by browser authorization and bound to a business subject and allowed routes | A target-scoped Executor Token that identifies a worker node, not an end-user business identity |
| Interaction | The user holds an ongoing local conversation and can switch connections | The worker claims, heartbeats, executes, and reports by Job ID |
| Capability source | A restricted workspace projection of tools and rules | The execution target configuration and task envelope |
| Typical use | A desktop agent operates orders, staff, or tickets | Code review, local files, private scripts, or a specialized runtime |
Choose Agent Client when
Section titled “Choose Agent Client when”The user wants to state a goal in a local agent and let the local model choose multiple business tools. The user confirms identity on a business-side authorization page. BailingHub still enforces capability projection, approval, idempotency, invocation, and audit.
Choose Executor when
Section titled “Choose Executor when”BailingHub has already created a task that must run in a local or private environment the Hub cannot reach directly. An Executor is a task worker. It does not inherit a browser login session, and its token must not be treated as authority to represent any business user.
What must not be shared
Section titled “What must not be shared”- Tokens: an Agent access token and an Executor Token have different meanings.
- Configuration: an Agent Client connection/workspace is not an execution target.
- Audit subjects: one records an authorized business identity; the other records the worker that claimed a task.
- Authorization: an Executor Token cannot replace the business subject or final authorization required by a tool call.