64 karma · joined May 26, 2021
I would like to introduce the Grok Box
I hope they can restore the cartoon cartoon summer resort games.
You do not want to log in one day to find your favorite workflow has changed via updates.
Then again this is all personal preference as well.
First thing to do is try it out in a hobby project see how it works out!
Or make a subagent do the debugging and let the main agent orchestrate it over many subagent sessions.
This can be customized via a shell env variable that I cannot remember ATM.
The downside (upside?) is that the plan will not end up in your repo. Which sometimes I want. I love the native plan mode though.
It’s all a matter of perspective and personal goals, no?
Think of it as TDD.
Wipr 2
It’s a one time paid app that works for both Mac and iOS
Perhaps “journaling-before-answering” lol. It’s basically talking out loud to itself. (Is that still being too anthropomorphic?)
Is this comment me “thinking out loud”? shrug
Since all agents are able to use the terminal I suggest looking up the Gitlab CLI and have it use that. Should work locally and in runners.
Afterwards I make sure the LLM passes all the tests before I spend my time to review the code.
I find this process keeps the iterations count low for review -> prompt -> review.
I personally love writing code with an LLM. I’m a sloppy typist but love programming. I find it’s a great burnout prevention.
For context: node.js development/React (a very LLM friendly stack.)
I think it all comes down to discovery. MCP has a lot of natural language written in each of its “calls” allowing the LLM to understand context.
MCP is also not stateless, but to keep it short. I believe it’s just a way to make these tools more discoverable for the LLM. MCP doesn’t do much that you can’t with other options. Just makes it easier on the LLM.
That’s my take as someone who wrote a few.
Edit: I like to think of them as RCP for LLM