i made it is an open-source version of grammarly that uses chatgpt, grok subscription or even then already local apple intelligence models.
Any conversation
Uhm, not really. Activity Pub comes with a lot more features we don't need - we want to keep this simple and text-only
It doesnโt have the high but it will make you more alert, kind of like tea or coffee.
I just took a look on it yesterday and seems like the stimulant effect is there, so seems like at this point there are mix results on if it actually helps with anxiety and sleep issues. For me personally seems to work just fine but Im not 100% sure how much does it actually does something for me or is just a placebo effect. My thinking is that if I do it from time to time, I can let my body get use to the feeling of a sleep schedule without create dependency on external melatonin dosis or CBD.
Error: Provider rejected the request (invalid_request_error, 400): Claude Code 2.1.75 does not support this model; version 2.1.251 or newer is required. Run
'claude update', or update the Claude desktop app, then try again. [request_id: req_011CedKqBRnC6Qr3m6nKEwNN]
Iโm not using Claude Code. This is how you drop the ball.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).
Economist Lant Pritchett describes shifts in ideas as silly, controversial, progressive, then obvious.
Also:
"Radio has no future. X-rays are clearly a hoax. The aeroplane is scientifically impossible." - Lord Kelvin
". No wireless. Less space than a nomad. Lame." - CmdrTaco