How Hive works
Hive collects work from external sources and routes it into local feeds.
The model
- A source reads from a provider, a feed, a command, or a local webhook.
- A flow connects sources to filters and destinations.
- A workspace is the Inbox view of one flow.
- A feed is a list of items produced by a flow.
- An action starts a repository session or agent workspace chat, runs a command, publishes a message, or copies text.
- A notify node raises a system banner or an in-app toast.
- A launch node starts a repository session or an agent workspace chat for each item, without an action.
Hive stores item history and read state locally. Changing a flow recalculates feed membership without losing that history.
Work with feed items
Use Feed options to sort a feed, refresh its sources, mark its items as read, or select multiple items.
In selection mode, choose items and use Copy contents to copy one readable block in feed order. Copy with action applies a configured clipboard action to every selected item.
Select Create session to open one editable New Session form with context from every selected item. Choose Repository for a coding session or Agent workspace for a chat that does not need a checkout. A repository session appears in each selected item's detail pane. An agent workspace chat appears in Chats, receives the same generated prompt, and appears in each selected item's detail pane.
A prompt larger than 32 KiB shows a warning in the form. Hive writes the full text to a private temporary file and asks the agent to read and delete it instead of passing the text as a command argument.
Selections remain active while you search, filter, sort, copy, or cancel the New Session form. Use Cancel selection to clear them.
The app areas
Inbox is one of Hive's three main areas. See the feature overview for the core Inbox, Code, and Chats capabilities.
Configure Hive
Use the flow editor and Settings screens, edit the YAML files directly, or ask the built-in Hive workspace in Chats.