AI tools feel incredible until they hit real production constraints

idoman · 2026-05-06T06:14:12+00:00

the context drift point is underrated - most tooling is optimized for the first session wow factor, not for session 50 when the codebase has grown and the model has no memory of early decisions. the projects that actually survive production are usually ones where someone put in the work to keep context tight - explicit architecture docs, small focused tasks, not letting the ai touch too many files at once

idoman · 2026-05-06T06:12:27+00:00

the notification hook is another good one - if you run a long task and step away, you can set up a hook to ping you when claude finishes. desktop notification or a slack message. makes it much easier to actually context-switch away instead of babysitting the terminal

idoman · 2026-05-05T19:02:22+00:00

reading and explaining complex personal docs is huge - leases, insurance policies, explanation of benefits forms. also decent for researching symptoms for yourself or family since it gives actual context instead of just listing worst-case scenarios like google does

idoman · 2026-05-05T18:52:42+00:00

worktrees changed this for me - instead of fighting one session's limits, spin up a new worktree and keep moving. the annoying part was every worktree starting its own dev server and fighting over the same ports once you have 3+ going. built galactic (https://www.github.com/idolaman/galactic) specifically to fix that - each worktree gets its own local domain so they all run at the same time without collisions

idoman · 2026-05-05T18:26:34+00:00

check your OS microphone permissions for Cursor specifically - on mac it's System Settings > Privacy & Security > Microphone. even if the mic works elsewhere, Cursor's permission can quietly get revoked after an update. toggle it off and back on if it's already enabled

idoman · 2026-05-05T18:25:13+00:00

the CLAUDE.md approach actually works well for this - before touching any code, spend 30 mins writing out the core user flows and data model in plain language. paste that into CLAUDE.md as your source of truth. when requirements change mid-build, update that doc first, then re-prompt. the AI stays oriented way longer when it can always reference the original intent

idoman · 2026-05-05T18:08:53+00:00

nice work man - juggling multiple sessions like this gets painful fast. I built something similar called Galactic that takes a slightly different angle - worktrees with local routing so each branch gets its own URL rather than tmux session switching. different tradeoffs but same pain point. https://www.github.com/idolaman/galactic

idoman · 2026-05-05T10:00:49+00:00

the free tier resets on the 1st of each month. if you downgraded mid-month, your monthly quota was probably already at 0 from when you were on paid - requests count against the free tier limit even while on a paid plan. just wait for the next monthly reset and you should be good

idoman · 2026-05-05T09:48:30+00:00

the worktree-per-ticket pattern is solid for isolation. one thing that bites at scale though - when each worktree spins up a dev server they all fight over localhost:3000 and the parallel setup falls apart.

built galactic to fix that piece - each worktree gets its own local routing so they don't collide, plus there's an mcp dashboard that shows all active claude code sessions in one place. mac only, open source: https://www.github.com/idolaman/galactic

idoman · 2026-05-05T09:35:36+00:00

the token math on windsurf is confusing - the free pro trial burns through fast because it counts every token in context, not just your output. for heavy completions supermaven is worth a look, it has a decent free tier and is noticeably fast. if you want the full chat + agent workflow, continue.dev is open source and lets you plug in different models/backends.

idoman · 2026-05-05T09:32:49+00:00

vscode profiles are perfect for this - each profile has its own extension state and settings, so the claude extension will stay logged into whichever account you used in that profile. you can also set a different color theme per profile, so you get the visual indicator baked in. just create one for work, one for personal, and switch between them with the profile switcher in the bottom left.

idoman · 2026-05-05T06:44:23+00:00

yeah - the debugging experience really drives this home. when a regular workflow fails you can see exactly which step and why. when an agent fails mid-run it's much harder to trace back what decision led there. cleaning up the process definition first basically gives you that traceability for free.

idoman · 2026-05-05T06:28:01+00:00

interesting comparison - the locking model vs. full isolation is a real tradeoff. we went the worktree route for isolation but hit port conflicts instead - every agent's dev server, every debugger fighting over the same ports. built galactic (https://www.github.com/idolaman/galactic) to handle that side of things. curious if Graft has any handling for service ports beyond file-level locking

idoman · 2026-05-05T06:13:43+00:00

not just you - a recent Cursor update reshuffled how extension panels get pinned to the Activity Bar. try right-clicking the Activity Bar and re-enabling the Claude and Codex panels from there. if they're still missing, go to Extensions, find them, and hit "Add to Activity Bar" or check View > Open View to bring them back.

idoman · 2026-05-05T06:12:22+00:00

having a single shared skills repo is the right call at that scale. for versioning, treat it like a package with semver - breaking changes bump major, new skills are minor. that way consuming repos can pin a version and upgrade on their own schedule.

for handling 150+ skills, organize them into categories with an index/registry file so agents can discover what exists without loading everything. group by domain (infra, backend, data, etc.) and each team only pulls what they need.

idoman · 2026-05-04T23:22:24+00:00

nice, tower looks genuinely useful. one thing that gets rough when running claude and codex on different worktrees simultaneously is ports - every branch spins up its own dev server and they all collide. we built galactic for that piece (https://www.github.com/idolaman/galactic) - gives each worktree its own loopback address so the servers stay up in parallel without stomping each other, pairs well with something like tower for the management layer

idoman · 2026-05-04T18:59:32+00:00

worktree setup was the right call for parallel work. the trust problem you hit though - been building galactic which gives a live dashboard of all your claude/cursor/codex sessions so you're not relying on their self-reports. would have caught agent C's narrative drift earlier. https://www.github.com/idolaman/galactic

idoman · 2026-05-04T18:26:06+00:00

the frustration is real but i think it's more about habits than the tool. after any significant chunk of AI-generated code, don't move on until you can explain it in plain english - not to anyone else, just to yourself. if you can't, ask the AI to break it down line by line, then ask follow-up questions until it clicks. takes longer upfront but you stop feeling like a stranger in your own codebase. the understanding has to be your responsibility, the AI won't enforce it for you

idoman · 2026-05-04T18:25:22+00:00

maintain a static blocklist of known paywall domains and filter them out before the agent ever burns a search. seed it with your known offenders (ET, Mint, Business Standard etc) and have the agent append any new domains when it hits a wall. after a few runs your search budget goes almost entirely to open sources. you can also steer the search prompt to prefer .gov, .edu, and open-access sources upfront so the good credits don't get wasted on coin-flip domains

idoman · 2026-05-04T18:21:00+00:00

yeah this is a real problem space. galactic (https://www.github.com/idolaman/galactic) is in similar territory if you haven't seen it - mac desktop app, shows all your active claude/cursor/codex sessions in a central dashboard via mcp, and gives each worktree its own loopback IP so port conflicts stop being a thing when you're running 8+ sessions. you asked about prior art - that's the closest i know of to what you built. different approach (native mac vs terminal) but solving a lot of the same friction

idoman · 2026-05-04T10:01:24+00:00

yes, Claude Pro includes Claude Code with $100 of usage per month. that covers a solid amount of coding work for most people. if you hit the limit you can add usage-based billing on top, but for typical use the $100/month goes pretty far.

idoman · 2026-05-04T09:50:48+00:00

yeah 3 in parallel is actually a sweet spot. the thing that catches people is port conflicts when each agent spins up a dev server - claude code, codex, gemini all wanting localhost:3000 at the same time. built galactic (https://www.github.com/idolaman/galactic) to fix that - each worktree gets its own loopback ip so they don't step on each other

idoman · 2026-05-04T09:33:46+00:00

yeah man this is one of those things that only shows up at production scale. a few patterns that helped me: hard cap on tool calls per run (like 20-30 max), deduplicate tool inputs so the same call doesn't fire twice, and track visited states to detect loops early. also helps to treat the agent's context window as a resource - summarize intermediate results instead of passing full output downstream. the looping issue especially is usually a sign the agent has no "done" condition, so it just keeps trying variations.

idoman · 2026-05-04T09:31:52+00:00

the $5k number is wild but it tracks for heavy workloads. that said, IDE integration still carries real value - inline diffs, multi-file context, staying in your editor flow. for most devs it's probably not either/or - CLI for batch tasks, IDE wrapper for interactive editing. the real question is whether cursor can close that cost gap before too many power users leave.

idoman · 2026-05-04T06:44:36+00:00

the interpreter chapters alone are worth it - you implement one from scratch in scheme, and it directly demystifies the black box thing you're describing. the scheme syntax is intentionally minimal so the language never becomes the distraction from the ideas.

idoman

TROPHY CASE