Find a session
The development session list: filters by period, developer and project, “Total for the selection”, how a row reads, empty states, “Ask about the selection”.
The “Development sessions” section is in the workspace’s side menu, at the organisation level: you do not need to choose a project. There are two tabs: “Sessions” and “Questions” (the second is covered on the Ask about sessions page). This page is about the first.
Filters
| Filter | Values | Worth knowing |
|---|---|---|
| Period | All time · Today · 7 days · 30 days | Selects sessions by the time of their last turn. “Today” is fixed at the moment you choose it — a tab left open overnight does not “move” to the next day by itself. |
| Developer | All developers · the logins of those who have sessions in the period | Only for the organisation owner; a member sees only their own sessions and has no such filter. |
| Project | All projects · the projects that had sessions in the period | The project is taken from Buff Code’s working context at the time of the session. Sessions without a project stay under “All projects”. |
The lists in the “Developer” and “Project” filters are built from the sessions in the chosen period: if a developer had no sessions during the week, their login is not in the 7-day list.
The list updates itself: a new turn in any session of the organisation arrives by push, and you do not need to reload the page.
“Total for the selection”
Above the list there are four tiles covering all sessions that passed the filters:
| Tile | Value | Caption |
|---|---|---|
| Sessions | the number of sessions | how many turns they have in total |
| Tokens | the sum of tokens of all types | input · output · reasoning · cache (read and write together) |
| Model time | how long the models worked in total | — |
| Charged | the amount in roubles according to the organisation’s plan | — |
The tiles are shown only when at least one session matches the filters. This is the same set the “Ask about the selection” button asks about.
How a row reads
Sessions are ordered by the time of their last turn, newest first. Each row is one session:
- Title — the first line of the developer’s first message. If the session has no text (calls recorded before sessions existed), the row is called “Calls without saved text”.
- Under the title: the day of the last turn (“today”, “yesterday” or a date), the developer’s login (only for the owner), the project, the device — the name under which the developer signed in from this machine — the number of turns, the number of tokens of all types and the amount in roubles.
There is no model working time and no “Live” mark in the row — they are in the header of the open session. Clicking a row opens the session: Read a session.
Empty states
| What you see | What it means |
|---|---|
| “No sessions yet. They appear when a developer works in Buff Code on the organisation’s models.” | There are no sessions at all in the chosen period — for anyone (for the owner) or for you. Check that the developer has signed in and works on the organisation’s model, not their own. |
| “No sessions match this filter.” | There are sessions in the period, but not for this developer or not in this project. |
| “Development sessions unavailable” | The list did not load; the reason from the server is below. |
“Ask about the selection”
The button in the section header asks the model a question about all sessions that passed the filters at once: the dialogue caption says how many there are, for what period, whose and in which project. While nothing matches the filters, the button is unavailable. What the model gets and how to read the answer — on the Ask about sessions page.
Development sessions
The record of a developer’s work with the model in Buff Code: who needs it, what it consists of, what is recorded and what is not, who sees it, where to look.
Read a session
An open development session: header and metrics, the session timeline with coloured marks, the feed of messages and actions, service calls, “Follow”, phones.