Assistant session

Overview

An assistant session is one saved conversation with the dashboard assistant on Home. Each session has a title, full message history, a tool-step log of what the assistant did, and optional approval checkpoints where you confirmed sensitive actions.

Sessions are lazy-created — no empty session exists until you send the first message. After that, opening the session from Recents or Search chats loads the complete thread in the same Home layout.

Tip: Treat sessions like project notebooks:

  • One session per major task (single tender search, one pursuit update)

  • Rename vague auto-titles before Recents grows long

  • Use Search chats when scrolling Recents is slow

  • Remember deleting a session does not undo pursuit or settings changes

Important: Sessions belong to one team. Teammates on the same team can open your session read-only — they cannot send messages in your thread.

How sessions are created

Flow diagram

Step by step

  1. Start from Home (no session selected) or click New chat.

  2. Type and send your first message.

  3. Server creates the session.

  4. Browser address updates to that conversation.

  5. Title may briefly show New chat, then refine from content.

  6. Row appears in Recents.

Opening an existing session

Method

Result

Click Recents row

Loads history; URL updates

Search chats dialog

Filter by title; click result

Bookmarked link

Opens session if you have team access

Browser back from session

Returns to Home start screen (history preserved)

Loading states

State

UI

Loading

Placeholder rows while data loads

Success

Full thread + composer

Failure

Something went wrong + Try again

Authorization

Condition

Access

Your session, same team

Full read/write

Teammate's session, same team

Read-only

Wrong or deleted session

Not found / unauthorised

Different team

Not listed in Recents until you switch team

Page behaviour

The session view uses the same Home shell — not a separate app area:

Region

Content

Sidebar or mobile bar

Recents, New chat, Search

Main column

Message thread

Bottom

Composer, suggestions, approval cards

Page title = session title (or Home when none selected).

Session lifecycle

During an active session

Feature

Behaviour

Token streaming

Assistant text appears incrementally

What I am doing

Live tool-step panel

Thinking...

Before first token

Queued messages

If you send during a reply

Approval cards

Pause composer until resolved

Pulsing dot in Recents

Visible on other rows if those chats still run

Session menu (Recents ⋮ or right-click)

Action

Writable session

Read-only session

Last updated

Shown

Shown

Rename

Inline edit; Enter saves

Disabled

Delete

Permanent removal

Disabled

Deleting the active session switches to another chat or New chat.

Deliverables and attachments

The assistant may attach generated files to messages — exports, filled documents, downloads.

  1. Locate the message with attachments.

  2. Click the attachment to download or open.

  3. Files are tied to the session history — deleting the session removes the chat record, not necessarily the underlying pursuit documents already saved in the product.

Team scoping

Rule

Detail

One team per session

Created under active team at first message

Switch teams

Recents reloads; other team's sessions hidden

Credits

Consumed from session's team balance

Permissions

Team role limits what assistant can approve

Session vs New chat vs delete

Action

Session data

Product data (pursuits, etc.)

New chat

Old session kept in Recents

Unchanged

Delete session

Chat history removed

Unchanged

Approve create pursuit

Logged in thread

Pursuit created

Real-time and background activity

You may navigate away while a session runs:

Signal

Meaning

Pulsing dot on Recents row

Assistant still working on that chat

Return to row

Resume watching stream

Stopping from another session does not stop background runs on a different row unless you open that chat and press Stop.

Best practices

Practice

Reason

One session per task

Clear titles; better follow-up suggestions

Rename early

Search only matches titles

Do not delete to "undo" bids

Deletes chat only

Review approval cards on shared machines

Approvals commit real changes

Use read-only teammate sessions for learning

Then New chat for your own work

Edge cases

Scenario

Behaviour

Title stuck New chat

First message too short — Rename manually

404 on bookmark

Session deleted or wrong team

Long thread checkpoint message

Internal context compaction — data in app unchanged

Multiple reply versions

Use previous/next on assistant message

Session URL shared with colleague

They open read-only if same team

Troubleshooting

Symptom

Cause

Action

404 on open

Deleted or invalid session

Pick from Recents

Read-only composer

Someone else's session

New chat

History won't load

Network

Try again

Title never updates

Very short first message

Rename

Missing from search

Title mismatch

Scroll Recents to load more; search again

Wrong team's pursuits in answers

Wrong active team when created

Switch team; start new session

FAQ

Can I share a session URL with a colleague?

They can open it read-only on the same team. They cannot send in your session.

Does deleting a session undo platform changes?

No. Pursuits, settings updates, and documents persist — only chat history is removed.

Is there a limit on sessions per team?

Recents loads in batches (20); older sessions remain reachable via scroll and search.

Can I move a session to another team?

No. Create a new chat on the other team and summarise what you need.

Do sessions expire?

No automatic expiry in normal use — delete manually when no longer needed.

Why can I see a colleague's chat?

Same-team visibility supports transparency; write access is owner-only per session.

  • Dashboard (Home)

  • Dashboard assistant

  • New chat

  • Search chats

  • Working with AI assistant