Skip to content

behavior.md

Latest commit

 

History

History
37 lines (24 loc) · 2.76 KB

behavior.md

File metadata and controls

37 lines (24 loc) · 2.76 KB
Raw

Monitoring behavior

What the agent receives

[t3poll] New activity on https://github.com/owner/repo/pull/123
Check the PR for updates and continue the task.

Comment bodies and CI logs are not copied into the message. The agent fetches what it needs. t3poll does not merge, push, approve, or post comments.

Polling and lifetime

An optional CLI --interval 30, or MCP intervalSeconds: 30, changes the poll interval. The default is 60 seconds; the accepted range is 15–3600 seconds. Repeating watch for the same PR and destination returns the existing watch without changing its interval or expiration. Stop and watch again to reset it.

Delivery and recovery

  • The first read establishes a baseline. Existing feedback does not cause a notification.
  • New or edited comments/reviews, terminal CI results, head commits, and closure/merge are detected. Check reruns and legacy commit statuses are included; queued/running checks stay quiet.
  • Changes found in one poll become one notification. Changes accumulate while the destination is starting or awaiting input/approval.
  • Watches finish after the final closure/merge notification, stop on request, or expire after 24 hours. Expiration cancels remaining unsent work.
  • T3/GitHub failures retry with backoff. list shows polling and delivery errors. A timed-out dispatch retains the same command and message IDs for retry.
  • lastDelivery means T3 accepted the command. It does not mean the agent completed the work. Provider failures remain in T3; t3poll does not blindly send the message again.
  • Stopping cancels unsent work. An HTTP request already in flight may still be accepted and run.
  • There is no startup service. After a reboot or worker crash, calling watch or list restarts saved active watches. The machine must be awake and T3 available for delivery.

State lives in ~/.local/share/t3poll, or T3POLL_HOME. All clients using the same directory share one worker. Keep that directory private. The worker writes startup/crash diagnostics to worker.log; ordinary unchanged polls are silent.

See compatibility and limitations and why polling comes before webhooks.

Busy threads

GitHub polling continues every 60 seconds by default. Running threads receive the same short notification immediately through T3's normal message command. With Codex 0.153.2, this steers the active turn. Idle threads start a new turn.

Threads starting up or awaiting approval/input are checked again every 15 seconds. Changes accumulate until they can accept input. Watches still expire after 24 hours, including unsent notifications. Unknown or errored session states block delivery.

Delivery uses the provider's normal input handling; see compatibility limits.