Not available yet
Slack context in vidbyte-cli
No released or main vidbyte-cli reads Slack. The Slack sign-in and channel-history reads this page used to describe were designed but never released; pass exported messages as a file instead.
What is not available
None of the following exists in the released CLI (0.3.4) or on the CLI's main branch.
No Slack sign-in — No CLI reads
VIDBYTE_SLACK_CLIENT_ID, so setting it changes nothing.No connections command — The planned
connections login slackflow, which used Slack user scopes rather than bot scopes, was never merged; running it ends in "No such command".No channel reads — The planned channel-history read and its page-size option (such as
--limit 25) do not exist in any release.Sending is a different feature — The released CLI (0.3.4) can post an agent's result to a Slack incoming webhook saved with
vidbyte-cli slack add. That sends output only and never reads Slack.
Give an agent Slack context today
Save the messages the agent should read to a file, then pass the file with --files.
Save the messages as a file
Copy the thread or channel messages you need into a
.txtor.mdfile.Pass the file to an agent
The Suggestion Agent reads each
--filespath as context; it accepts.txt,.md, and.jsonfiles, and you can repeat the option. This works in the released CLI (0.3.4).Context from a file
bashvidbyte-cli agents suggest run --goal "Ship the billing page this week" --files context.md