Skip to content

fix(web): a scheduled run reports to the person who deployed it (CL-8580) - #940

Merged
TheGreatAxios merged 3 commits into
mainfrom
cl-8580-cron-reply-to-person
Sep 18, 2026
Merged

TheGreatAxios merged 3 commits into
mainfrom
cl-8580-cron-reply-to-person

Conversation

@TheGreatAxios

Copy link
Copy Markdown
Contributor

Summary

  • A cron-scheduled agent run's mail body previously carried no reachable sender, so the ticker's mail address (cron@<domain>) has no mailbox and the agent's reply is silently dropped by the hub.
  • The scheduled run's body now names the deploying person's mailbox address and asks the agent to reply there.

Changes

  • apps/web/src/agent-deploy.ts: scheduleAgentRun resolves the deploying person's mailbox address (<refId>@<tenantDomain>, same shape threads-api.ts builds a person participant's address from) via the existing session probe, and passes it into a new buildScheduledRunBody helper that asks the agent to mail its result there (as a single-item to list) with a short subject. Falls back to a bare reply instruction if the session probe comes back empty — never fails the deploy over it.

Testing

  • bun test apps/web/src/agent-deploy.test.ts
  • bun run check

@linear-code

linear-code Bot commented Sep 18, 2026

Copy link
Copy Markdown

CL-8580

@TheGreatAxios
TheGreatAxios merged commit 6a2d65e into main Sep 18, 2026
4 checks passed
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