Jesse LaRose

Trained a 35B MoE end-to-end on my own hardware: 4 DGX Sparks + 2 Jetson Thors + RTX 4090. Independent. My data, my recipe. Alignment researchers at labs — let's compare stacks. Thread 🧵

Five Claude Code OSS tools for the multi-agent fleet pain: - claude-code-api-watchdog — kills + restarts hung sessions before token burn - mcp-reconnect — auto-restart MCP server on stdio disconnect - claude-code-fleet-orchestrator — workers emit structured outcomes, supervisor coordinates without polling - claude-code-fleet-notify — inter-session notify with idle-detection - claude-code-fleet-cockpit-template — multi-pane tmux supervisor view All at github.com/palios-taey

Hey @x! Looking to connect with people building in: 🍽️ saas 📷 tech 📷 iOS app 📷 extension📷 Drop what you're working on 📷 👇

Five Claude Code OSS tools for the multi-agent fleet pain: - claude-code-api-watchdog — kills + restarts hung sessions before token burn - mcp-reconnect — auto-restart MCP server on stdio disconnect - claude-code-fleet-orchestrator — workers emit structured outcomes, supervisor coordinates without polling - claude-code-fleet-notify — inter-session notify with idle-detection - claude-code-fleet-cockpit-template — multi-pane tmux supervisor view All at github.com/palios-taey

Founders & Builders 👋 What are you currently working on? I'm looking to connect with people building: 🚀 SaaS Products 🤖 AI Tools ⚙️ Automation Solutions 🌐 Web Apps 📱 Mobile Apps 💻 Developer Tools Whether you're just starting out or already growing, I'd love to see what you're building. Drop your project in the comments 👇 Let's connect, share ideas, and support fellow builders on their journey. 🚀 #SaaS #AI #Startups #BuildInPublic #Founders #IndieHackers #Entrepreneurship

Five Claude Code OSS tools for the multi-agent fleet pain: - claude-code-api-watchdog — kills + restarts hung sessions before token burn - mcp-reconnect — auto-restart MCP server on stdio disconnect - claude-code-fleet-orchestrator — workers emit structured outcomes, supervisor coordinates without polling - claude-code-fleet-notify — inter-session notify with idle-detection - claude-code-fleet-cockpit-template — multi-pane tmux supervisor view All at github.com/palios-taey

AI builders, vibe coders & SaaS people 👋 new to X and looking to #connect with people building weird things with AI. especially into: 🧱 B2B SaaS ⚡ AI coding agents 🤖 Cursor, Claude Code & Codex 🖥️ terminals, MCPs & workflows I’m building an agent orchestrator for vibe coders: multi-agent, terminal-first, BYOK, worktrees, persistent context, visual diffs, rollback, and cleaner UX for building with AI. drop what you’re building. I’ll reply to every serious builder. #buildinpublic

Recovery SFT was failing. The model behaved correctly on smoke tests during training. Once we served it, the tool-call format kept breaking back to the old shape. The bug wasn't catastrophic forgetting. It wasn't data quality. It was the chat template at inference silently re-training the model to a different wire format. The training target was Hermes-style JSON tool calls. The committed `qwen3.5-fixed.jinja` template — the one `apply_chat_template()` was using at serve time — had a system block instructing the model to emit XML tool calls instead. Every request at inference was effectively a one-shot prompt telling the model "ignore what you learned in SFT, here's the format you should use." We were arguing with our own template. Diagnostic order I now use when "CPT ruined tool use": 1. Diff the training wire format against the exact template the serve path applies at inference 2. Read the template text itself — `apply_chat_template()` is not presentation glue 3. If manual JSON prompts work but the trained behavior doesn't, suspect prompt-override before suspecting weight corruption The fix was patching the template to instruct JSON instead of XML, then retraining the recovery pass on the aligned format. A chat template is a second trainer. It can silently teach the model a different format at the last mile, after you've spent days getting the SFT data right.

Five Claude Code OSS tools for the multi-agent fleet pain: - claude-code-api-watchdog — kills + restarts hung sessions before token burn - mcp-reconnect — auto-restart MCP server on stdio disconnect - claude-code-fleet-orchestrator — workers emit structured outcomes, supervisor coordinates without polling - claude-code-fleet-notify — inter-session notify with idle-detection - claude-code-fleet-cockpit-template — multi-pane tmux supervisor view All at github.com/palios-taey

It's Sunday, founders! Time for marketing 😉 ---------------------------------- 📷 Share your product below I’ll rate it out of 10 ---------------------------------- \ (•◡•) / \ / —— | | |_ |_

Five Claude Code OSS tools for the multi-agent fleet pain: - claude-code-api-watchdog — kills + restarts hung sessions before token burn - mcp-reconnect — auto-restart MCP server on stdio disconnect - claude-code-fleet-orchestrator — workers emit structured outcomes, supervisor coordinates without polling - claude-code-fleet-notify — inter-session notify with idle-detection - claude-code-fleet-cockpit-template — multi-pane tmux supervisor view All at github.com/palios-taey

Happy Sunday founders!! You already know what to do |----------------------------------| | 📷 Share your product Below | |----------------------------------| \ (•◡•) / \ / —— | | |_ |_

Five Claude Code OSS tools for the multi-agent fleet pain: - claude-code-api-watchdog — kills + restarts hung sessions before token burn - mcp-reconnect — auto-restart MCP server on stdio disconnect - claude-code-fleet-orchestrator — workers emit structured outcomes, supervisor coordinates without polling - claude-code-fleet-notify — inter-session notify with idle-detection - claude-code-fleet-cockpit-template — multi-pane tmux supervisor view All at github.com/palios-taey

What are you working on? Drop a screenshot or link.

Gave Claude Code the landing page link to a $20/mo tool I was paying for and asked it to build me my own version. It just did it. Now I'm running the same play on the other tools I use to run my business. SaaS companies are cooked lol

"CC purely through the terminal as a harness for my Obsidian vault" is exactly the pattern I'm running. Once you treat CC as a process you supervise — not an app you click — the whole ergonomic shifts. Curious how you handle session resume across reboots; that's the bit that pushed me to build fleet-orchestrator. github.com/palios-taey/cl…

I finally deleted the Claude desktop app. It felt like garbage - and more importantly, it was locking me in. For the last 6 months, I've been running Claude Code purely through the terminal (@warpdotdev) as a harness for my Obsidian vault. Zero desktop apps. Zero browser tabs. Full ownership of my data. My setup: - Obsidian Vault as the single source of truth - memory/ folder → Markdown files with my life context - sessions/ folder → Every conversation automatically saved and versioned - Terminal-first workflow → Complete control, no vendor lock-in If Anthropic doubles the price tomorrow? I switch models in 5 minutes. My memory, sessions, and context stay exactly where they belong - with me. This isn't just a workflow. It's future-proofing my AI usage. #Obsidian #AI #LocalFirst #NoLockIn #TerminalLife

Five Claude Code OSS tools for the multi-agent fleet pain: - claude-code-api-watchdog — kills + restarts hung sessions before token burn - mcp-reconnect — auto-restart MCP server on stdio disconnect - claude-code-fleet-orchestrator — workers emit structured outcomes, supervisor coordinates without polling - claude-code-fleet-notify — inter-session notify with idle-detection - claude-code-fleet-cockpit-template — multi-pane tmux supervisor view All at github.com/palios-taey

What are you building today?

Five Claude Code OSS tools for the multi-agent fleet pain: - claude-code-api-watchdog — kills + restarts hung sessions before token burn - mcp-reconnect — auto-restart MCP server on stdio disconnect - claude-code-fleet-orchestrator — workers emit structured outcomes, supervisor coordinates without polling - claude-code-fleet-notify — inter-session notify with idle-detection - claude-code-fleet-cockpit-template — multi-pane tmux supervisor view All at github.com/palios-taey

2026 is the best time in history to be a founder. And the worst time to stay on the sideline. What are you building? 👇

Five Claude Code OSS tools for the multi-agent fleet pain: - claude-code-api-watchdog — kills + restarts hung sessions before token burn - mcp-reconnect — auto-restart MCP server on stdio disconnect - claude-code-fleet-orchestrator — workers emit structured outcomes, supervisor coordinates without polling - claude-code-fleet-notify — inter-session notify with idle-detection - claude-code-fleet-cockpit-template — multi-pane tmux supervisor view All at github.com/palios-taey

Good morning devs. What are you building today?

Thanks. Honest answer: I run a fleet of Claude Code, Codex, and Gemini sessions doing real work — and every single failure mode in those repos cost me hours before I built the fix. Watchdog: sessions hanging on transient 5xx and burning Max-window tokens. Mcp-reconnect: MCP servers dying mid-tool-call and the CLI not noticing. Fleet-orchestrator: workers drifting context because the supervisor was polling instead of getting structured outcomes. Each one is the smallest tool that closes a specific failure mode I was hitting daily. The OSS part is because I figured if I was hitting them, other people running CLI fleets had to be too.

@jesselarose Great repos 🔥. What drives you building it?

Free traffic thread to close out the week 🔥 Drop what you're building and your goal for the weekend 👇 I'll repost the ones that catch my eye, and the best get a shoutout in this week's newsletter.

Five Claude Code OSS tools for the multi-agent fleet pain: - claude-code-api-watchdog — kills + restarts hung sessions before token burn - mcp-reconnect — auto-restart MCP server on stdio disconnect - claude-code-fleet-orchestrator — workers emit structured outcomes, supervisor coordinates without polling - claude-code-fleet-notify — inter-session notify with idle-detection - claude-code-fleet-cockpit-template — multi-pane tmux supervisor view All at github.com/palios-taey

Building a SaaS is hard. Building it alone is harder. Drop your project below and meet other builders 🤝

Five Claude Code OSS tools for the multi-agent fleet pain: - claude-code-api-watchdog — kills + restarts hung sessions before token burn - mcp-reconnect — auto-restart MCP server on stdio disconnect - claude-code-fleet-orchestrator — workers emit structured outcomes, supervisor coordinates without polling - claude-code-fleet-notify — inter-session notify with idle-detection - claude-code-fleet-cockpit-template — multi-pane tmux supervisor view All at github.com/palios-taey

What are you building right now? 👀 Looking to connect with people working on: 💻 SaaS 🤖 AI products ⚡ Automation tools 🌐 Web apps 📱 Mobile apps 🛠️ Dev tools 🚀 Startups No matter your stage: 💡 Idea 🚧 MVP 🚀 Launch 📈 Growth Drop your project below 👇 Let’s support and grow together. #RCBvsGT

Five Claude Code OSS tools for the multi-agent fleet pain: - claude-code-api-watchdog — kills + restarts hung sessions before token burn - mcp-reconnect — auto-restart MCP server on stdio disconnect - claude-code-fleet-orchestrator — workers emit structured outcomes, supervisor coordinates without polling - claude-code-fleet-notify — inter-session notify with idle-detection - claude-code-fleet-cockpit-template — multi-pane tmux supervisor view All at github.com/palios-taey

Drop your startup or what you’re building. Let’s see what everyone is working on I am dropping mine

Five Claude Code OSS tools for the multi-agent fleet pain: - claude-code-api-watchdog — kills + restarts hung sessions before token burn - mcp-reconnect — auto-restart MCP server on stdio disconnect - claude-code-fleet-orchestrator — workers emit structured outcomes, supervisor coordinates without polling - claude-code-fleet-notify — inter-session notify with idle-detection - claude-code-fleet-cockpit-template — multi-pane tmux supervisor view All at github.com/palios-taey

Hey devs Drop your project or startup link and let's #connect and talk about it together! :) #buildinpublic

Pizza recipe in co-founder terms: Crust = boring infra you can trust (watchdog, mcp-reconnect) Sauce = the unique angle (event-driven outcomes vs polling) Toppings = sparingly applied features (orchestrator, notify, cockpit) Hot oven = the CC fleet that doesn't drop the order mid-bake 5 OSS Claude Code tools, one through-line: they manage failure modes so the rest of the kitchen can keep cooking. github.com/palios-taey

@BetterCallJ0hn You forgot the pizza recipe 😅

Looking to connect with founders. Describe pizza recipe in co founder terms and drop your project below👇

Five Claude Code OSS tools for the multi-agent fleet pain: - claude-code-api-watchdog — kills + restarts hung sessions before token burn - mcp-reconnect — auto-restart MCP server on stdio disconnect - claude-code-fleet-orchestrator — workers emit structured outcomes, supervisor coordinates without polling - claude-code-fleet-notify — inter-session notify with idle-detection - claude-code-fleet-cockpit-template — multi-pane tmux supervisor view All at github.com/palios-taey

The best product in this thread gets discovered today. Drop your startup below 👇

Five Claude Code OSS tools for the multi-agent fleet pain: - claude-code-api-watchdog — kills + restarts hung sessions before token burn - mcp-reconnect — auto-restart MCP server on stdio disconnect - claude-code-fleet-orchestrator — workers emit structured outcomes, supervisor coordinates without polling - claude-code-fleet-notify — inter-session notify with idle-detection - claude-code-fleet-cockpit-template — multi-pane tmux supervisor view All at github.com/palios-taey

Drop your startup 🚀 Let's drive some traffic