Assistant
The assistant is a chat agent on one project, for you. It can read the project and propose writes. It does not apply mutations until a human approves. That gate is permanent — not a beta safety switch.
Plan: Studio+.
Open it from the project section nav. It is not the project chat and not Ask.
| Surface | Job |
|---|---|
| Ask | Answer from knowledge. Cites. Never writes. |
| Assistant | Sitting with tools. Reads now; writes as proposals. |
| Chat | People talking to people. |
Sittings
Section titled “Sittings”A sitting is a burst of turns — private to you, not shared project chat, and not knowledge-base memory.
- InHive reuses the current sitting if you were active today and within a few hours.
- New starts a clean slate.
- You can hide old sittings (list them from the assistant disclosure). You cannot hide one that still has pending proposals.
If it should last, Save this answer. Do not treat sitting history as the hive’s memory.
What it may do
Section titled “What it may do”- Read — search knowledge, open tasks, pull a handoff. These run immediately. You will see the reply pause and continue when it looks something up.
- Write — create or update tasks, features, decisions, comments. These become proposals.
On a proposal:
- Read the kind mark (task, feature, or decision), the status chip, and the arguments (and the grounding quote, if it came from a transcript).
- Edit if they are almost right (they are re-checked).
- Approve or Reject. Approval runs as you, so activity and notifications look like ordinary work. A reject reason teaches the next pass.
If someone edited the task after the proposal was written, approve is refused so you do not overwrite newer work. Refresh and propose again if it still applies.
When a sitting proposes a new deliverable or goal and the tasks (or a decision) that belong to it, they appear as a pack. Approve pack creates the deliverable or goal first so the tasks land on it. You can still approve a single card.
Do not approve a write you would not type yourself.
From agents
Section titled “From agents”Coding agents connected through Agents can change acceptance criteria, the primary deliverable on a task, an accepted decision, or org knowledge. Those writes do not apply immediately — even when Account write mode is auto. They wait here under From agents, and on Plan → Decisions, until you or a manager approve them. You can approve a proposal your own agent queued.
Managers can see how long that queue sits, and how often proposals are approved without an edit, on Organization settings → AI → Oversight health. That card measures review load. It does not turn on any autonomy.
Propose from knowledge
Section titled “Propose from knowledge”Managers can start an onboarding pack with Propose from knowledge on this page. Same proposal list, different trigger: read the KB, draft features / tasks / open decisions. Files stay on Documents; the button is here.
Suggest with AI
Section titled “Suggest with AI”On a new task, Suggest with AI pre-fills the form from project context. You still press create. Available on Studio, Team, and Enterprise — configure a provider key in AI settings first.
Digests
Section titled “Digests”Project and standup digests summarise the activity log. They do not write hive data.
On a project, open Activity. The digest (and handoff) stay on top; the full log is underneath.
- Project digest — on demand, what changed.
- Task brief — in the task drawer, under the description (hidden while you edit the title or description). Distill in the ⋮ menu folds the description and comments into one current set of requirements. The hive remembers that brief: the next person to open the task sees it without spending tokens again. If the description or a comment changes, Distill again from the same menu. It does not overwrite the written description. A nearly empty description and thread is not distilled.
- Standup — weekday morning, hive timezone, to managers and project members (in-app + email).
- Handoff — I-PASS order: status line, goals and deliverables, done so far (verified vs declared), next ready actions, open questions and blockers, gotchas, where to work (Studio+ / Ask). See Knowledge.
Related
Section titled “Related”Knowledge · Automations · AI settings · Documents
Review a change together
Section titled “Review a change together”A Proposed change can connect one agreement with updates to existing work. Choose Review change to see the meeting source (when present), the agreement to record, and before-and-after values for each affected task or feature. Edit lets you correct the wording; Refresh review shows the revised comparison before approval.
Approve this change records the agreement, applies the work updates and preserves their links together. It can also replace an earlier decision, which remains in history as superseded. If work or source access changed while you reviewed it, refresh the review. An unsuccessful application does not leave half the change applied. Rejection leaves the plan untouched. After approval, See change in Plan History opens its combined record.
This review supports new tasks and changes to task/feature names, descriptions and acceptance criteria. Existing task memberships stay intact. New-feature packs, assignments, status changes and other individual actions remain available through their usual controls. Grouped changes have their own review and are excluded from bulk approval.