I’ve been wondering if chat is the wrong interface for slower local models (and some projects) and maybe something like a ticket system is a better fit. I just decided how I would test this idea on my available hardware before I go drop money on a Mac Studio or GPUs. I’ll probably have a POC this week. There is nothing novel here, just need to spend the time to get it working for me.

▲

alexhans 4 hours ago | parent | next [-]

Having a thin python/ts orchestrator and workers that pick up tasks from the directories like events and decide whether to make deterministic calls and wait is pretty standard albeit custom way of doing things in this space where you're bottlenecked by the concurrent call your workers/agents can make.

The hard thing is always keeping complexity low and being ZeroOps.

▲

antondd 2 hours ago | parent [-]

Are there any frameworks/scaffolding/harnesses or general resources on this you can share? I’d love to learn more

	▲	walrus01 2 hours ago \| parent [-]
		Most any ticketing system can integrate with ordinary IMAP and smtp email flow, so you can really use any agent that can "do" inbound and outbound email to talk to a self hosted ticket queue.

▲

digitaltrees 2 hours ago | parent | prev [-]

This is actually really smart. It would be like working with a team of humans.

I have a 3 Mac Studio set up and built an IDE / harness (propelcode.app) and would be interested in contributing if you’re open to collaboration