2 ms·
I’ve been doing this for a while [1], but ultimately settled on a building a thin transport layer for Telegram to accept and return media, and persistent channe
by elliotbnvl 8mo ago
I’ve been doing this for a while [1], but ultimately settled on a building a thin transport layer for Telegram to accept and return media, and persistent channels, vastly improved messaging UX, etc. and ended up turning this into a ‘claw with a heartbeat and SOUL [2].
[1] https://elliotbonneville.com/phone-to-mac-persistent-terminal/ https://elliotbonneville.com/phone-to-mac-persistent-termina...
[2] https://elliotbonneville.com/claude-code-is-all-you-need/ https://elliotbonneville.com/claude-code-is-all-you-need/
- adamtaylor_13 8mo agoI really enjoyed reading both posts. Thanks for sharing! I, like many others, have written my own "claw" implementation, but it's stagnated a bit. I use it through Slack, but the idea of journaling with it is compelling. Especially when combined with the recent "two sentence" journaling article[1] that floated through HN not too long ago. [1] https://alexanderbjoy.com/two-sentence-journal-approaches/ https://alexanderbjoy.com/two-sentence-journal-approaches/
- elliotbnvl 8mo agoHappy you liked it! Always really nice to get positive feedback. I’ll have to check out the journaling article. I’ve been journaling a lot more lately!
- bavell 8mo agoGreat posts! So far [2] is the only "claw" that has caught my interest, mostly because it isn't trying to do everything itself in some bespoke, NIH way.
- botverse 8mo agoI ended doing a similar thing, but each tg bot can choose what repo/session to attend to. https://github.com/botverse/tgcc https://github.com/botverse/tgcc I found that cc is all you need indeed