For the last weeks, Iโve been building a local-first AI desktop companion that lives on your screen.
It can:
- see your screen
- understand your context
- execute actions on your system
But it had one big limitation:
It only lived on your desktop
So I changed that.
๐ Introducing: Blob Connectors
I just added a new layer to OpenBlob:
๐ Blob Connectors
A lightweight Python bridge that connects your local AI to the outside world:
- Telegram
- Discord
- Slack
๐ง What this actually means
You can now do things like:
- send
open spotifyvia Telegram โ Spotify opens on your PC - ask a question in Discord โ your local model answers
- send an email โ get a contextual AI reply
- control your desktop from anywhere
And the important part:
Itโs still local-first
โ๏ธ How it works
All channels go through the same pipeline:
Telegram / Discord / Slack / Email
โ
Blob Connectors (Python)
โ
โโโโโโโโโโโดโโโโโโโโโโ
โ โ
OpenBlob running? Ollama fallback
(localhost) (local model)
โ
Command Router
โ
Desktop action
Everything becomes a normalized Message object.
No matter where it comes from.
๐ Why this matters
This is not just โadding integrationsโ.
This is the first real step towards:
an AI system that exists beyond a single interface
Now OpenBlob is:
- not just UI-bound
- not just voice-bound
- not just desktop-bound
It becomes a distributed interface to your own system
๐งฉ Built for extension
Each connector implements the same interface:
class MyConnector(BlobConnector):
async def receive_message(self, raw) -> Message | None: ...
async def send_response(self, original: Message, response: str) -> None: ...
async def start(self) -> None: ...
So adding new platforms is trivial:
- Matrix
- iMessage (maybe ๐)
- anything with an API
๐ Still local-first
Important:
- runs on your machine
- uses your local models (Ollama)
- no required cloud backend
- transparent behavior
If OpenBlob is offline:
โ it automatically falls back to local reasoning
๐ง Current state
- works across all channels
- still early
- structure is stabilizing
- lots of room for improvement
๐ฎ What this unlocks next
This connector layer enables things like:
- shared memory across all channels
- persistent conversations
- multi-agent systems
- calendar / tool integrations
- real remote control of your system
๐ค If you want to build with me
This is probably the best moment to jump in.
You can:
- build new connectors
- improve routing / memory
- design better UX
- experiment with AI behaviors
๐ https://github.com/southy404/openblob
๐ก Final thoughts
This is mainly an infrastructure update.
By introducing a connector layer and a normalized message interface, OpenBlob becomes:
- easier to extend
- easier to integrate
- less tied to a single UI
Itโs a small surface change โ but a significant internal shift.
This article was originally published by DEV Community and written by southy404.
Read original article on DEV Community