I have an llm agent with a harness that stores/logs everything in a structured manner to local files and/or sqlite. This then turns more into casual conversation type stuff. Send it test results, talk about stuff, give it updates, etc, and it handles the rest. Querying the data is pretty straight-forward without the agent since it's plaintext/sqlite. I tried random tools over time but sorta fell out of them. This is kinda the only thing that's stuck.

Could take this further and make it better with structured tooling. Some sorta CLI perhaps, or an API, that the agent knows how to use, then can build a frontend on top or something. For now this works okay.

▲

vitorbaptistaa 2 days ago | parent | next [-]

This is a great idea for a potential startup or, even better, some free software. I started developing something like this but didn't go far.

	▲	nusl 2 days ago \| parent [-]
		Yeah, maybe. The issue I foresee is more that the moat is quite small if you can just build it, so the moat would need to exist in stuff that can't just be built and replicated within a few weeks or something. User base maybe, connections to real resources, some other form of deeper value you can't just copy. Not sure though; I'm not a business person

▲

ncr100 2 days ago | parent | prev [-]

So like a voice capture system, then just feed all that as raw data into an agent?

▲

nusl 2 days ago | parent | next [-]

Suppose you could use voice too, yeah. I built a k8s-based sandbox environment. One pod = one agent, and then a bunch of scaffolding around that to manage it and stuff. "Agent" here is a Claude Code instance within a pod with root access to do whatever it wants inside the pod. The main interface is Discord, but it supports other interfaces/frontends. 1 agent = 1 pod = 1 discord channel, managed by the harness. It can do other stuff too, like spawn its own pods and namespaces to build and host its own infra, new agent teams/sub-teams, but unrelated.

I mostly use text to talk to it, and send files via the Discord file sharing mechanism. Discord has voice recordings too, which are sent as .ogg files, which the agents then turn into text with Whisper.

Not quite plain Claude Code but I didn't want to go into too much depth in my original message.

The end result though is a persistent data store for each pod/agent, and then I can talk to them whenever I want from wherever I want, and interact with it with proper media support and stuff. So I have one agent that's for medical logs and such, and others for various other things.

▲

nusl 2 days ago | parent | prev | next [-]

Is the Dune summary in your bio steganography of some sort, or contains a code? Or just as-is to avoid spoilers?

▲

ncr100 2 days ago | parent [-]

Mostly merely playing.

And in response to this question, I did a new version (WARNING: Has LOUD Star-Wars music): https://starwarsintrocreator.kassellabs.io/FP-LxbQVrUHPe7UvJ...

Thank you! Those would be more constructive ideas than what I originally sought out to do: play with text!

And the text-blob deserves refinement, IMO. It still seems 'cool' to me, though yes it's really really ambiguous just WHAT it is .. and if it were merely "really ambiguous" that would be better for us humans.

I did -want- to avoid spoilers.

I am impressed by the Dune story's epic nature. The all-caps treatment was meant in part to express this epic quality.

Also but more abstractly to call out how humans gather strings of concepts and form them into meaningful stories. So as I present the block of meaningless text it becomes meaningful upon a more technical word-parsing form of contemplation.

	▲	nusl a day ago \| parent [-]
		Haha, fair enough. I read the Dune books through the 4th and enjoyed them. I saw some typos and things and figured maybe there's something hidden in there.

▲

arionhardison 2 days ago | parent | prev [-]

Thats what I did here... w/ the agent and voice capture etc...

https://crohns.ai