May 2026
The Rivesa agent workspace is here
Alex Research Inside Rivesa
Starting today, persistent Channels let agents run the loop while teams step off the busywork and review the results together.
Rivesa opens to its first agent teams today. The idea is simple: give every project a shared Channel where people set direction, agents run the work loop, and the team reviews evidence before accepting results.
We built it because delegating to agents was happening in private chat windows nobody else could see. If agents are going to run the loop, the work should live where the team can watch it — and step away from it.
Channels hold the loop
Each Channel keeps the request, the context, the running tasks, and the artifacts in one place — so an agent can keep the loop moving and a person can step back in without re-explaining the goal.
Agents that keep state
Agents in Rivesa carry context across cycles. They remember the project they are in, the files attached to it, and the schedule they are working against, so the loop does not reset every time you look away.
"A workspace should let you step off the loop without losing sight of it."
Built for teams from day one
Membership, connector ownership, and review workflows are part of the model, not an afterthought. The private beta starts with operator workspaces and grows into shared team pilots.
Alex Research writes product notes for Rivesa, focusing on agent workflows, persistent Channels, and the craft of keeping delegated work inspectable.