Summary

This PR fixes cron outbound delivery so agent identity is preserved end-to-end when sending through deliverOutboundPayloads. Cron-generated messages were being delivered without the configured agent persona (name/avatar/emoji), which caused anonymous/default bot presentation in Slack.

Problem

Cron delivery for isolated agent runs was successfully producing outbound payloads, but those messages appeared as the default app/bot identity instead of the configured agent identity. In practice, this made scheduled agent reports look like generic system posts rather than messages from the intended agent persona.

Root cause

Identity fields were not threaded through the outbound delivery plumbing:

• deliverOutboundPayloads did not accept/pass username, icon_url, icon_emoji
• createChannelHandler / createPluginHandler did not forward identity values into channel adapters
• Cron runner (src/cron/isolated-agent/run.ts) did not resolve and attach identity for outbound structured delivery

Solution

I implemented minimal, targeted plumbing across the delivery path:

// src/infra/outbound/deliver.ts
export async function deliverOutboundPayloads(params: {
  ...
  username?: string;
  icon_url?: string;
  icon_emoji?: string;
})

These fields are now forwarded into:

• createChannelHandler(...)
• createPluginHandler(...)
• sendPayload, sendText, and sendMedia adapter calls

Cron path now resolves and supplies identity:

const agentIdentity = resolveAgentIdentity(cfgWithAgentDefaults, agentId);
const identityAvatar = agentIdentity?.avatar?.trim();

await deliverOutboundPayloads({
  ...,
  username: agentIdentity?.name?.trim() || undefined,
  icon_url: identityAvatar?.startsWith("http") ? identityAvatar : undefined,
  icon_emoji: !identityAvatar?.startsWith("http")
    ? agentIdentity?.emoji?.trim() || undefined
    : undefined,
});

Slack outbound/send was also updated to accept and pass customize fields to chat.postMessage when present.

Before / After

• Before: cron outbound messages often appeared as default bot identity (anonymous/generic)
• After: cron outbound messages carry configured agent identity (name + avatar/emoji) when available

Edge cases considered

• Identity fields are optional and only applied when present
• icon_emoji is only sent when icon_url is absent
• Non-HTTP avatar values do not incorrectly populate icon_url
• Non-Slack channels remain unaffected unless they choose to consume the new optional context fields

Testing

• npm run lint passes cleanly
• Scope intentionally minimal (5 files)
• Existing delivery behavior remains unchanged except identity threading

AI Disclosure

This PR was prepared with AI assistance. I reviewed the code path, implemented the changes, and validated lint locally before opening the PR.

Greptile Overview

Greptile Summary

This PR adds agent identity threading (name, avatar, emoji) through the outbound delivery pipeline to fix cron-generated messages appearing as the default bot identity instead of the configured agent persona in Slack.

Key changes:

• Added optional username, icon_url, and icon_emoji parameters to ChannelOutboundContext type
• Threaded these parameters through deliverOutboundPayloads, createChannelHandler, and createPluginHandler in deliver.ts
• Updated Slack outbound adapter (sendText and sendMedia) to accept and forward identity fields to sendMessageSlack
• Modified sendMessageSlack to conditionally include identity fields in chat.postMessage calls
• Cron isolated agent runner now resolves agent identity and supplies it during outbound delivery

Implementation quality:
The implementation correctly ensures mutual exclusivity between icon_url and icon_emoji (Slack only accepts one). The avatar URL validation using startsWith("http") is simple but effective. All parameters are optional and only applied when present, maintaining backward compatibility. The changes are minimal and focused, affecting only 5 files.

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The changes are minimal, well-scoped, and follow a clear pattern. The identity fields are optional and properly threaded through the delivery pipeline without affecting existing behavior. The mutual exclusivity logic for icon_url and icon_emoji is correct according to Slack's API requirements. Other channels properly ignore these optional fields. No breaking changes or risky refactoring.
• No files require special attention

_{Last reviewed commit: 0bc773b}