Every 📧 @every

AI-pill your whole company with the Every Agent: https://t.co/ki3hyz8sVP every.to Joined September 2012

Tweets

8K
Followers

58K
Following

138
Likes

8K

Every 📧 @every

7 hours ago

How do you explain reasoning models inside a story about the people building them? For “How Codex Happened,” the answer was to make OpenAI itself the character doing the thinking. Between sections, imagined reasoning traces follow the company as it tries an approach, sees what works, and changes course. The device lets readers follow the company’s decisions while getting a feel for the technology behind Codex. @danshipper and his editors found a way to make the explanation part of the story. Read the full story of how Codex happened: every.to/p/how-codex-ha…

2 1 5 1K 1

View Details

Every 📧 @every

8 hours ago

Imagine if finishing one task kicks off all the follow-up tasks that come after. That’s what we’ve done with our conference speaker workflow. Our head of marketing, @DABrundage, built an Every Agent skill that pulls the speaker’s headshot and title, creates an asset in Figma, shares it in Slack, and opens a pull request to update the site. The skill is shared, so teammates can use it while Douglas is away. The design work and the website update become one automatic workflow. Install the Every Agent in Slack: every.to/agent?utm_sour…

3 1 7 3K 2

View Details

Every 📧 @every

10 hours ago

Before @huggingface became an AI platform, it was a chatbot company with a retention problem. People tried the chatbot, but they weren’t sticking around. Then the team released open-source AI work, and researchers started asking for more. As an early investor, @MattHartman watched the founders follow that demand. They understood how difficult the technical work was—and saw an opportunity to help other people use it. Watch the full episode: every.to/context-window…

3 1 8 1K 2

View Details

Every 📧 @every

14 hours ago

A better AI model can force you to rethink, well, everything. In reporting “How Codex Happened,” @danshipper found a distinction that also shapes how we build at Every: Model teams can plan for improvements in intelligence, but product teams have to discover what those improvements make possible. Read our full story on how Codex happened: every.to/p/how-codex-ha…

3 3 11 3K 8

View Details

Every 📧 @every

a day ago

We taught our Slack agent to edit like our editor in chief. @danshipper built a skill from @katelaurielee’s historical edits, then asked the Every Agent to give his draft a “Kate pass” in a Slack channel. Kate could see the edits. So could the rest of the team—and they started using the same skill themselves. Install the Every Agent in Slack: every.to/agent?utm_sour…

4 4 11 3K 6

View Details

Every 📧 @every

a day ago

When @MattHartman backs an early-stage startup, he assumes it will pivot. A team of real estate executives building an AI product is more likely to pivot to another problem in real estate. A technical team might recognize that the same kind of data appears in the car industry—and take its technology there instead. Some of the most successful teams he’s backed did the latter. Their technical expertise allowed them to recognize where else their work could be useful. Watch the full episode: every.to/context-window…

1 3 8 2K 1

View Details

Every 📧 @every

2 days ago

Vibe coding his own app made @MattHartman more willing to pay for software. After building Ghost Pepper, a voice-to-text app, he started thinking differently about the subscriptions on his phone. Getting an app to work is only step one. Someone has to keep fixing it and making it better. Watch the full episode: every.to/context-window…

0 3 7 2K 4

View Details

Every 📧 @every

2 days ago

An early version of "How Codex Happened" from @dealville: Read the full piece: every.to/p/how-codex-ha…

0 3 15 3K 7

View Details

Every 📧 @every

2 days ago

@aurelcorp @danshipper @leeknowlton We're exploring this 🙏

0 0 2 38 0

View Details

Lee Knowlton @leeknowlton

2 days ago

Remixed the interviews from @danshipper's Codex piece into a playable visual novel and cut a trailer for it

Dan Shipper @danshipper

2 days ago

at show and tell today @leeknowlton demoing how he turned my Codex piece into a visual novel:

9 3 39 8K 5

4 4 11 2K 4

View Details

Every 📧 @every

2 days ago

ATTENDING: @stewfortier of @typedotai will attend Thesis: 2027. Apply to attend Thesis, our inaugural conference on work and AI: every.to/thesis-2027?ut…

0 0 4 2K 0

View Details

Every 📧 @every

2 days ago

Us every 5 mins: "Hold on, agents [are doing something crazy on my computer so my screen is frozen]."

0 3 7 2K 0

View Details

Every 📧 @every

2 days ago

Nothing fishy about @hammer_mt's new book.

Dan Shipper @danshipper

4 days ago

must read

1 3 53 9K 60

0 3 4 2K 1

View Details

Every 📧 @every

3 days ago

Storyboards for "How Codex Happened" by @dealville: Read the full story: every.to/p/how-codex-ha…

1 6 15 3K 5

View Details

Every 📧 @every

3 days ago

@fredrivett thanks for the heads up! Asking our agent to fix it 🫡

1 0 1 36 0

View Details

Douglas Brundage @DABrundage

3 days ago

For the design of @every's How Codex Happened, we started with the history of thinking, machines, and thinking machines. I did some experiments with Codex (obviously), we got ideas and feedback from @danshipper, and then @dealville brought it all to life. See the results (and read the piece for free) here: every.to/p/how-codex-ha…

0 3 9 2K 4

View Details

Every 📧 @every

3 days ago

What do you build when you can build anything? @MattHartman, one of @huggingface’s investors, says valuable work starts with watching people use a product: Where do they get stuck? What do they keep trying to do? Which behavior tells you the product should change? AI-enabled coding lets teams act on those observations sooner. The advantage goes to the person who can turn what they learn into the next version—whether their title is engineer or product manager. Watch the full episode: every.to/context-window…

1 2 20 3K 9

View Details

Ananth @asub927

3 days ago

A must read from @every and its free.

Every 📧 @every

3 days ago

Our definitive history of how Codex happened. Read for free: every.to/p/how-codex-ha…

0 1 11 2K 3

0 1 3 587 1

View Details

Every 📧 @every

3 days ago

@dealville is the real deal

0 1 1 616 0

View Details

Every 📧 @every

3 days ago

Early sketches from Mike Deal's desk for "How Codex Happened." Explore the finished piece: every.to/p/how-codex-ha…

2 2 14 3K 5

View Details

Kristen Anderson @FintechKristen

3 days ago

Amazing encapsulation of @ajambrosino. One time a waiter in Palo Alto thought Andrew *was* BJ Novak and Andrew just let it ride. Never corrected him. Great piece @danshipper.

Dan Shipper @danshipper

3 days ago

Codex is one of the most important untold stories in the history of technology. A year ago, it was a scrappy effort in a quiet corner of @OpenAI. Its cloud product hadn’t found PMF, and the team was starting over from scratch. Less than 12 months later: - Codex swallowed the