Overview
Soele is a switchboard for coding agents that I host myself. It is one web page served from my own server, and inside it are all of my Claude sessions across every machine I own. I can open any of them from my phone, watch which ones are thinking right now, type into the one that needs me, and put the phone away. The code is open for anyone to run. It is my best attempt at the interface I actually wanted for working with these things.
The issue
I picked up an iPhone not long ago and noticed the back button is still in the top left corner, a decade of ergonomics research later, on a phone most people cannot reach the top of one-handed. I asked around and most right handed people report that they simply exit the app, restarting the entire flow instead of trying to reach that back button one-handed or hoping the dev utilized the left to right swipe gesture. Leaving it up to devs to implement means it doesn't work all the time, people don't want to have to remember which apps let them swipe and which ones need to be exited, they will simply exit every time. Apple spent 42 billion on R&D in the last year, and back buttons are still only for left handed people..
At least if the interface lives on my own server, then nobody needs my layout to match anyone else's, so the buttons can sit where my thumb is, and someone left-handed can shift the whole thing to the other side, and a theme can be an actual feeling (sharp material, glitchy dark, a 90s garden) instead of a light mode and a dark mode. None of that requires new technology. It mostly requires the interface not answering to a business model that needs it frozen.
The operating side
There is also the operating side, which I did not plan and which turned out to matter more. Claude has a weekly usage cap and I used to hit it by Wednesday without knowing where the tokens went. So Soele grew a usage meter that reads my real rate-limit numbers off the API responses instead of estimating, and a sweep where a local model reads my old chats and suggests what to archive, and nothing gets archived unless I click approve. Projects run in throwaway containers cloned from one I set up carefully once, so a session can wreck its own room and I re-clone the room instead of debugging it. Each piece is simple and none of it is my invention. Having all of it in one place is, as far as I can tell, why I stopped hitting the cap while getting more done. If other people run their own and share what they build on top of it, the pieces hopefully get better for everyone.
How it runs
It runs on a single Python daemon and a single HTML file, no build step, no database, no accounts. You point it at your Claude login, open its port on your LAN, and add it to your phone's home screen. Every session gets a chat view and a real terminal (tmux underneath). The sidebar shows a pulsing dot on whichever sessions are mid-turn. A grid view opens every session at once, tiled, and closes them all the same way. If you run it on several machines, one becomes the gateway and merges the rest. There are docs for building the Android app against your own address, a prebuilt would just point at mine.
Get it
Soele is on GitHub: github.com/Floral-Overcast/SoeleSilico, AGPL. The container pattern is its own small project: github.com/Floral-Overcast/golden-container, MIT. Both came out of the setup I use every day, so they carry my opinions. If it earns a place in your week, there is a Patreon: patreon.com/FloralOvercast.