zlacker

[return to "Code and Let Live"]
1. senko+px3[view] [source] 2026-01-11 00:24:04
>>usrme+(OP)
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.

◧◩
2. tptace+Sz3[view] [source] 2026-01-11 00:46:38
>>senko+px3
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.

◧◩◪
3. mcinty+db4[view] [source] 2026-01-11 09:15:16
>>tptace+Sz3
Do you expect that to replace git worktree for getting Claude to work on multiple things in parallel? That was something I was curious about watching the demo video.
◧◩◪◨
4. mcinty+FY4[view] [source] 2026-01-11 16:14:15
>>mcinty+db4
Can’t edit, but adding I noticed that there’s a limit of 3 sprites running concurrently for pay as you go, so that’s probably not a realistic day-to-day workflow.
[go to top]