AQ for remote teams
Published July 28, 2026 · by the AQ team
AQ gives a distributed team what an office used to provide for free: one place where the work is visibly happening. Agent sessions run server-side in shared workspaces, so a teammate nine timezones away opens the same live terminal, the same files, and the same running app you were just looking at, and picks up where you stopped.
Remote teams feel the single-player agent problem hardest. When every agent runs in someone's local terminal, "how is that task going" costs a meeting, a handoff costs a writeup, and a stuck session at 6pm your time waits until you are back online. AQ removes the machine in the middle.
Handoffs are a link, not a document
Because the session lives in the workspace rather than on anyone's laptop, handing work across timezones means sending a link. The next person opens the workspace, reads the terminal scrollback to see what the agent did and why, checks the diff in the editor, and picks the work up in their own terminal in the same workspace, on the same branch. The original session keeps running and stays readable the whole time (and its owner can delegate its keyboard with a one-click grant). Nothing is reconstructed from memory. The full pattern is in sharing a live agent session.
Watching beats screen-sharing
When a teammate says "my agent is stuck," you open their workspace and see the actual session, live. If watching is not enough, you request control and they grant it in one click; then you can interrupt the agent and redirect it yourself. That replaces the remote-team ritual of a call, a screen share, and one person narrating a terminal: the workspace is the shared screen, permanently, with real access control instead of a meeting invite. See debugging an agent session together.
Async review with the app in hand
Reviews across timezones are async by necessity. AQ makes them concrete: every workspace can expose its dev server as a live preview link, and reviewers pin comments directly on the running app, screenshots included. Comments can be sent to the agent as its next prompt, so feedback given at midnight your time is acted on before you wake up. Stakeholders outside the team can use preview links without an account.
Always-on by architecture
Sessions survive laptop close because they never depended on the laptop: agents run inside tmux on a server (a VM you bring on the Free plan, or the dedicated always-on VM included with the Team plan). The workspace list doubles as the team's live directory of what is running, which is the ambient awareness remote teams usually lose. Guide: keeping agents running after you disconnect.
Frequently asked questions
How does a timezone handoff work in AQ?
Send the workspace link. The teammate opens the same live session: terminal scrollback for context, the diff in the editor, the preview for behavior, and the same agent ready for the next prompt. There is no export, transcript, or re-setup step.
Can two people be in the same agent session at once?
Yes. A workspace's terminal is shared live: everyone with access sees the same output as it happens, and typing is delegated deliberately (request control, the session owner approves in one click, and you drive alongside them). It replaces screen-sharing for pair-debugging a session.
What about contractors or people who should only see some work?
Workspaces can be private and shared with specific people, so a contractor sees exactly the workspaces they are on and nothing else. For review-only outsiders, preview links show the running app without workspace access.
Do agent sessions stop when someone closes their laptop?
No. Sessions run on a server, not on laptops, so they continue unattended and anyone with access can reattach later. This is the default on both plans.