I naively went into a work problem thinking that RAG was solved by the service offered at work, and wow was I wrong. Been a fun week so far experimenting with many different methods before doing the academic research, and it's been nice to be validated by outside research.
Any conversation
Run Claude code in docker sandbox (sbx) to ensure it only has current folder access and limited or no network access. Especially since a lot of runs are now in โauto modeโ.
Unless even this is not really so safe!?
@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:Claude will run on auto mode only if you tell it to do it.
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:They've changed the default -
@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:Ah, wow, TIL! Hmm, it is evident I need to visit their blog at least once a week now. Thanks!
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.
de a tapasztalatok szerint a kezelลfelรผlet elfรกradรกsa elลbb-utรณbb magรกval hozza magรกnak a rendszernek az elfรกradรกsรกt, majd lassulรกsรกt, szerintem 1-2 รฉv mรบlva (amikor mรกr senki sem emlรฉkszik majd rรก), forradalmi รบjรญtรกskรฉnt visszahozzรกk a Windows 10 kezelลfelรผletรฉt Windows 12 nรฉven
but according to experience, the fatigue of the user interface will sooner or later lead to the fatigue and then the slowdown of the system itself. I think in 1-2 years (when no one will remember it anymore), they will bring back the Windows 10 user interface as a revolutionary innovation under the name Windows 12.
ะฆะฒะตัะพะบ ัะพะทั ะฝะต ะธะทะดะฐะตั ะณะพะปะพัะฐ, ะฐ ะฑะปะฐะณะพัั
ะฐะฝะธะต ะตะณะพ ะดะฐะปะตะบะพ ัะฐัั
ะพะดะธััั ะผะพะปัะฐ; ัะฐะบ ะฝะฐะดะพ ะถะธัั ะธ ะฒัะตะผ ั
ัะธััะธะฐะฝะฐะผ.
โะกะฒััะธัะตะปั ะคะตะพัะฐะฝ ะะฐัะฒะพัะฝะธะบ
The rose flower makes no sound, but its fragrance spreads far and wide in silence; so should all Christians live.
โSt. Theophan the Recluse
NBA is BACK!! Check out this minimalist NBA score site I made few years ago
nba.5ntoro.com
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).
anything you'd like to talk about
Interface looks sleek. The idea of text based messaging is quite interesting in the age photos and videos based heavy apps.
haha, yes. it's quiet on here though!
Thatโs also the point isnโt it? The people who like this place doesnโt like it too busy. So for them (us?) it will be a nice place to hang out as long as it stay uncommercial and low-key. But to be prosperous and interesting to the creator, it need to grow. ๐คทโโ๏ธ