Brian Casel
@briancasel
Building: Co-hosting
In flywrite.app, your AI agents are one keystroke away. Launchers open a new terminal with something already running: a plain shell, Claude Code, or Codex — each on its own shortcut. Add launchers for your own commands, and remap any keyboard shortcut in settings.
Your writing app should look like yours. In flywrite.app you can pick any font installed on your Mac with a live preview as you choose. Build full custom themes, down to every color, font size, and weight.
New in flywrite.app: click any image, video, or audio file in your project and it opens right in the editor — zoom images, scrub video, play audio. And it refreshes live so you can watch your agent generate visuals in real time.
Good thing I've started moving all my writing and artifact'ing into local markdown files with Claude Code and flywrite.app.
New in flywrite.app: put images right in your writing. Paste a screenshot, drag a file in, or click the Img button — the picture appears right in your document. Files land in an images folder near your doc (configurable).
Subtle but helpful: When toggling between the file editor and terminal in flywrite.app the top line of each lightens/darkens. That lets me know which is active so that I can manage the tabs in each using the same keyboard shortcuts (all customizeable btw).
How do you like your markdown docs to feel? Dial in the perfect fonts, weights, colors, scale in flywrite.app. See mine here. Now available.
I plan builds twice. For a reason: PRD = the macro plan. My product vision. The decisions around *what* to build. (👈 vast majority of my time is here) Plan mode = the micro plan. Claude's plan for how it will code that vision. (👈 this alone is not enough)
A frontier model can build your whole app in one prompt. Sometimes that's even true. The question is whether you should. And no, you shouldn't. One-shotting skips every checkpoint where you'd catch your own planning misses. Build in milestones.
"It works", Claude said. Reality: All it did was re-read its code and decide it was "correct". Make Claude prove it: 1. Write tests, require 100% pass. 2. Use agent-browser skill to screenshot & check its UI work. That eliminates a ton of time having Claude fix stuff.
My internal app for planning my pipeline, scheduling and publishing content. I develop pieces in Claude Code. Agent pushes to here then schedules things out, according to my rules.
The tool (or agent skill) your business actually needs is already hiding in your week. You don't have to dream up a clever app idea. Look at the recurring busywork that quietly eats your hours every week. That's the thing worth building. Start there.
A stronger AI model isn't a threat to your job. The best output from the best models comes when someone with judgment, taste and experience is steering it. More horsepower goes to whoever's willing to migrate their technical chops UP the ladder to where they matter more now.
Don't love "workflow" being a keyword for Claude now, which instructs Claude to use its' new Workflow tool. The apps I build are for managing MY workflow, so I often frame my specs/prompts around the user's "workflow" with the feature/UI. That's a different meaning/context.
The AI prompted playlist feature on Spotify is pretty great. Here are 2 of mine (in my work account):
Seeing how far I can go to make my solo creator business AI-native. Here's my slate of custom apps and agent skills that run my pipeline. Goal: Less of my time on busy work. More of my time on creating, teaching, building.
Been working on some internal tools for me & my agents to power my content pipeline. So much freedom and power when designing for a customer base of one.
Every time I buy a new mac it sits unopened for a week until I have a day to set it up.
Added this email sent to folks who hesitate in my checkout flow. Highly recommend.
Working on a new course for people who want to build tools, but lack software dev experience. You will fill those gaps and build something real, using the same tools and process that "pros" do. Coming to Builder Methods Pro this month.
My agent sends me my morning report daily. (apparently I'm behind on my todos)
Built myself a core daily tool I call "BrainDown": 📝 Markdown file editor/viewer. 🔄 Dropbox-based file management. 📱 Mobile & keyboard-friendly. 🎙️ Create with voice, text or paste. 🔗 Link to any markdown file (great for my chats with @openclaw agents).
Working title for my next video: "How to create jobs for OpenClaw Agents."