News Ciev Recorder is live. Add to Chrome

Your recordings saw everything.
Now your agents do too.

Stop rewatching a call to remember what was decided. Ask Claude, Cursor, or any AI tool your team already uses, and get a cited answer, a coaching report, or any document you need. Every claim is grounded in what was actually said and shown on screen.

ciev.ai/meetings/payments-sync
Payments sync · Tue screen + audio
0042_orders_index.sqlpayments-api
10-- orders backfill, 10k rows a batch
11
12CREATE INDEX idx_orders_status
13 ON orders (status, created_at);
ERROR: canceling statement due to lock timeout
PSPriya
MLMarcus
34:12 / 47:05
PS
Priya34:08

If that index ships as is, orders is locked for the whole backfill.

On screen · 0042_orders_index.sql, line 12
ML
Marcus34:31Decision

Then it goes out CONCURRENTLY, and the backfill moves to Sunday night.

Claude Codevia Ciev MCP

Why didn’t the orders index ship on Friday?

Building it would have locked orders for the entire backfill 34:08. The team switched to CREATE INDEX CONCURRENTLY and moved the backfill to Sunday night 34:31.

ZoomGoogle MeetUpload video
Infra ReviewMarch 14 · 3 people · screen sharedREC 34:12

Preeti is presenting

Shared screen: inference p99 latency, spiking to 8.7 seconds on cold starts and flattening after the service was split out.
Preeti:…so we keep the model warm before the request hits.
PPreeti
AAlexandarmuted
34:1258:04

4 moments indexed so far

Extracting: audio + visual

audiotranscript · Preeti: "keep the model warm before the request hits"
visualocr · p99 8.7s → inference split out
CIEV

AI agents

Cursor
Claude Cowork
Gemini
Codex
any MCP client

Company platforms: via connector

Glean
M365 Copilot