Summarize anything.

Videos, articles, PDFs, files, podcasts — one click, infinite customization.

Developer Preview
Try it on
youtube.com/watch?v=aR20FWCCjAs
Ilya SutskeverDwarkesh Podcast

0:00 / 1:36:04

Ilya Sutskever – We're moving from the age of scaling to the age of research

Dwarkesh PatelPodcast

Field Notes · Engineering

Why your team ships slower every quarter

Every engineering leader I talk to describes the same curve. In year one, the team ships something meaningful every week. By year three, a similar change takes a month, and nobody can point to the moment it got slow.

The usual suspects are headcount and process. But in the teams I've studied, the slowdown tracks something quieter: the number of things a change has to touch before it can go out.

Call it coordination surface. A feature that once lived in one service now crosses four. Each crossing adds a review, a deploy window, a contract to keep in sync. None of them is expensive alone. Together, they multiply.

The second force is unowned code. Roughly a third of the modules in a typical three-year-old codebase have no clear owner. Changes there stall, not because they're hard, but because nobody feels safe saying yes.

The third is invisible work: migrations, flaky tests, on-call. It rarely shows up in planning, so it quietly eats the margin every sprint was relying on.

What works is boring. Measure lead time per change, not velocity per sprint. Give every module a named owner. Budget 20% of each cycle for maintenance, explicitly, and protect it.

Teams that did all three recovered most of their early speed within two quarters. The ones that reorganized instead mostly moved the coordination surface somewhere else.

The Build Log

Ep. 42 — Why small teams ship faster

48 min · Oct 14

0:0048:12

Episode notes

Two founders compare notes on what changed when their teams grew from four people to forty, and what they'd keep small on purpose.

attention_is_all_you_need.pdf1 / 15

Attention Is All You Need

Ashish Vaswani, Noam Shazeer, Niki Parmar, Jakob Uszkoreit, Llion Jones, Aidan N. Gomez, Łukasz Kaiser, Illia Polosukhin

Abstract

The dominant sequence transduction models are based on complex recurrent or convolutional neural networks that include an encoder and a decoder. The best performing models also connect the encoder and decoder through an attention mechanism. We propose a new simple network architecture, the Transformer, based solely on attention mechanisms, dispensing with recurrence and convolutions entirely. Experiments on two machine translation tasks show these models to be superior in quality while being more parallelizable and requiring significantly less time to train.

1 Introduction

2 Background

3 Model Architecture

Figure 1: The Transformer, model architecture

3.2 Attention

Attention(Q, K, V) = softmax(QKT / √dk) V

3.2.2 Multi-Head Attention

3.3 Position-wise Feed-Forward Networks

3.5 Positional Encoding

4 Why Self-Attention

Table 1: Maximum path lengths, per-layer complexity and minimum number of sequential operations

5 Training

5.2 Hardware and Schedule

6 Results

Table 2: BLEU scores on English-to-German and English-to-French newstest2014

6.3 English Constituency Parsing

Interactive demo of the Chrome extension

Features

5 min readYouTube

# The Scaling Era Is Over

2020–2025 was the age of scaling. Data is finite and 100x more compute won't transform things, so we're back in an age of research. [21:15]

# Timeline

  • Human-level continual learners in 5 to 20 years. [82:16]
  • Build AI that cares about sentient life, and cap its power. [61:04]
sk-ant-•••••••••••••••••••••7Qx Stored in this browser

*No TLDL/R server in between.

Sensitive sites3 built in · 1 yours
  • bank.example.com
  • login.example.com
  • hr.example.com
  • intranet.yourcompany.com
+ Add a domain
youtube.mdarticle.mdpodcast.md
# How to summarize a video
Open with one line on what it's about.
Bullets only, 5 to 7.
Bold the claims, timestamp each one.
Keep it under 150 words.
Before
Yours
What's Sutskever's timeline for human-level AI?
✓ Searched the transcript · 0.8sSutskever estimates 5 to 20 years for human-level continual learners. He argues we're back in an age of research: ideas, not scale, are the bottleneck. [82:16]
Ask anything. Type / for commands.↑

FAQ

What can it summarize?

YouTube videos with captions, web articles, PDFs, Word documents, and podcast episodes from Apple Podcasts or Spotify. Open the page, or paste a link or drop a file into the side panel, and click Summarize.

Which AI models does it use?

Your choice of Claude, OpenAI or Gemini. Add a key for one or more providers in Settings, then pick the model in the panel before each summary. Chat and summaries can use different models.

Where does my data go?

Straight from your browser to the provider you chose, and nowhere else. There is no TLDL/R server and no account. Keys, summaries and skills are kept in your browser's local storage, and you can optionally sync them to a folder on your machine.

What does it cost?

The extension is open source and free. You pay your AI provider for what you use, at their rates. A typical video summary costs a fraction of a cent to a few cents, depending on the model and the length of the transcript.

Can I change how summaries are written?

Yes. Each content type has a short Markdown skill that tells the model what a good summary looks like. Edit it directly, or tell the chat what you want changed and it rewrites the skill for you. You can keep several and switch between them.

How do I install it?

It's in developer preview: clone the repo from GitHub, run npm install and npm run build, then load the dist folder as an unpacked extension in Chrome. The README walks through it. Join the waitlist to hear when the public release lands on the Chrome Web Store.

Does it work on every site?

It's off by default on banking, login and HR pages, and you can add your own domains to that list in Settings. Videos need captions or a transcript for the summary to work.

Your keys, your data.

No server, no signup. Everything runs locally in your browser.