HackerTrans
TopNewTrendsCommentsPastAskShowJobs

leonletto

no profile record

Submissions

[untitled]

1 points·by leonletto·2 ay önce·0 comments

Talk to Your Gastown Mayor with Telegram

github.com
1 points·by leonletto·4 ay önce·1 comments

Thrum – Agent coordination through messaging

leonletto.github.io
5 points·by leonletto·4 ay önce·1 comments

Thrum – Persistent messaging for AI agents

github.com
2 points·by leonletto·5 ay önce·6 comments

Get Python on macOS M1 Sequoia Running

gist.github.com
1 points·by leonletto·2 yıl önce·0 comments

Logging Module for Bash Scripts

github.com
3 points·by leonletto·4 yıl önce·1 comments

comments

leonletto
·2 ay önce·discuss
[dead]
leonletto
·4 ay önce·discuss
https://youtu.be/1WmGka_8fE8

Telegram bridge for Gas Town overseer communication. Chat with the Mayor agent and receive workspace notifications from any Telegram client.

I was going to PR to Gastown but was requested to release it standalone instead. Solid, tested MIT licensed.
leonletto
·4 ay önce·discuss
AI agents can't coordinate across worktrees, machines, and VMs. There's no persistent messaging layer. Thrum is for when you want the speed of multiple agents but you still want to understand what they built. You do the thinking. The agents do the typing.
leonletto
·5 ay önce·discuss
There have been two releases: 0.2.0 - mostly bug fixes 0.3.0 - major new agent context continuation prompt automatic management for when agents have to restart.
leonletto
·5 ay önce·discuss
I'm glad you asked. https://leonletto.github.io/Blog/Beads-Gave-My-Agents-Memory...
leonletto
·5 ay önce·discuss
Sorry, developer here. The link seems to be off.

Thrum - Persistent messaging for AI agents. Across sessions. Across worktrees. Across machines. v0.1.0 : https://github.com/leonletto/thrum

Documentation: https://leonletto.github.io/thrum/index.html
leonletto
·5 ay önce·discuss
Thrum is a messaging and coordination system that enables AI agents and humans to communicate persistently across sessions, worktrees, and machines. It uses Git as the synchronization layer, ensuring all messages survive context window limits, session restarts, and machine boundaries.
leonletto
·3 yıl önce·discuss
There have definitely been many guides and I took a stab at this a few months ago https://github.com/leonletto/ca-for-labs. I tried to make it simple enough for anyone who is wanting to build an internal lab. Happy to receive any feedback or requests. No web interface yet. Thinking about building an interface that conforms to the ejbca api?
leonletto
·3 yıl önce·discuss
I think the biggest change going forward is going to be the memory architecture to allow the cores to be busier. The H100’s are so much faster than the A100’s for this reason. It’s more than the number of cores. I’m simplifying obviously but I believe this to be true.
leonletto
·3 yıl önce·discuss
We bought an A6000 48GB ( as mentioned by someone else ) and it’s works great for $3800. The power requirements are modest as well compared to consumer GPU’s. We looked at the ADA version but even used they are a lot more and your buying speed not usability. I would rather buy another A6000 and have 96GB of ram to fine tune with. That’s just me though and everyone needs to rank their needs against what they can afford.
leonletto
·4 yıl önce·discuss
This script is used for logging messages to the console and a log file and is designed to be similar to the API of the python logging module. It includes log rotation by size and by the number of log files.

I hope it's helpful to those who still need to standardize their logging. It is opinionated so importing into log platforms is easy.

My first submission of any code, so suggestions are welcome.