Every 📧

@every

AI-pill your whole company with the Every Agent: https://t.co/ki3hyz8sVP

140 Following58.3K Followers7.6K Posts
  1. Every 📧@every
    Introducing: The @Every agent, the fastest way to AI-pill your company, now officially out of beta. With personal agent use, no one can see how their teammates are working with AI. With one “company agent” in @SlackHQ, they can. The Every agent comes loaded with the skills and workflows we use to run Every, and each person on your team gets $15 in free credits to try it. Install @Every in @SlackHQ today:
    Dan Shipper @danshipper
    BREAKING: Introducing the @Every Agent—an agentic coworker in Slack built to help you AI-pill your company. It comes with: - Everything you'd expect from a premium company agent. You can delegate difficult, long-running—like opening PRs, writing reports from large datasets, and monitoring social or customer feedback—and get high-quality results all from Slack - Every's best workflows, pre-installed and always updated. Compound Engineering to Compound Writing. We add more all the time. - Personalized Frontier Alerts. to help you keep up with new models. When we drop a Vibe Check, the Every Agent will read it and let you know if the new model is relevant to your workflow. - Zero markup on tokens. What we pay is what you pay—as token prices go down, so does your bill. You can try it today with $15 in free credits per person, up to $500 per workspace. After that: it comes with your $30/month Every subscription, plus tokens at cost. Add the Every Agent to Slack: Why it's hard to AI-pill your coworkers If you’re the AI-pilled one at work, you know the problem: you discover something incredible in Claude or Codex, but getting your coworkers to try it is another matter. The problem is that most of your AI use is invisible. You do it alone, in a terminal or a chat window. Your coworkers see the finished report or the five new ads, but they never see the request that produced them, or the corrections you made along the way. When you describe it afterward, it sounds like magic, but nobody learns a magic trick without seeing how it’s done. Why a company agent, in Slack, solves this problem When you use a company agent like the @every agent you go from prompting in private, to prompting in public. In a Slack channel, a coworker who would never open a terminal scrolls past a thread with your agent interaction and thinks: I could do that too. This lets you show instead of tell your coworkers about your discoveries. New AI tools and workflows then spread naturally and virally across your organization. That's why we made the @every agent for ourselves—and why we're releasing it to you today. Add the Every Agent to Slack:
    331913K
  2. Dan Shipper✓@danshipper
    BREAKING: Introducing the @Every Agent—an agentic coworker in Slack built to help you AI-pill your company. It comes with: - Everything you'd expect from a premium company agent. You can delegate difficult, long-running—like opening PRs, writing reports from large datasets, and monitoring social or customer feedback—and get high-quality results all from Slack - Every's best workflows, pre-installed and always updated. Compound Engineering to Compound Writing. We add more all the time. - Personalized Frontier Alerts. to help you keep up with new models. When we drop a Vibe Check, the Every Agent will read it and let you know if the new model is relevant to your workflow. - Zero markup on tokens. What we pay is what you pay—as token prices go down, so does your bill. You can try it today with $15 in free credits per person, up to $500 per workspace. After that: it comes with your $30/month Every subscription, plus tokens at cost. Add the Every Agent to Slack: Why it's hard to AI-pill your coworkers If you’re the AI-pilled one at work, you know the problem: you discover something incredible in Claude or Codex, but getting your coworkers to try it is another matter. The problem is that most of your AI use is invisible. You do it alone, in a terminal or a chat window. Your coworkers see the finished report or the five new ads, but they never see the request that produced them, or the corrections you made along the way. When you describe it afterward, it sounds like magic, but nobody learns a magic trick without seeing how it’s done. Why a company agent, in Slack, solves this problem When you use a company agent like the @every agent you go from prompting in private, to prompting in public. In a Slack channel, a coworker who would never open a terminal scrolls past a thread with your agent interaction and thinks: I could do that too. This lets you show instead of tell your coworkers about your discoveries. New AI tools and workflows then spread naturally and virally across your organization. That's why we made the @every agent for ourselves—and why we're releasing it to you today. Add the Every Agent to Slack:
    Download
    421222853.9K
  3. Every 📧@every
    Over 80% of @AnthropicAI’s Q3 revenue came from models released in the previous six months. A $2 trillion valuation means betting it can keep making the next hit. And be worth about the GDP of Spain at the same time. @itsurboyevan breaks down the business behind the eye-popping numbers:
    Download
    0592.2K
  4. Every 📧@every
    An operator with an idea used to need a vendor to add the feature—or an engineer to help build it. @ArielleShipper can now build some of the systems she needs herself. As the models improve, she’s excited about how much more of her operational work she’ll be able to turn into tools. Watch the full episode:
    Download
    2272.9K
  5. Every 📧@every
    .@hammer_mt starts a fresh chat for every task, even for the same project. He does this to avoid context rot, which happens when accumulated history makes AI responses worse. These are 7 tips for context engineering: 1. Start a new thread whenever the tone or type of task changes. 2. Keep memory turned off so irrelevant context can’t leak into the current conversation. 3. Only upload the documents the task needs. 4. Keep the preferences you always want—like spelling, tone, or length—in a saved document and paste them in at the top of every new chat. 5. Write the full brief before you start and put everything the model needs into the first message rather than drip-feeding it. 6. When the AI makes a mistake, go back and edit your previous message so it has no memory of doing anything wrong. 7. Before you leave a long thread, ask the model the question Mike has recommended when working on recurring tasks: What information would have been useful to know at the start of this task that would have eliminated several steps or mistakes? Get Mike’s new book, Context Engineering with DSPy: Read the full piece:
    Download
    44112K
  6. Every 📧@every
    ATTENDING: Fletcher Richman of @typedotcom will attend Thesis: 2027. Apply to attend Thesis, our inaugural conference on work and AI:
    Download
    1141.8K
  7. Every 📧@every
    Your AI bill tells you what you spent. What work did those tokens actually buy? @ArielleShipper demos Every’s usage dashboard, which breaks spending down by person, model, and effort level. A companion workflow groups sessions into types of work and asks the user to approve the categories—so they can judge whether the spending was worth it. Watch the full episode:
    Download
    52183.2K
  8. Every 📧@every
    Keeping up with every AI model can become a full-time distraction for a company. Every’s frontier team gives people like @danshipper room to experiment while the rest of the company builds products and serves customers. Some experiments become useful lessons. Others make their way into products and services once they’re ready for the wider team. Watch the full episode:
    Download
    131293.4K
  9. Every 📧@every
    If you’ve just joined a company and are still figuring out who does what, try asking your company agent. That’s what happened to @beckyisj, who joined the team earlier this year. She asked the Every Agent who people were, their responsibilities, and what unfamiliar terms meant. Because the company shares one agent, it could draw on conversations and documents she hadn’t found yet. 3 prompts to try on day one: • I’ve just joined [team]. What are the main projects they are working on right now? • Who is [name], what do they own, and what should I ask them? • Summarize the last week of #[channel]. My role is [x], and my goals are [insert here]. Caveat: Don’t forget to check the answers with people, too. A misattributed transcript sent her to the wrong colleague, but they were able to point her to the right person. Install the Every agent: Read more:
    Download
    3251.8K
  10. Every 📧@every
    100 AI experiments won’t help your company if none of them land. @kieranklaassen’s advice for frontier teams: Listen to the people doing the work, make the experiments understandable, and help the useful ones get adopted. Dumping everything into a channel is easy. Integration is the job. Watch the full episode:
    Download
    94203.8K
  11. Every 📧@every
    The raw material for an explainer video was already in @hammer_mt’s @SlackHQ messages and @meetgranola notes. He asked Opus to find the narrative, pull references to what he’d said, and cut a video explaining Checks, Every’s personal benchmark product. For someone busy running experiments, that makes it easier to tell the team what he’s been building. Watch the full episode:
    Download
    22154.1K
  12. Every 📧@every
    Before the CEO woke up, the Every Agent flagged a customer who was still waiting for their test results. The customer, a farmer, had paid for bovine parentage testing and was asking for an update. The only issue was the engineer in charge was out sick. Thankfully, the agent’s morning report connected those facts and suggested a coworker who could cover. That’s one example from FeanixBio, a 28-person cattle genetics startup serving about 35 family-owned farms. Its team uses the shared agent for task reports and vacation coverage, too. Install the Every Agent: Read more:
    Download
    0081.9K
  13. Every 📧@every
    What would it look like to manage coding agents at the level of goals and plans? @JannikJung built Minga to try it. He gives an orchestrator the requirements; it breaks the work into tasks, tracks dependencies, and starts work in the background. When it needs a decision or feedback on a UI, it brings him back in. Watch the full episode:
    Download
    174294.2K
  14. Every 📧@every
    AI makes it easier to generate ideas. It also makes it easier to overwhelm everyone around you. @hammer_mt’s next job is making his experiments easier to absorb: turning the work into digestible videos and protecting his colleagues’ attention as his output grows. Watch the full episode:
    Download
    24144.8K
  15. Every 📧@every
    “Don’t freak out, I cloned you.” That’s what @hammer_mt told @nataliazarina after distilling a year of her Slack messages into a natalia.md file describing how she thinks and makes decisions. He then asked an AI to use that file to critique a client email as Natalia would. Using SynthTeam, an open-source library that turns someone’s Slack history into a persona file, he had Codex pull a year of Natalia’s messages from public channels. He looked for situations where she’d made decisions and reverse-engineered how she made them. Read the full piece:
    Download
    45214.6K
  16. Every 📧@every
    Getting an AI-built prototype to work once is only the beginning. @JannikJung helps turn experiments into software the team can rely on. That means making decisions about code structure, libraries, deployment, and how the project will be maintained. Watch the full episode:
    Download
    1383.1K
  17. Every 📧@every
    How to write well with AI: Know your reader. @kplikethebird is adding audience.md to Compound Writing, alongside its voice.md and style.md. For her Working Overtime column, that means checking whether a draft welcomes the AI-curious reader while giving the experienced operator enough practical detail. Watch the full episode:
    Download
    02192.2K
  18. Every 📧@every
    Too many browser tabs sent @jackcheng down an unexpected path: building his own browser. It has no tabs, an agent pane for editing with different models, and a peek mode for looking something up without losing his place. A small example of what becomes possible when you can change the application around your workflow. Watch the full episode:
    Download
    10141.9K
  19. Every 📧@every
    Earlier this year, every teammate had a personal agent. Then none of us wanted to keep fixing and updating them. So we shifted to building a shared agent, relying on @AnthropicAI’s Claude Managed Agents infrastructure. @paridhitweets helped build the first version of the Every Agent that went live within a week. Now that the hard part was handled by Anthropic, we could focus on the parts that made the Every Agent more like a coworker: how it behaves, when it should stay quiet, and which connections each teammate can use. Security-wise, credentials stay out of the agent’s view, and changes to shared skills require human approval. There are some trade-offs: We’re tied to Claude, and persistent conversation history means the platform doesn’t support zero-data retention. Install the Every Agent: Read more on our experience building the Every Agent on Claude Managed Agents:
    Download
    70172K