Skip to content

Run Operator ambient loop only while fleet active#374

Merged
edwin-zvs merged 1 commit into
mainfrom
operator-ambient-active-loop
Jun 6, 2026
Merged

Run Operator ambient loop only while fleet active#374
edwin-zvs merged 1 commit into
mainfrom
operator-ambient-active-loop

Conversation

@edwin-zvs

Copy link
Copy Markdown
Contributor

Summary

  • Change the Operator ambient loop default cadence from 5 minutes to 60 seconds.
  • Gate ambient ticks on fleet activity: every interval, Operator checks for an active non-Operator, non-terminal session and only emits the ambient tick when one exists.
  • Treat recent PTY activity, recent transcript/event activity, and brand-new running sessions without timestamps as active.
  • Stop ticking when all sessions are idle/terminal/inactive instead of falling back to a 5-minute idle loop.

Tests

  • cargo test -p agentd-adapter-zarvis ambient
  • cargo build
  • git diff --check

@edwin-zvs
edwin-zvs merged commit 40ec9f6 into main Jun 6, 2026
1 check passed
@edwin-zvs
edwin-zvs deleted the operator-ambient-active-loop branch June 6, 2026 17:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant