Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Code and Let Live

fly.io

Post reply on HN
Print view View original

121–130 of 195 posts

Re: Code and Let Live

#121

Post by phelm »

This looks great, i've been wanting a dev sandbox that doesn't run the risk of costing a lot if I forget to turn it off.

I had a few issues

1. manpath: can't set the locale; make sure $LC_* and $LANG are correct

suspect this is due to it inheriting locale from my local machine? easy to get around with some updates to .bashrc

2. the $SHELL environment in my sprite is `/opt/homebrew/bin/fish` I use fish on my local (mac + homebrew) machine and it seems to have inherited from my local machine, its nice to be using fish in the sprite, but seems weird that $SHELL in the sprite points to non-existent path. Slightly concerning that a local env var is being transferred to a remote machine without my explicit permission, I have some sensitive env vars locally.

Re: Code and Let Live

#122

Post by cschmatzler »

timabdulla wrote: post #109

This seems cool, but beware that Fly's other products are not exactly models of stability and polish. API downtime is a semi-frequent occurrence, as are transient API errors and slowness. I've also had a ticket open with support for weeks due to rampant billing issues. For instance, a destroyed instance still shows up in my usage report as actively accruing billed time, and at a rate faster than is even possible (som…

yeah nobody should use this based on reliability and support alone

Re: Code and Let Live

#123

Post by _kb »

yoavsha1 wrote: post #111

I know it's one me for thinking this -- since the domain is fly.io -- but I was really hoping this is some local solution. Not self-hosted, but just local. A thin command line wrapper to something (docker? bubblewrap?) that gave me sort of a containerized "VM" experience for my local machine using CoW.

Check out LXC and the wider Incus set of projects: https://linuxcontainers.org/incus/.

Running IncusOS on some local hardware with ZFS underneath is a phenomenally powerful sandbox.

Re: Code and Let Live

#125

Post by senko »

tptacek wrote: post #64
senko wrote: post #59

I might have missed this in the docs, but is there a way to fork/clone a sprite, or restore a checkpoint into a new one? Use cases: set up my preferred env in one sprite and use that as a template for others; or fire off a few independent sprites with claude code exploring alternative solutions, then choose a winner and reap the rest.

It's coming, and it'll make sense how and why next week when I run the "how this shit works" post. I actually pushed to include it in the launch release. You'd have to ask Kurt why he didn't, but I think the idea is just to get more real-world usage first.

> It's coming, and it'll make sense how and why next week when I run the "how this shit works" post.

Thanks! Also looking forward to reading the post :)

> the idea is just to get more real-world usage first

My particular wish notwithstanding, I agree with this.

Re: Code and Let Live

#126

Post by PanMan »

I liked this idea so much I signed up and linked my personal cc (to my job email) to try it out. Unfortunately, it keeps saying "You must add a credit card to use Sprites with this organization" - even though I just linked a card. No way to continue from there: it's a loop that shows my account with an "activate" button, clicking it shows the error and my account again. Fly.io says I have an account now and it's "in good standing".. :(

Re: Code and Let Live

#127

Post by mehdi1964 »

Treating agents like full computers instead of ephemeral sandboxes makes a lot of sense—durable state and checkpoints solve real pain points that stateless containers force you to work around. Curious how this approach scales when you need dozens or hundreds of Sprites at once.

Re: Code and Let Live

#128

Post by zahlman »

stogot wrote: post #51

> I have kids. They have devices. I wanted some control over them. So I did what many of you would do in my situation: I vibe-coded an MDM. Wait, what?

I'm so far from the target audience for this article that I had to look up what MDM even stands for.

Re: Code and Let Live

#129

Post by causal »

spondyl wrote: post #118

Philosophically, I like Fly and have been a customer since very early on. That said, I dread having to do anything CLI related, which for hobby projects is like once every few weeks. Glancing at the docs for Sprite, I worry that this will be another CLI where a good 95% of the time that I go to invoke a command, my workflow is interrupted by an auto-updater that takes longer than whatever interaction I'm trying to do…

Same. Abandoned fly for Digital Ocean when I found myself hitting my head against the wall trying to get their "just works" to work too often.

Re: Code and Let Live

#130

Post by kasey_junk »

mcintyre1994 wrote: post #114
tptacek wrote: post #90

Earlier quoted context omitted.

One of the coolest things about this is that Claude in his environment --- without him asking to --- knows how to drive Sprites. If you ask it to run a server, it will register it as a local service so it survives reboots. Without you asking to, it'll checkpoint when it makes big changes. I think this is kind of freaky. I can't say enough how, if you're using this like Kurt and Chris have been, you have like, a dozen…

That’s a great demo! For curious mere mortals, are all those custom instructions that make Claude know how to use it public? I’d like to learn how to drive it myself too, just out of curiosity!

Check out the skills that are installed on the box by default
Post reply on HN