Prototype: live rooms work, team and org seats do not
Coding presence for remote teams
A live room that shows teammates who are actually coding, with avatars you can drag together to start a recorded co-working session. The room, invite links and sessions work today as a prototype wherever the server enables it. What is missing is the layer above them: organisations, assigned team seats and billing.
The problem
Remote teams lose the ambient awareness an office gives you. Chat presence only says an app is open; it does not say whether someone is in flow or whether this is a good time to interrupt.
Presence you cannot fake
AtoAxis already receives editor heartbeats while you work. That same signal can answer whether someone is writing code without anyone setting a manual status.
A chat status reflects an open window. This reflects work.
How presence works
Rooms and invites, today
You create a room, share an invite link, and everyone who joins appears as an avatar with a working, idle or offline state derived from their own editor heartbeats.
Dragging avatars together, today
Dragging two avatars together starts a recorded co-working session; its duration and participants land in both histories.
Sub-teams, later
An organisation will divide assigned seats into smaller working groups, each with its own standing room. That layer is not built yet.
What this will not be
Presence and surveillance are separated by design:
- Everyone who can see the room appears in it, including owners and admins
- Only working, idle or offline is shown, never file paths, projects or branches
- Presence is opt-in and leaving a room does not leave the organisation
- Presence changes nothing about heartbeat storage
A room where everyone is equally visible feels like working together; an observer view is monitoring software.
What you can use today
Individual tracking works today: coding time by project, language, branch and editor, keystroke and character counts, and complete history. The presence prototype above is also usable now wherever the server enables it, for ad-hoc rooms and invite links rather than standing team seats.
Related pages
Join early access
We will use this address only for AtoAxis Early Access updates.
Team presence FAQ
- Can I use team features in AtoAxis today?
- Partly. A presence prototype with live rooms, invite links and recorded co-working sessions is usable now wherever the server enables it. Assigned team seats, sub-teams and organisation billing are still in development.
- What is coding presence?
- A live avatar view derived from editor heartbeats rather than a manually selected status.
- Will managers watch developers?
- No. Presence is mutual and shows activity state only, never file paths, projects or branches.
- How does it differ from chat tools?
- It is derived from editor activity and is intended as an ambient team signal, not a chat product.
- What does dragging avatars do?
- It records a co-working session with its duration and participants.
- When is the full team version available?
- There is no committed date. The presence prototype is usable now wherever it is enabled; organisation and assigned-seat support must land before it is a team product.