Chema

Meet Chema 2.0.The agentic terminal.

The interface after Slack. One window that turns conversations into decisions, tasks, and company memory.

Chema

Summarize today's launch blockers and assign next steps.

Thinking

From Slack · #hb-ops:

Hugo Ruizin#hb-ops· SlackToday · 9:41 AM

QA is blocked on the billing webhook — we can't ship the pricing page until Sam's fix lands.

From Slack · #fundraising:

Brian Cheskyin#fundraising· SlackToday · 10:12 AM

Investors keep asking for desktop-native. If launch slips past Thursday we're explaining a miss, not a feature.

From Chema · #sales:

Sam Altmanin#salesToday · 11:03 AM

Three enterprise prospects are waiting on the usage-band deck. I need a clear owner before I chase follow-ups.

Launch blockers — today 1. Billing webhook blocks QA + pricing page ship. Owner needed on Sam's fix. 2. Desktop narrative — Thursday investor pressure if launch slips. 3. Usage-band deck — three enterprise deals stalled without an owner. I've drafted the recovery initiative and a Sales update so the team can move without another meeting.

Worked for 3.4s

Sources
CC

DRAFT INITIATIVE

Assign to: @James Wan

Tap priority or status to cycle options before you create.

Unblock Thursday launch

Clear billing webhook, pricing page, and investor narrative before Thursday.

1) Land Sam's billing webhook fix and unblock QA. 2) Confirm pricing page ship window with Hugo. 3) Publish usage-band deck so Sales can chase the three enterprise follow-ups. 4) Post status in #hb-ops once the recovery plan is locked.

Due: Thu, Jul 31

Workspace:

DRAFT MESSAGE

To: ACME Sales (4 people)

Workspace:

Team — launch blockers are mapped. James owns the recovery plan; usage-band deck is next so we can unblock the three enterprise follow-ups before Thursday. Reply here if a deal needs a different priority.

One prompt. Every system. Real work.

Not another chat app. Not another copilot waiting for an @mention.

An agent terminal sits above every platform and becomes the interface for your company — slack, email, crm, docs, meetings.

One prompt. Every system.

Instead of opening five apps, ask once. Chema reads Slack, Gmail, docs, CRM, meetings, and the web — then executes.

Cross-system work

Summarize channels, draft replies, create tasks, and build reports without leaving one window.

Native + connected

Work in Chema channels or bring Slack and the rest of your stack into the same agent.

Research when needed

Search the web, pull context, and return grounded answers you can act on.

Work in natural language.

The interface shift isn’t another chat app. It’s telling your company what to do in plain English.

Yesterday

Open Slack → find the channel → @someone → paste a link → summarize → create a task.

Tomorrow

“Summarize today’s launch blockers and assign next steps.”

Structured outcomes

Conversations become decisions, tasks, reports, and memory — not more scrollback.

Company memory.

Chat history tells you what people said. Company memory tells you what was decided, why it mattered, and who owns it.

Decisions that stick

Save the call, the owner, and the why — so the next agent turn starts from truth.

Initiatives & outcomes

Turn talk into owned work, then track whether it actually moved the company.

Audit trail

See what the agent did across systems before you approve, send, or ship.

How teams use Chema

Same agent terminal. Different high-value moves — from launch week to board prep.

Agentic terminal

One window above every system

  • Reads Slack, email, CRM, and docs
  • Saves decisions into company memory
  • Drafts replies and creates tasks
  • Builds reports you can ship

The next decade of work won't happen inside channels.

It will happen inside agent terminals.

Download for macOS

— Brian Daniel, CEO