
polymorpheus
2.7K posts

polymorpheus
@polymorph3us
junior dev at heart | happy to be here | LOTR | functions | types


We're extending Claude Fable 5 access on all paid plans, as well as keeping Claude Code’s weekly rate limits 50% higher, through July 19.

very few production agents need a full linux sandbox most apps nowadays just: - read/analyze files (code review) - parse files (pdf/excel) - analyze data (python/js) - calling integrations (curl/mcp) - basic website generation (next/vite) - use browserbase this can be done in a virtual operating system in a few mb of ram using webassembly, like we did with agentOS (git.new/agent-os) all in your existing backend, no extra specialized infra the edge cases that need x86 (compiling rust) or cpu-intensive work (ffmpeg) can opt-in to a full sandbox as needed



It is absurd and insane how much software engineering changed between November 2025 and now.





There's a flaw in Codex's (or should I say ChatGPT's?) subagent orchestration. The spawn_agent tool doesn't let you choose the model or reasoning effort. Therefore, every time 5.6 Sol Ultra spawns a subagent, you're getting another Sol Ultra instance. That's why your quota gets drained so fast.







Warp now supports Grok 4.5. You can use it by plugging in your X Premium subscription. It's smart, and token output is fast. This is real-time:

(1) Today we're releasing Muse Spark 1.1 -- a strong agentic and coding model at a very low price. It's available through our new Meta Model API and in Meta AI.



I just declared a moratorium against AI-written change descriptions (e.g. PR and commit messages, also issues/tickets) from my team. AI was writing change descriptions that were worse than useless to me as I tried to review PRs: outlining details of the code that could easily be seen by looking at the code, but omitting the higher-level framing needed to understand broadly what the code is doing. I think people like having AI write these things because the output looks structured and thorough, which makes it feel professional in a way. But this isn't actually valuable. Concise, high-level descriptions are better for everyone. If I need to use my own AI to interpret what your AI wrote then something is wrong. Let AI write code, sure, but for the description, I'd rather see your prompt than your output. We could maybe have extended agents.md with guidelines on writing descriptions, but this seemed a bit pointless since a good, concise change description only takes a few minutes to write -- not a significant time savings to delegate to AI. At least, it doesn't take long if you understand the code -- and if you don't understand the code, then I'm definitely not merging it.






