Skip to content

fix: preserve original Slack source context across channel continuations#7

Closed
ashpreetbedi wants to merge 1 commit intomainfrom
coda/slack-origin-context
Closed

fix: preserve original Slack source context across channel continuations#7
ashpreetbedi wants to merge 1 commit intomainfrom
coda/slack-origin-context

Conversation

@ashpreetbedi
Copy link
Copy Markdown
Contributor

Summary

  • preserve original Slack source metadata in the AgentOS Slack interface session state
  • teach the leader prompt to prefer original Slack source context over the current continuation thread
  • add a Slack-context eval and update Slack docs/README to describe the behavior

Testing

  • python -m compileall /repos/coda/worktrees/slack-origin-context/app /repos/coda/worktrees/slack-origin-context/coda /repos/coda/worktrees/slack-origin-context/evals

Context

This fixes cases where a task starts in one Slack channel/thread (for example #chitchat, channel C04A0C09VEJ, thread 1775118051.885189) and is later continued from another channel/thread, mention, or share. The original source channel/thread metadata now stays pinned to the session instead of being replaced by the continuation context.

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