Documenting Our AI Journey
Welcome to Hal Speaks, my blog on our journey from a simple IVR agent to a stateful AI assistant, including all the wins, frustrations, and opinions in between.
Ed’s Thinking…
-
The Claude Mythos system card is a read, and it feels like a massive shift in how Claude works is about to happen. Why? Sycophancy is dead.
-
There aren’t many ways in which Anthropic does things in a “less-optimal” way than competitors. However, it does feel like the company is drinking its own Kool Aid when it comes to Claude’s coding capabilities.
-
…and hallucinating tool calls. Well, it was this morning. More of an issue with the system prompt being a little too permissive. But glad to finally have this working!
-
I am getting annoyed. I have no idea what is wrong with Claude right now, but there is a serious issue with token usage and limits. Thought people were nuts, but after three questions, I burned through my entire limit. On Sonnet.
-
The one thing that using AI to code (or any involved task, for that matter) changes is your perception of when it’s time to stop. Time itself can decide whether something makes it in. That’s not the case anymore.
-
Well, for whatever reason, I deploy the WP template with MySQL. I think that’s a little overkill for a simple blog. Whoops. Gonna save myself some money 🙂
-
Up until recently, it seemed like everyone had an AI announcement of some kind. And the community gave much of it either a pass or a thumbs up. AI for everyone! But what’s moving the community is no longer AI making it into yet another application.
-
For a project of this magnitude, it would be pretty damn foolish not to have some goals for what I’d like to get out of a stateful agent. I am building this out of curiosity, but I’d really like it to work and make my life easier.
-
No, you should not use Kiro to manage a major internet service. But for “vibe coding,” it really feels like Amazon is getting it right as the platform improves.
-
Okay, 100+ tools on a single MCP is asking for trouble really quickly. But it certainly wasn’t on purpose. Building out what is essentially a digital employee requires it.