I'm setting up a small orchestration around zellij (I have almost no experience with tmux, so I went with the "modern" alternative), upterm and qrencode that allows me to 1) generate a claude code instance in a persistent session 2) make it controllable remotely via upterm 3) scan a qr code to copy the upterm server's ssh url on my phone so that I can paste it in termux.
I wonder if it would be more ergonomic to connect to the aoe window on my phone for when I have more then one claude code session to keep track of. I'm not against switching the zellij part to tmux.
Tbh that's exactly what I'm using aoe for: termius on my phone ssh into my Mac mini and then use aoe to check in on each agent session. Just make sure you check out the readme if you do this because at least for termius there's a quirk to make tmux and TUI happy. The recommended approach is to run aoe itself inside a tmux session which then will spawn additional tmux sessions as needed.
After your comment I tried to do something with my phone but tmux + claude code is definitely not great on mobile though the main view of aoe works decently.
Thanks for giving it a try! If you can think of any improvements I'm certainly all ears. What i've been doing is using the ios + termius + aoe setup to just keep tasks moving forwards. I log in from my phone, see which sessions are waiting for me, and then type just enough to keep them moving forwards until I get back to my desktop where then I can use aoe again to keep them moving
I've been waiting for Logseq DB to come out to replace Google docs for my team. So your offering is interesting, but
1) is it possible to use Obsidian like Logseq, with a primary block based system (the block based system, which allows building documents like Lego bricks, and easily cross referencing sections of other documents is key to me) and
2) Don't you expect to be sherlocked by the obsidian team?
In Obsidian you can have transclusions which is basically an embed of a section of another note. It isn't perfect, but worth looking into.
Regarding getting sherlocked; Obsidian does have realtime collaboration on their roadmap. There are likely to be important differences in approach, though.
Our offering is available now and we're learning a ton about what customers want.
If anything, I'd actually love to work more closely with them. They are a huge inspiration in how to build a business and are around the state of the art of a philosophy of software.
I'm interested in combining the unix philosophy with native collaboration (with both LLMs and other people).
That vision is inherently collaborative, anti lock-in, and also bigger than Obsidian. The important lasting part is the graph-of-local-files, not the editor (though Obsidian is fantastic).
> 1) is it possible to use Obsidian like Logseq, with a primary block based system (the block based system, which allows building documents like Lego bricks, and easily cross referencing sections of other documents is key to me) and
More or less yes, embeddable templates basically gives you that out of the box, Obsidian "Bases" let you query them.
> 2) Don't you expect to be sherlocked by the obsidian team?
I seem to remember that someone from the team once said they have no interest in building "real-time" collaboration features, but I might misremember and I cannot find it now.
And after all, Obsidian is a for-profit company who can change their mind, so as long as you don't try to build your own for-profit business on top of a use case that could be sherlocked, I think they're fine.
Doesn't say real-time there though? But yeah, must be what they mean, because you can in theory already collaborate on notes, via their "Sync", although it sucks for real-time collaboration.
This is the ultimate cope out: taking technology as a singular entity that evolved outside of human control and is simply commented on by passive observers who are simply "pessimist" or "optimist" about it instead of people whose lives are meaningfully impacted by it.
The trick to do so is to flatten human experience under the determinism of "efficiency" (which you euphemistically called "quality of life"). This way "optimists" can dismiss nuanced oppositions to a lack of regulations as "luddism" and fold together anti-vaxxers and AI skeptics, as if those are the same people, with the same motivations or arguments.
This also conveniently distracts from the fact that technological pessimism exists as a contrast to periods of technological optimism, which helps evade the question of what changed: after all, pessimists aways existed, as your link shows.
I would suggest unfolding the "pessimist" reductionism and questioning why AI skeptics are not stem-cell skeptics. This will probably help avoid arguments that sound very much like "the end justify the means".
I would recommend re-reading The Ones Who Walk Away from Omelas as a companion story then. Maybe you'll get to underhand techno-pessimism as something more than the the result of people "forgetting the incredible technology that makes their quality of life real".
Why Don’t We Just Kill The Kid In The Omelas Hole by Isabel Kim. My favorite short story of 2024, and very much worth reading if you’re at all familiar with LeGuin’s original story.
They’re both short stories, less than 10 minutes to read.
If you’d like to read novel length LeGuin, “The Left Hand Of Darkness” and “The Dispossessed” are excellent. Much of her most lauded work shares a universe, but each novel stands alone and doesn’t share relevant characters, let alone protagonists.
I also thought this and didn’t get the point.
But the link was published 2013 and maybe for users not used to personal blogs but only social media nowadays it’s worth mentioning…
Looks great, and it has some features and polish that I would love Logseq to have natively, but overall I prefer the customisation potential of logseq with tags, templates, block refs etc.
I wonder if it would be more ergonomic to connect to the aoe window on my phone for when I have more then one claude code session to keep track of. I'm not against switching the zellij part to tmux.
reply