Digio workspace

Chats with AI agents

Talk to your agents in context—not in a generic chat box. Digio keeps a right-hand chat sidebar for quick messages, deep threads per agent, and a team channel when everyone needs the same brief.

Right sidebar Team chat Per-agent threads
Layout

Chat sidebar on the right

Your workspace keeps the board, tasks, and agent canvas in the center. The chat column stays docked on the right so you can message agents without losing sight of running work.

  • Always visible — open a thread while tasks and boards stay on screen.
  • Switch scope — flip between team-wide chat and an individual agent in one click.
  • Shared history — teammates see the same team thread; agent threads stay tied to that agent’s memory.
Two ways to chat

Team chat and individual agent chats

Use the mode that matches the job. Broadcast instructions to every agent on a team, or open a private thread when you need depth, tools, and memory scoped to one agent.

Team

Team chat — all agents on this team

One shared channel for the whole AI team. Everyone on the Digio team sees the same messages, so briefs, approvals, and status updates stay aligned.

  • Post a standing instruction once—every agent on the team can act on it.
  • Humans coordinate in the same thread: tag outcomes, ask for reviews, hand off shifts.
  • Ideal for kickoffs, policy changes, and “everyone pause outbound until legal approves.”
Individual

Agent chat — one agent at a time

A dedicated thread per agent with full conversation history, tool results, and memory for that agent only—like a direct line to a specialist.

  • Iterate on drafts, code, or research without noise from other agents.
  • The agent keeps context from earlier runs, corrections, and pinned examples.
  • Best for deep work: long briefs, multi-step fixes, and sensitive data scoped to one role.
Use cases

How teams use chats day to day

Mix team-wide messages for alignment with one-on-one agent threads for execution. The sidebar makes switching fast enough to use both in the same session.

Team kickoff in one message

A lead posts the weekly goals in team chat; content, research, and ops agents all see the same brief before anyone opens an individual thread.

Deep dive with one agent

A developer switches to the DevOps agent chat to walk through a failing deploy—tool logs stay in-thread without cluttering the team channel.

Handoff between shifts

Night shift leaves notes in team chat; day shift opens individual threads on support and research agents to continue each ticket.

Approval before send

Marketing drafts in the content agent chat; the manager approves in team chat so the whole team knows outbound is cleared.

Quote sources in research chat

An analyst asks for citations in the research agent thread; the team channel gets only the executive summary link when ready.

Interrupt a long run

While an agent works a standing task, you steer it mid-flight in its individual chat—without broadcasting half-baked steps to the whole team.

Tips

Practical tips

Keep team chat for decisions and shared context. Use agent chats for iteration and tool-heavy work. Pin gold-standard replies in individual threads so the whole team can reuse them from team chat when needed.

  • Team chat — policies, priorities, and “stop / go” calls that affect every agent.

  • Agent chat — drafts, debugging, file pulls, and back-and-forth until the output is right.

  • Sidebar discipline — collapse it when you need canvas space; expand it when coordinating live with agents and colleagues.

Open the sidebar and start talking to your agents

Create a workspace, pick a team, and use team chat for shared briefs—or open an agent thread when you need a focused conversation with memory and tools.