Agent sessions
Send a task to an agent and watch it work. Follow-up requests keep the original context.
A session holds one task with one agent in a team. The request, follow-ups, generated work, and cost stay together, so someone can reopen the task without reconstructing what happened.
Video placeholder
Record New chat, the scope and model choices, the agent’s progress, and one follow-up request on the result.
Start with the right scope
Open New chat. Before you send anything, check the four selectors in the composer because they determine where the session lives and how it runs.
- Team
- Limits the agents and resources you can choose for this task.
- Agent
- Selects the specialist, instructions, and tools used in the session.
- Model
- Sets the model and cost profile for this session only.
- Reasoning effort
- Controls how much reasoning the selected model uses before it answers.
Image placeholder
Show the team, agent, model, reasoning effort, attachment, voice, and send controls at readable scale.
Choose the agent before the model
Pick the specialist whose job matches the request, since that choice brings its instructions, tools, and team access into the session. After that, choose the lowest-cost model you trust to finish the work.
Hivy preselects the agent's default model. Change it when this specific task needs stronger reasoning or code work, and set the reasoning effort before sending the first message.
Give the agent a finish line
Name the deliverable and its audience, then include the source material and limits that affect the answer. Vague requests make the agent guess; a finish line gives you something concrete to review.
Build a Hivy Sheet comparing five competitors for the sales team. Include pricing, target customer, main differentiator, and a short note on the two strongest opportunities for us.
Attach images when the task depends on visual details. Voice input works better for requests that are faster to explain aloud.
Follow the work without reading every tool call
Hivy groups tool activity under the working section, which stays collapsed when you only need the answer. Expand it to inspect the searches, commands, file changes, plans, or delegated tasks behind that answer.
If the agent heads in the wrong direction, stop the active turn. Hivy keeps the session intact for a corrected follow-up.
An agent may pause with one to three structured questions. Choose an option, add a free-form answer when needed, then submit the answers so the same turn can continue.
Continue from the existing result
Keep revisions in the same session when they depend on an existing result. The agent can use the history and working environment rather than rebuild the output.
A different goal belongs in a new session, where unrelated history can't steer the answer and the session list stays easier to scan.
Review cost as the session grows
The composer shows running credits and estimated dollar cost. Check it after real tasks, then move routine work to a faster model when a stronger one doesn't improve the result enough to justify its price.
Share, rename, or archive the session
A specific name helps teammates find the session later. Add workspace members as participants when they need access, and archive finished work that no longer belongs in the active session list.
To bring it back, open Settings, choose Archived chats, and select Restore.
Sessions inherit the team boundary
A session can use only its team's agents. Sharing or reopening a session doesn't bypass the team boundary or participant access.