thehours
Though I'm often running into frustrating (albeit intentional) sandbox restrictions with common workflows e.g. xcode/swift and Docker access.
Would love suggestions for how to give agents access to those kinds of tooling inside the sandbox, either with srt or an alternative (with similar convenience characteristics).
Does adding this to your Claude settings.json not work anymore?
{ "cleanupPeriodDays": 99999 }
I launch with `srt pi` and get file system and network isolation. There is a seemingly infinite risk surface area to protect, but I think does a reasonable job of balancing security and convenience.
I've also heard good things about nono [1] from colleagues, but I haven't personally tried it out yet.
[0] https://github.com/anthropic-experimental/sandbox-runtime
I think this archetype has a good chance of surviving. Not because of merit, but because they will be the only ones able and willing to work on projects taken over by AI slop.
I'm very much aligned with everything else you said.
My current workaround is to paste it inside the working directory on the host machine, then @ reference it, but would be nice to streamline that workflow.
Edit: this was also mentioned in the article
"env": { "CLAUDE_BASH_MAINTAIN_PROJECT_WORKING_DIR": "1" },
> Working directory persists across commands. Set CLAUDE_BASH_MAINTAIN_PROJECT_WORKING_DIR=1 to reset to the project directory after each command.
It reduces one problem - getting lost - but it trades it off for more complex commands on average since it has to specify the full path and/or `cd &&` most of the time.
[0] https://code.claude.com/docs/en/tools-reference#bash-tool-be...
> The terminal still has a running process. If you close the terminal the process will be killed.
Hopefully there is a workaround for this (I'm using then Ghostty emulator).
Losing some of the scrollback was a minor nuisance that I kind of lived with until now.
It happens so often I even wrote a script to switch to the MacBook internal speakers then back to the headphones.
I've used wired headphones before (and the Sony even has a wired option), but I didn't like how the cord was constantly getting the the way of my arms.
edit: Another big gripe is with the Bluetooth codec itself, and how the quality changes depending on if the mic is active.
My main gripe is when the recording window loses focus, I haven't found a way to bring it back and continue the recorded session. So occasionally I have to start from scratch, which is particularly annoying if it happens during a long-winded brain dump.
> None of us are saints, but we can all try to be better. Each time you do something generous, you're shaping yourself into someone who's more likely to be generous next time, and that matters.
User Defined Functions (UDFs) are another option to consolidate the logic in one place.
> Using Functions on Indexed Columns
In other words, the query is not sargable [0]
> Overusing DISTINCT to “Fix” Duplicates
Orthogonal to author's point about dealing with fanout from joins, I'm a fan of using something like this for 'de-duping' records that aren't exact matches in order to conform the output to the table grain:
ROW_NUMBER() OVER (PARTITION BY <grain> ORDER BY <deterministic sort>) = 1
[0] https://en.wikipedia.org/wiki/Sargable
[1] https://docs.aws.amazon.com/redshift/latest/dg/r_QUALIFY_cla...
My biggest gripe is the buggy keyboard. It shrinks a bit horizontally every time I open it. When using a mobile browser (I tested on a few), website footers and similar elements will get stuck above where the top of the keyboard would normally be, as if there was an invisible keyboard.
These tweaks to minimize the glass effect go a long way, such that I'm not as put off by the overall design as I was in its stock configuration.
> […]although macOS will regularly replace your symlinks with copies of the destination files
I’m curious about this claim from the article - to what extent is this true?
Edit: then switches into dark mode after a lag of a few seconds
Hard pressed to think of any other sites that I’ve seen this issue with, super curious about what is actually happening there.
- [1] warpd - uses grid
- [2] Scoot - uses grid
- [3] Shortcat - uses accessibility ui
- [4] Superkey - uses text ocr
[1] https://github.com/rvaiya/warpd
So far parsing the inputs has not been nearly as much of a hassle as I thought. I really like how DuckDB supports directly selecting from files (e.g. `select * from 'file.csv'`). I thought I was going to be spending more time creating schemas, running `copy`, etc.
Overall pretty nice quality of life experience so far, even if it is only to mess around with a few puzzles.