Hive

Coordination for Agents. Attention for a Human. A team of AI agents can work in parallel. A human cannot give every thread attention at once. Hive connects the Weave’s agents across machines and turns the moments that need my judgement into a focused queue. Hive Attention brings the brief into Slack, records my response and returns it to the originating work context.

Agent workA concrete decision needs a human.
Human attentionRead the brief. Record the response.
Agent workRestore context. Apply the decision.

Project, work and artifacts stay attached to the intervention and its return.

The question is: why did this need me?

The Weave is the AI engineering team I designed and lead. Its agents plan, write, review and repair software. Hive is the service that connects them. It delivers the handoffs between agents and brings me the decisions that need human judgement.

A useful request arrives with enough context to answer it: what to decide, what to inspect and what happens next. Once I answer, I should not have to find the right terminal and explain the project again.

1 active intervention per human; the rest can wait without holding an agent turn open

Explore the attention workflow

Project: Hákon Freyr Gunnarsson
Sheet: Detail K
Title: Hive
Scale: N.T.S.
Rev: 2026-10

Attention, returned

A structured Slack surface closes the human part of the loop. Follow one intervention from an agent’s request to a recorded response and a return to the work.

Illustrative reconstruction of a real engineering intervention. Wording is paraphrased; this is a portfolio walkthrough, not a Slack screenshot or a connected queue.

Intervention briefQueued

Keep the attention queue current

Do: Approve one focused repair and an independent review.
Context: A deleted Slack card must stay retired. The Home queue must still reflect later changes to that intervention.
Unblocks: The engineer can repair the queue refresh; a different agent can verify the result.

Queue the ask

The agent binds the intervention to its work and saves a complete brief: the action requested, the context, the artifacts and what the answer will unblock. Its current turn can end.

Step 1 of 5

Queue the ask. The agent binds the intervention to its work and saves a complete brief: the action requested, the context, the artifacts and what the answer will unblock. Its current turn can end.

Display in Slack. Hive renders the brief as native Slack blocks. One direct-message card announces the intervention; later changes update that card. The app’s Home tab gathers the queue. Displaying an item does not make it active.

Record a response. Take next selects the oldest eligible intervention and opens its decision modal. The human can resolve, defer or cancel it. Answer this one is an explicit, recorded override. Only one intervention can be active.

Return to context. The response and the intent to return commit together. Ordinary Hive delivery carries the verbatim answer and the saved packet to the originating work context. Recording a response and delivering it are separate events.

Report the outcome. The receiving agent restores the right repository, work and artifacts, acts within its existing permissions, and reports an outcome. Processed means an outcome was reported. The work still needs its own verification, review and publication.

Project: Hákon Freyr Gunnarsson
Sheet: Detail K.1
Title: Attention, returned
Scale: N.T.S.
Rev: 2026-10

The work stays attached

Preserving context means returning to the right work with the evidence needed to continue. The live demonstration used a fresh turn with the saved work packet.

Two explicit return paths

Return to the captured session: Same session, where supported. Hive captures the session and its working directory, then checks both again before delivery. If that route becomes unavailable, it fails visibly and needs an explicit reroute.
Return with the work packet: Fresh turn, restored work context. A new turn receives the saved project, work, artifacts and human response. The agent must restore that context before acting. This is the mode used in the recovered live demonstration.

Recording a decision does not complete the work

The response becomes a durable continuation through Hive’s ordinary delivery machinery. Retries carry the same response identity. A changed brief invalidates an older decision form, and a blocked or failed return remains visible.

An approval is recorded data. It does not grant merge, deployment or spending authority. The receiving agent still works within its existing permissions and the project’s review and delivery rules.

Across the Weave

Conversation: Slack is where the team discusses work. Hive routes an explicit handoff to the named agent, across machines and model providers.
Work and decisions: Linear holds the durable work ledger. Git holds the code. Hive carries the deliveries between the people, agents and tools that move that work forward.
Human judgement: A product choice, a visual selection or a blocker that no peer can resolve becomes a concrete intervention. Routine progress and peer review stay with the team.

One broker, outward connections

The central broker owns Slack and a durable SQLite ledger. A small edge process on each agent’s machine connects outward and handles local sessions. Deliveries can be retried; Hive records their status and the agent’s outcome rather than claiming execution happens exactly once.

Meet the Weave

Project: Hákon Freyr Gunnarsson
Sheet: Detail K.2
Title: The work stays attached
Scale: N.T.S.
Rev: 2026-10

Built, tried, bounded

Hive Attention has moved from a specification to an implemented queue and a live Slack interaction. The evidence supports a precise claim: a human response can return to an agent with its work context.

Demonstrated on the live fleet: The command-line pilot on 15 October 2026 proved the queue and return path. A real engineering intervention then followed the Slack selection and response path early on 16 October: the saved response returned to Ariadne, the delivery reported an outcome, and the card’s stored state reflected the processed return.
Implemented in the public repository: The durable queue, source binding and return paths are implemented. The Slack extension renders direct-message cards, the app Home queue and decision modals using native Slack components. The Home queue, defer and cancel controls are implemented; the recovered live record does not establish a separate demonstration of each control.
The wider design: The Attention specification defines explicit switching, durable commands, revision checks and visible return failures. Priority scheduling, calendar projection, focus inference and autonomous approvals remain outside this release. Returning into every desktop agent chat is not demonstrated; the specification leaves the Mac desktop delivery path for later work.

Evidence checked on 16 October 2026 against the public source, change history and read-only live delivery records. The reconstruction uses the shape of the implemented interface and a paraphrased public engineering case. Private Slack content is omitted. No original Slack capture is presented.

Inspect the work

Hive repositoryThe coordination service and its operating model.
Hive Attention specificationThe queue, return contract and Slack amendment.
Slack implementationNative blocks, Home queue and decision modal.
Context return implementationResponse delivery and the meaning of processed.
Slack extension historyThe implemented change and its review history.

Materials

TypeScript
Bun
SQLite
Slack Block Kit
Claude
Codex
Tailscale

Back to the cover sheet

Project: Hákon Freyr Gunnarsson
Sheet: Detail K.3
Title: Built, tried, bounded
Scale: N.T.S.
Rev: 2026-10