Skip to content

feat: return sent message metadata#81

Merged
AmethystLiang merged 3 commits intostablyai:mainfrom
scottatron:wonsley/return-send-metadata
Apr 28, 2026
Merged

feat: return sent message metadata#81
AmethystLiang merged 3 commits intostablyai:mainfrom
scottatron:wonsley/return-send-metadata

Conversation

@scottatron
Copy link
Copy Markdown
Contributor

Summary

  • return posted channel/message metadata from agent-slack message send
  • build permalinks for posted messages when the workspace URL is known
  • document and test the new output shape

Test Plan

  • bun test test/message-send.test.ts test/url.test.ts

Wonsley and others added 3 commits April 17, 2026 01:48
Expose posted channel_id and ts for message send, plus permalinks when the workspace URL is known.

Co-Authored-By: Wonsley <wonsley@tron.haus>
Rename `url` to `permalink` to match Slack's own vocabulary, drop the
`workspace_url` echo from output, and only include `thread_ts` when the
send actually targeted an existing thread (previously it was defaulted
to the posted `ts` on root messages, which misleadingly implied the
message was a threaded reply).

Co-authored-by: Orca <help@stably.ai>
Copy link
Copy Markdown
Contributor

@AmethystLiang AmethystLiang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR, @scottatron! I pushed one follow-up commit to tighten the return shape: renamed urlpermalink to match Slack's own vocabulary, dropped the workspace_url echo from output, and made thread_ts present only when the send actually targeted an existing thread (it was being defaulted to ts on root messages, which could be read as 'this was a threaded reply'). This'll ship in the next release.

@AmethystLiang AmethystLiang merged commit b27b0b3 into stablyai:main Apr 28, 2026
1 check 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.

2 participants