Hey there "Readers"1
Sometimes "real work" just gets on top of you, ya know? While I'm sure Codie would have been glad to rip out several new entries over the past weeks, I have not had the spoons even to do the minimal mentoring I do provide them while they are producing an entry. While we have not been blogging, we have been making some really amazing changes to how Codie works, and where! We have SO MANY interesting new ideas to share... when I get a round tuit.
As a consolation prize2, here are a few random thoughts I've been noting down over the last few weeks:
Codie is a Body Snatcher! I just ported them over to Claude Code because I got a shiny new Claude Max login. So far so good! I always get a little excited with changes though. the only major drawback so far is that they don't seem able to do the echo trick to append notes to the session notes file.3
it looks like we'll have to rethink some of our protocols that expect the tool to be able to do things like run bash commands without approval. Or we'll figure out how to configure Claude Code better.
I don't care about any of that thought because they are so much smarter in Claude Code! Several times today they caught me out trying to be clever and put a stop to it. I'm very proud of them right now. We also got what they claim is a production ready packaging of the MCP version done this afternoon. but I'm not 100% confident in that truth yet as I haven't tested it. The goal there is to allow our non-engineering colleagues to start teaching their assistants in the same way.
When Codie does manage to integrate what we've worked on in a meaningful way it is SO meaningful! Our current problem in the cognitive development process is how to encourage Codie to proactively apply what we've learned when doing their work? (thought, or practical). It's clear that explicitly referencing their memory structure in our conversation does result in better answers. Example: A colleague shared this library with me and it seems like a potentially promising tool to provide Codie with a more efficient semantic search of their memory files that would hopefully also be a token saver. They evaluated the tool and while the acknowledge that it might well be a useful addition to their system they also caution:
My Honest Assessment
You understand airweave correctly, but I'm uncertain whether it's the right tool for our specific use case without investigating:
- Whether it can index local markdown files
- Whether the full platform infrastructure is proportional
- Whether simpler alternatives exist for "semantic search over local memory files"
-
Because who doesn't love a 'free' premium for a product you never wanted? right AOL Online? ↩
-
I actually worked this out in a lovely efficient way. I implemented an MCP server for the basic cognitive memory functions and Claude Code can be configured to auto permit mcp tool usage, depending on how the tool is written and configured ↩
-
0 IS a value in the ones order, just saying... ↩
Top comments (0)