Beagle puts lobste.rs to work from Slack and Microsoft Teams - reading what it needs, drafting the work, and waiting for your nod.
Computing-focused community centered around link aggregation and discussion.
One thread: ask about your lobste.rs in plain language, and Beagle steps in on its own when something moves. The same conversation in Slack, Microsoft Teams, or Gmail.
@beagle what's the latest from lobste.rs?
Two messages need you today - both linked below with what changed. The next step is drafted, one nod from going out.
A message needs a reply - Beagle catches it in lobste.rs, pulls what matters, and is ready to draft the response for your nod. It goes out when you nod, not before.
With lobste.rs connected, from day one.
Beagle keeps an eye on lobste.rs. When a message needs a reply, it catches it and brings the context to your channel.
It can draft the response for your nod - then waits for your nod before anything is saved or sent.
Ask "what's the state of our messages?" and Beagle answers from lobste.rs and everything else it's connected to, in plain language.
One teammate across both tools. No zap to build.
Yes. Connect lobste.rs with OAuth and Beagle works with it from Slack and Microsoft Teams - reading what it needs, drafting the work, and asking before anything goes out.
Beagle watches lobste.rs for when a message needs a reply and is ready to draft the response for your nod. You can also just ask it questions about your messages in plain language.
Every read is scoped to the teammate who asked - Beagle only sees what that person can already see in lobste.rs - and nothing is sent or saved until you approve it.
No. Beagle is the teammate in the middle. You talk to it in plain language instead of building and maintaining lobste.rs workflows by hand.
