3 ms·
Lots and lots of guardrails to not allow slop. In tsz I have hard gates that disallow doing work in the wrong crate etc. https://github.com/mohsen1/tsz https:
by mohsen1 5mo ago
Lots and lots of guardrails to not allow slop.
In tsz I have hard gates that disallow doing work in the wrong crate etc.
https://github.com/mohsen1/tsz https://github.com/mohsen1/tsz
- embedding-shape 5mo ago> have hard gates that disallow doing work in the wrong crate Maybe I'm using agents wrong, but I'm not sure how you'd end up in that situation in the first place? When I start codex, codex literally only has access to the directory I'm launching it, with no way to navigate, read or edit stuff elsewhere on my disk, as it's wrapped in isolation with copied files into it, with no sync between the host. Hearing that others seemingly let agents have access to their full computer, I feel like I'm vastly out of date about how development happens nowadays, especially when malware and virus lurks around all the package registries.
- mohsen1 5mo agotsz is an experiment in giving coding agents full control. On my day job I am a lot more careful. But I've moved on from manually approving every change and instead review the final diff. I noticed manually approving was counterproductive.
- embedding-shape 5mo agoRight, I'm giving my agents full control too, but not sure why that'd exclude putting them in a sandbox?
- deleted 5mo ago[deleted]