/ai/spell/search (toolshed)

[bfollington]

• Integrate blobby with clipper
• add /ai/spell/search route
• add behavior tree implementation + search agent
• one strategy for search will try to make use of collections, if they exist, by looking at tags starting with # e.g.
  • { key: '#email', value: ['an-email-key', 'another-email-key'] }
• extract llm and redis library code

The idea is to create a set of building blocks (strategies) we can compose into different behavior trees. Those strategies can mix and match platform features, so I've factored those out into lib. This is basically what I meant by functional-core, imperative-shell the other day. In practice I mean splitting the service concerns from the API concerns, the services do not need to care that they are exposed via HTTP endpoints.

I've got some mixed file naming conventions going on, can do camelCase or kebab-case but it feels a bit weird to export one function called scanForText from a file called scan-for-text.ts?

[jakedahn]

Just a heads up, I already have some fancy logging stuff using pino-logger https://github.com/pinojs/pino

It's currently only hooked up to hono via a middleware, and not super obvious how to use elsewhere: https://github.com/commontoolsinc/labs/blob/main/typescript/packages/toolshed/middlewares/pino-logger.ts

I'm cool merging this as-is, but I'll probably make a follow-up pass at killing pino or this setup in the next week or two.

[bfollington]

SGTM! I would prefer to use a library, I was just losing my sanity without context in the logs. Let's rip it out soon 👍

[bfollington]

Since the routes I'm testing using hono/client, they need an actual server to hit I think? Maybe you can pass a router directly to the client.

Regardless, this actually worked but there's no LLM configured in CI so it fails.

Tests are commented out, they work locally for me.

[bfollington]

Some tweaks, I had to resolve every type error to run the spell tests