talon gateway serve-webhook --port 7070Submit a buffered task:
curl -X POST http://127.0.0.1:7070/tasks \
-H "Content-Type: application/json" \
-d '{"requester":{"externalSessionId":"local-session","externalUserId":"local-user","externalUserLabel":"Local User"},"taskInput":"summarize runtime status"}'Submit a task and stream live output in the same response:
curl -N -X POST http://127.0.0.1:7070/tasks/stream \
-H "Content-Type: application/json" \
-d '{"requester":{"externalSessionId":"local-session","externalUserId":"local-user","externalUserLabel":"Local User"},"taskInput":"summarize runtime status"}'The stream uses Server-Sent Events with named events such as
output.assistant_turn_delta, output.result, progress, gateway.result,
and a terminal done event. Existing task history remains available through
GET /tasks/:taskId/events.
The Feishu/Lark adapter is loaded as an optional gateway plugin so the core CLI
runtime stays lightweight. Install the Lark SDK only in workspaces that run this
adapter. This is a formal chat entry point into the same runtime used by
talon tui, not just an adapter demo:
pnpm add @larksuiteoapi/node-sdktalon gateway serve-feishu --cwd .Configuration files:
.auto-talon/gateway.config.json.auto-talon/feishu.config.json
Inspect adapters:
talon gateway list-adaptersFeishu schedule commands:
/schedule create 1分钟后 | say hello
/schedule create cron 0 17 * * 5 | weekly review
/schedule preview cron 0 17 * * 5
/schedule show <schedule-id-prefix>
/schedule edit <schedule-id-prefix> cron 0 9 * * *
/schedule runs <schedule-id-prefix>
Schedule timing validation is explicit. Invalid cron expressions, ambiguous timing fields, or unavailable declared toolsets fail with a visible error instead of falling back to another model, channel, or execution path.