Live Links
Published July 28, 2026 · by the AQ team
A Live Link is AQ's answer to "can you show me?": a URL that opens the work itself, as it runs. Follow one and you are looking at the live agent session (the same terminal the agent is typing into right now), the working tree in an editor, and the app in a preview. Nothing was exported, recorded, or written up to make that possible; the link points at the workspace, and the workspace is the work.
Most tools in the agent era share artifacts: a transcript of a finished conversation, a replay, a diff. Useful, but an artifact is the past. The moments teams actually need to share (a stuck session, a half-built feature that needs a decision, a demo that is more convincing when you can touch it) are all in the present tense. That is the gap Live Links close.
What opens when someone follows one
- The live terminal. The agent session as it happens, scrollback included. Teammates watch live by default and can be granted the keyboard through a control request the session owner approves in one click.
- The editor. The workspace's isolated git worktree, browsable in place. The reviewer reads the change as it actually is, before anything is pushed.
- The running app. The workspace's dev server as a live preview. Click the feature, do not imagine it from logs.
Scoped to the audience
Not everyone should get the same door. A workspace itself is either visible to the whole team or private and shared with specific people, and sharing stays owner-managed. For audiences outside the team (a client, a stakeholder, a designer on contract), the preview has its own shareable link: they open the running app without an account. Give them a review link that allows commenting and, after a quick email sign-in, they pin comments on the exact spot they mean. Comments can be sent to the agent as its next prompt, so an outsider's feedback becomes the next iteration without anyone transcribing it.
Present tense by architecture
Live Links work because nothing in AQ depends on a laptop being open: agent sessions run server-side, in your own cloud or on an AQ-managed VM. The link is durable for the workspace's life. Open it during the run and you see the run; open it after a handoff and the session is still there, context intact, ready for the next prompt. A link that opens a recording tells you what happened; a link that opens the session lets you change what happens next.
Where teams reach for them
Handoffs across timezones (remote teams), a second pair of eyes on a stuck run (debugging together), reviewing agent PRs with the app in hand (agent code review), and client demos that are always ready (agencies). One mechanism, most of the collaboration surface.
Frequently asked questions
Is a Live Link a recording of an agent session?
No, and that is the point. A Live Link opens the running workspace: the live terminal, the current working tree, the app as it behaves right now. A recording shows what already happened; a Live Link lets the person who follows it participate in what happens next.
How do I share a live coding agent session with a link?
In AQ every workspace is openable by link for people with access: make the workspace team-visible, or share a private one with specific people. Whoever opens it lands in the same live terminal, editor, and preview you are looking at.
Can someone without an AQ account use a Live Link?
For viewing, yes: the workspace's running app has a shareable link that needs no account. Commenting uses a review link plus a quick email sign-in, so every comment has a name on it. The full workspace (terminal and editor) stays limited to people the owner shared it with.
Does the link break when the person who shared it goes offline?
No. Sessions run server-side, not on anyone's laptop, so the workspace a Live Link points to keeps running and stays openable regardless of who is online.