Conversations
A conversation is Junior’s durable unit of work. In Slack, one conversation usually maps to one thread.
Conversations and Turns
Section titled “Conversations and Turns”A conversation contains messages, execution state, and the history needed to continue work. A turn starts with a request and ends with a reply, an intentional no-reply, or a failure.
A turn may pause and resume without starting a new conversation. Junior can also shorten its working history to fit the available context without changing the Slack transcript.
Slack Behavior
Section titled “Slack Behavior”- Mention Junior to start work in a channel thread.
- Follow-ups stay in the same conversation after Junior joins.
- Replies return to the same thread.
- Keep one task per thread. Start a new thread when the goal changes.
- Use public channels for shareable work and DMs for private work.
Messages are processed in order. A new mention can steer active work at the next safe point. Other messages wait for the current turn to finish.
Visibility
Section titled “Visibility”Conversation privacy follows its Slack destination:
- public channels follow workspace and dashboard access rules
- private channels and DMs stay private
- missing visibility is treated as private
Child work, generated files, and plugin records inherit the conversation’s visibility. Transcript access does not grant connected-account access or task ownership.
Context
Section titled “Context”Junior uses the current thread, selected skills and files, and results from the active work. It does not pull private context from unrelated conversations.
An installed Memory plugin may add scoped recall. It does not provide unrestricted access to every conversation.
Next Step
Section titled “Next Step”Read Execution Model for pauses and retries, or Data & Privacy for storage and access rules.