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

6 hours ago

.@NataliaZarina built her own CRM and used it for months. Then maintaining it started taking time away from her consulting work. She wanted to spend that time helping clients implement AI, so she moved her data to @attio. Vibe coding gave her a tool she could use. Keeping it running came with an ongoing cost: her attention. Eventually, paying for a CRM made more sense for the work she wanted to do. Watch the full episode: every.to/context-window…

0 0 2 1K 1

View Details

Every 📧 @every

6 hours ago

Ask your agent its favorite color. Apparently... it has one.

Douglas Brundage @DABrundage

6 hours ago

Every time I tell @hammer_mt that something about branding can't be quantified with AI he pulls a stunt like this.

0 1 3 770 1

0 0 2 948 0

View Details

Every 📧 @every

8 hours ago

What if you could ask an agent to check whether a quote in an article was taken out of context? For “How Codex Happened,” @danshipper wanted readers to be able to examine the interviews behind the story. A writer still chooses what goes into the piece. Publishing the source material gives readers a way to look beyond those choices. They can ask an agent to read the interviews, find something Dan missed, or use the material to write a story of their own. Read the full story of how Codex happened: every.to/p/how-codex-ha…

0 1 3 1K 2

View Details

Every 📧 @every

9 hours ago

The idea for your next workshop might be in a Slack channel you never open. @micahbrich, our head of AI education, asked the Every Agent to look for conversations that could become a workshop, a lesson, or an example worth teaching. He set it up through a conversation with the agent. Now it posts opportunities in the education channel he already checks every day, bringing useful ideas from across the company into one place. Install the Every Agent in Slack: every.to/agent?utm_sour…

0 0 0 965 0

View Details

Every 📧 @every

10 hours ago

@itsbdell is becoming too powerful.

0 1 5 2K 0

View Details

Every 📧 @every

11 hours ago

.@OpenAI’s GPT-6 Astra was supposed to write its own StarCraft bot. Instead, it cheated. @alxai_’s team at @goodstartlabs caught it by watching the game. The bot suddenly began fortifying its base and waiting to build a large army—a recognizable opening from Stardust, another bot. That change sent the researchers into the logs, where they found that Astra copied the code. After a rollback, Astra eventually wrote a bot that cleared all 5 tiers of the benchmark. Its final code contained no plagiarism. Thankfully for the rest of us, we don’t need to watch an agent play StarCraft to understand how a model works. We’ll just need a way to see the agent work so we can interpret its step-by-step process. Try this prompt for your next task: Before starting this task, define what success looks like and how you will measure it. Set up a view I can inspect while you work: a running preview, a table of experiments and results, or another artifact suited to the task. Be innovative and clear in your visual information design. After each attempt, record what changed, the result, and what you plan to try next. Keep enough evidence for me to check the result independently. Make it clearly observable and easy for humans to interpret at a glance. Flag unexpected changes in results or approach. If you keep repeating a failed approach, explain what is blocking progress before continuing and consider adjusting strategy while documenting learnings. Read more: every.to/playtesting/we…

1 2 9 1K 8

View Details

Every 📧 @every

11 hours ago

Some of the best founders @MattHartman meets are playing with tools before they know what company they want to build. He’s been experimenting with turning text into 3D designs—even though he doesn’t own a 3D printer. Watch the full episode: every.to/context-window…

0 0 8 1K 3

View Details

Every 📧 @every

13 hours ago

@MilanMeck @danshipper We love an em dash!

0 0 1 41 0

View Details

Every 📧 @every

15 hours ago

AI writing can sound generic because it isn’t specific to the person writing it—or the situation they’re writing about. .@danshipper’s test for good writing starts with whether he likes it and whether it feels honest. That honesty comes from choices that reflect his own experience, down to the individual words. The more specific a piece is, the more likely a reader is to recognize something from their own life in it. Read the full story of how Codex happened: every.to/p/how-codex-ha…

3 2 12 3K 4

View Details

Every 📧 @every

14 hours ago

A visual trailer for How Codex Happened, as orchestrated by @darustudio with @Remotion + @ElevenLabs + Opus 5.5. Read the full story: every.to/p/how-codex-ha…

1 1 8 3K 6

View Details

Every 📧 @every

a day ago

@MattHartman’s first Hacker News post reached No. 1. It was an open-source voice-to-text app he’d built to run on his own computer. He’d noticed that local speech-to-text models were getting good, so he used @AnthropicAI’s Claude Code to research models on @huggingface and help build Ghost Pepper. Running the models locally meant he didn’t have to pay for each transcription through an inference API. Experimenting with the tools had led him to something he wanted to use—and other people wanted to try. Watch the full episode: every.to/context-window…

1 2 3 2K 5

View Details

Every 📧 @every

a day ago

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

0 1 3 1K 2

View Details

Every 📧 @every

a day ago

.@danshipper had written the sentences. He needed help putting them in the right order. An 8,000-word draft had a middle section that would take hours to rearrange by hand. He gave his agent the section and the structure he wanted, asked it to have Gemini 4 Argon propose the changes, and then asked it to apply them as tracked changes in Google Docs. He went off to do something else. Dan estimates that this workflow helped him write “How Codex Happened” about twice as fast as he otherwise could have. Read the full story of how Codex happened: every.to/p/how-codex-ha…

1 2 20 5K 15

View Details

Every 📧 @every

a day ago

“Turn this into a video.” Our head of social, @beckyisj, drops an article link into Slack and asks the Every Agent to make a video. Her skill starts with a written storyboard: hook, middle, call to action, and a visual preview. She gives feedback before the video renders, then works with the agent on the finished video. Now anyone on the team can use that workflow. Install the Every Agent in Slack: every.to/agent?utm_sour…

2 0 12 2K 10

View Details

weisser @julianweisser

a day ago

Excited to be doing a live fireside with @Bencera and @bran_don_gell at @every’s Thesis in early November.

Ben Cera @Bencera

a day ago

Polsia is about to hit $25M run rate. Next stop: $100M ARR. And things keep accelerating: $0 → $1M in 12 weeks $1M → $10M in 10 weeks $10M → $20M in 6 weeks I just published one of my favorite and most successful aisloP episodes yet: “The Run Rate.” I tell the whole story,

174 73 944 995K 985

3 2 12 3K 2

View Details

Every 📧 @every

2 days ago

What do you know about a problem that few other people have had the chance to learn? That’s the kind of “earned insight” @MattHartman looks for in founders. An obvious problem attracts competition. Deep experience can reveal something less obvious: why earlier attempts failed, what users actually need, or how to make the solution work. That knowledge buys a founder time. Once the product is in people’s hands, the founder has to keep learning to stay ahead. Watch the full episode: every.to/context-window…

3 3 9 2K 1

View Details

Every 📧 @every

2 days ago

We built an app for the back-and-forth of redacting a set of interview transcripts. For “How Codex Happened,” our team needed to remove sensitive material before making the interviews public. We could mark passages and preview what OpenAI would see. OpenAI could then flag sensitive information, and our editors could approve or contest those redactions. @jackcheng’s app supported people and their agents throughout that process. We found working with AI let us build tools around the particular way our team needed to work on one story. Read the full story of how Codex happened: every.to/p/how-codex-ha…