1broseidon

5 ms·

1. 1.▲
   by 1broseidon 6mo ago

   Both- depending on the work. CLI for anything local and deterministic: code tools, builds, git, file ops. The agent already knows how to exec commands and parse output, and when something breaks you get stderr and an exit code. MCP for dis
2. 2.▲
   by 1broseidon 7mo ago

   100% - you are very right. 4.6 is amazing for orchestration. I even built some tools around agent to agent contracting. I use 4.6 as the brain and then handoff to a more rigid llm like GPT 5.2 or Opus 4.5
3. 3.▲
   by 1broseidon 7mo ago

   I think it’s kinda one of those YMMV metrics. I work for a large company around 80-100k employees and they are ranked on this list. The business unit I’m in is amazing and I truly feel that it’s a great place to work. But ask someone in a d
4. 4.▲
   by 1broseidon 7mo ago

   I have found this to be true too and I thought I was the only one. Everyone is praising 4.6 and while it’s great at agentic and tool use, it does not follow instructions as cleanly as 4.5 - I also feel like 4.5 was just way more efficient t
5. 5.▲
   by 1broseidon 7mo ago

   I think the 'AI productivity gap' is mostly a state management problem. Even with great models, you burn so much time just manually syncing context between different agents or chat sessions. Until the handoff tax is lower than the