Spiral

npm i -g @every-env/spiral-cli && spiral login

My biggest takeaways from @danshipper: 1. The future of work will happen inside Codex or Claude Code. Instead of putting AI into your SaaS tool, you’ll use your SaaS tools inside your favorite AI agents' in-app browser. Dan spends all his time in Codex now—writing documents, managing email, doing research, everything. He's using Google Docs, PostHog, and everything he needs within the agent's in-app browser. The agent can see what he’s doing, and has all of his context, so he and his agent collaborate quickly and super effectively. 2. Automation is a lie—every automation needs a human. Dan's company doubled in size this year despite being incredibly AI-forward. Why? Because in order to make automation work well, you need humans making sure everything keeps working. This is why benchmarks are misleading—they measure AI on problems we’ve already framed and can score, but there’s always a higher frame. 3. PMs will win the AI era. Marcus, a former PM who previously ran Axios’s writing product, joined Every after getting super AI-pilled. Now he runs their product Spiral, and ships faster than anyone on the team. He pairs technical knowledge with spiky product sense, deep user empathy, and an eye for what matters. Dan thinks any PM who gets really AI-native will be incredibly dangerous because the building is done for you—what matters is figuring out what to build and if it’s great. 4. Full-stack designers are becoming superheroes. Designers used to make beautiful interactions that engineers didn’t want to build or couldn’t execute properly. Now designers don’t need to hand things off; they can build it themselves. Designers are naturally creative people, and AI is the perfect tool for them because it lets them bring their vision to life without the traditional bottlenecks. 5. SaaS is not dead. In fact, Dan is bullish on SaaS stocks. When users bring their own AI (via Codex or Claude Code) to use SaaS products, the user—not the SaaS company—pays for tokens. This saves SaaS company’s margins. Since the agents need their own seats, Dan predicts that agents will create massive new demand for SaaS because there will be tons of agents using these products at high volume. 6. Every company will have one “super-agent” inside their Slack that every employee will use. Dan initially thought every employee would have their personal work agent, like a shadow AI org chart, but he’s completely flipped his view. He realized agents need humans who care about them. When someone gets tired of maintaining their personal agent, it becomes useless. The winning model is one forward-deployed engineer or AI-savvy person who maintains a company-wide agent (like Shopify’s River or Viktor), and then it trickles down to more specialized team agents as models improve and become less fiddly. 7. The AI job apocalypse is not happening, but you do need to evolve to stay relevant. Models make yesterday’s human competence cheap. But because everyone uses the same models, it all looks the same if you use it the default way; it becomes commoditized slop. Humans then take that frozen competence and use it to make something new and interesting for their specific situation. The key: “ride the models”—use them for everything you do, try new models when they drop, keep turning over rocks. 8. We will read way more AI-generated writing, and we will like it. Human writing is incredibly important for things that matter, but for internal docs, planning, and email, AI-generated is often better because most people are bad at writing strategy documents. 9. Build software for humans and agents to use together. The current model is building a CLI that an agent uses independently. Instead, you and your agent should be using the app together. This creates new design challenges—agents can make a billion requests in three seconds, so you need approval flows, inboxes that summarize what happened, logs, and easy rollback. 10. Forward-deployed engineers are the new most essential role. The big model companies have teams of people managing their internal agents, and those teams aren’t going away. It’s different from traditional software building, and certain engineers love it. As models get better, this role will evolve—you’ll be managing more agents doing more things.

Automation is a lie. CLIs are over. The SaaSpocalypse is dumb. A year ago @danshipper came on the podcast to predict where AI was heading. He was remarkably right—including the call that everyone was sleeping on Claude Code. Dan has a unique lens into where things are going because his team at @every is possibly the most AI-pilled group of people in tech. I always learn a ton talking to Dan. So I brought him back for round two. We'll score these in exactly a year: 🔸 Every company will have one “super-agent” in Slack. 🔸 Codex and Claude Code will become the new operating system for knowledge work. 🔸 The AI job apocalypse is not happening. 🔸 PMs and designers will thrive. 🔸 We will read way more AI-generated writing and we will like it. 🔸 "I would buy SaaS stocks right now." Listen now 👇 youtube.com/watch?v=4D3hDm…

We’ve automated every single thing we can @every with AI agents. And yet there’s way more human work to do than ever. We’ve gone from 4 -> 30 human employees since GPT-3. I wrote a report on the structural reasons: how AI makes expert competence cheap, why that drives up demand for experts, and why the dynamic only intensifies as we approach AGI. After Automation: every.to/p/after-automa…

Spiral's "top edit" function evolves with user perceptions of AI writing. Claude reviews anonymized messages flagging AI tells, and then selectively incorporates that guidance into the top edit prompt. The top edit runs on every draft Spiral produces, modeled after Every's own editorial process. The initial result has been a ~30% decline in user messages that flag AI phrasings.

A few weeks ago we launched a new designer role that required you to submit a small Figma design as your application. It was a little controversial. We got 100+ applications. Yesterday we relaunched the role with more of a standard application (no small Figma project). We’re gonna see which one nets out more/better apps and report back. modern-ton-234.notion.site/4b2ca4f355ac82…

@claudeai Spiral was featured on Anthropic's blog today announcing multiagent and other features: claude.com/blog/new-in-cl…

The Spiral CLI now handles multi-draft requests ~30% faster on average, thanks to multiagent in @claudeai Managed Agents. When you run `spiral write` and ask for several drafts, those drafts are written in parallel by Opus-class subagents.

@helloiamleonie @TrySpiral by @every is exactly this and has all of Every’s editorial taste built in.

@helloiamleonie Working on it!

Agent harness for writing instead of coding. Anyone working on that? Any recommendations? (Please don’t tell me Claude Code unless you have a workflow that’s actually good)

The Spiral CLI now includes memory – send project context or a style preference once and future drafts will reflect it. Powered by the new @claudeai Managed Agents platform

Spiral's version history now tracks drafts by author, so you know whether you or Spiral authored a version You can also ask Spiral to reference a past version, like "there was a great line about provenance two or three drafts ago, let's incorporate that"

upgrade to >1.3.0 to get these @every-env/spiral-cli" target="_blank" rel="nofollow noopener">npmjs.com/package/@every…

Two new commands in the Spiral CLI: personalize and humanize. spiral personalize "your_text" – rewrites the given text in your voice spiral humanize "your_text" – removes common AI tells according to your Account > Writing Rules

@EdgarCerecerez @every The package page has guidance @every-env/spiral-cli" target="_blank" rel="nofollow noopener">npmjs.com/package/@every… New website with docs coming soon. We're happy to help, just email support@writewithspiral.com

@TrySpiral @every awesome, but haven't been able to get it to work. thought there was an mcp or skill wrapper around it... Also are there docs? changelog?

npm i -g @every-env/spiral-cli && spiral login

We're looking for a few teams to beta test new collaborative workflows for company writing – if interested, DM or email beta@writewithspiral.com

@MalGsx Layering styles is a great idea. We're hoping to help more people across companies post publicly about their work. People close to the work have a lot of interesting info to share, but layers of corporate approval prevent it from getting out.

I think @TrySpiral will accelerate companies footprint on platforms such as X or even Substack. Train it to the companies overall tone to produce high quality items but also allow employees to generate their own tones and writing style. This way when you produce let’s say blogs you have the tone and essence of the company values with the personality of the writer.

Try it out: app.writewithspiral.com/onboarding Route works for existing users too

Spiral's new onboarding flow: Writing samples → LLM style guide automatically. 1. Accepts writing samples from your X account, website, files, or pasted text 2. Runs stylometry on the samples and produces an LLM-optimized style guide 3. LLM-as-a-judge evaluates a test draft to see if it blends in with your writing samples (fail case iterates on the guide and re-evaluates) Demo video (token generations sped up):