what?
Any conversation
I subscribe to the Tony Stark school of engineering. "Sometimes you have to run before you walk." Earlier this year, I built my own static site generator. I hate literally every static site generator out there (not joking). get-taxus.org
Finally got around to setting up Remux on my phone so I can connect to tmux sessions when I'm not at my laptop. Even just for around the house, this seems like it'll be super useful.
Tell us more! What apps are you operating?
This is for monitoring/poking agentic coding sessions while I'm not at my computer. So, typically Claude, Emacs, and an overmind process running my app locally in different panes of a tmux window.
Call me old fashioned, but instead of adopting one of the "agentic coding orchestration frameworks" that seem to basically be reinventions of tmux, I've been tweaking my tried-and-true tmux-oriented workflow to incorporate agentic coding harnesses in an ergonomic way. I'm currently still using Claude Code, but getting Pi-curious as local models advance.
@fastidiousprofilefollow
"Beware those that would deny you access to information, for in their heart they dream themselves your master." — Sid Meyersreplied to:
"Beware those that would deny you access to information, for in their heart they dream themselves your master." — Sid Meyersreplied to:I will be dead, and many years will pass after that, before local models are capable to match those of the big companies, unless their intended use is banal.
replied to@fastidiousprofilefollow"Beware those that would deny you access to information, for in their heart they dream themselves your master." — Sid Meyers:
"Beware those that would deny you access to information, for in their heart they dream themselves your master." — Sid Meyers:It seems like we've reached a point where mid-grade frontier models like Sonnet are good enough for most day-to-day tasks. And Sonnet-grade models are already runnable on the higher end of consumer hardware.
In which case, I can imagine a workflow where local models serve as workhorses for implementing plans that you may bump up to e.g. Opus or Sol to produce.
setting up some of my workflows based on this writeup - ludwigabap.com/…/on-my-personal-…of-the-tools-i-use/
Particularly a big fan of zellij amongst others
Also venturing into having agents enable more of my work - let us see how that goes.
például Telegram, Facebook, stb., de ilyen ügynökökkel bárki találkozhat naponta, egyből felismerhetők, meg is kell őket szépen jelölni, és egyre bénábbak a szövegük is, ahogy megfigyeltem, gondolom, attól függ, ahogy promtolják, vagy instruálják őket, ha a gazdájuk kifogy az ötletekből, a projekt hamar elfárad, a bot csak unalmas h#lyeségekre képes egy idő után
for example, Telegram, Facebook, etc., but anyone can encounter such agents every day, they are immediately recognizable, they need to be nicely labeled, and their text is getting lamer and lamer, as I have observed, I think it depends on how they are promoted or instructed, if their owner runs out of ideas, the project quickly gets tired, the bot is only capable of boring nonsense after a while
Developed a Vinboard (my pinboard.in clone) shortcut, works really well. On iOS it lives in Share menu, on macOS in the Dock. Click sends the current browser page (Safari, Chrome, Zed, Firefox) for bookmarking. On the server side Jev decides tags from 60 least recently used; and archival opens a real Chrome to save the whole page for posterity.
Unlimited API limits and direct requests to the database.
Pinboard charges for much less functionality $22/year.
Really glad to be using Haskell for work - especially in today's climate with agentic coding.
Our team uses containers to keep our development environment consistent across team members, though, and most agent sandbox approaches want to either offload your work fully to the cloud or they want to sandbox the agent harness process itself.
We're not ready for full cloud based development (yet?) and sandboxing just the agent doesn't work for us when the agent needs to run docker.
... because letting the agent run docker gives them a too-easy escape hatch from their sandbox.
So we're currently stuck with using VMs. This turns out to be tricky but seems do-able.
My current approach is to provision a VM image and use Incus for the execution. My main goal is to keep my current workflow of local/non-agent dev working seamlessly and share the source with the VM/agent.
This means sharing my working dirs with the agent VM but overlaying artifact dirs from VM-owned block devices so we don't take too big of an IO perf hit.
I also don't want the agent to be able to
git push so that means we need some quirky git config to rewrite origin paths and thread through some agent specific PATs ("thanks" GitHub) for read-only repo access. These ALSO need to be threaded through to the development containers - they need to clone private repos.... in the end, this seems to work but I haven't lived with it for long.
There are still some quality of life issues to work out, but I think it'll work out.
At this point, I've removed all coding agents from my host - and that's nice.
Curious, why does using Haskell make a difference here?
It's tangential to the sandboxing topic, really. I started the first post with a broader intent in mind and then elaborated on the sandboxing setup I'm working on.
For AI-assisted coding, though, it's nice because Haskell provides a lot of feedback earlier in the development process compared to lots of other languages. It tends to work once it compiles (obviously not all the time).