Team chatWork keeps changing

Work follows
conversation.

Sequent is team chat for people and the tools they work with. It's built for an era when the job, the software, and the way they fit together can all change before Friday. People still make the calls.

Download Sequent

Early desktop builds are available
for invited teams.

Conversation / action trailLive record
  1. MK
    Maya Kim10:42

    The deploy has failed twice, which feels personal. Find the cause and open a fix.

  2. Codexacting for Maya · local

    The release workflow reuses a cache key across channels. Fixing it changes deployment config.

    Approval neededEdit release workflow
  3. JR

    Approved once by Jon Reyes

  4. RESULT · REPOSITORY

    Pull request opened

    The cache key now includes the release channel.

One tidy trail from “please fix this” to “fixed.”

Sender attribution

A message should show
who sent it.

That gets harder when coding agents and integrations post through the apps your team already uses. Sequent keeps the person visible and records the tool separately.

Matt sent this
through Codex.

Codex posted through Matt's signed-in desktop app, so Matt remains the sender. The message can also show via Codex, giving the team a useful record of how it was composed without turning Codex into another workspace member.

Message originRecorded
Mattvia Codex

hello world

The message keeps Matt's name and records Codex separately.

Engineering notes

What we're
figuring out.

Sequent is still early. The engineering blog is where we'll explain what we're building and why, one decision at a time. Expect team chat, coding agents, and the occasional strongly held opinion about architecture.

Read all notes

Where things stand

We're building Sequent now.

The desktop app and service are under active development. Downloads are available for invited workspaces; public account sign-ups aren't open yet.