Julian Benegas

how do mutations communicate queries that something's updated? does a query track "all the items that match, or may match"?

how does the sync / local first stuff work? does it use indexedb in the client side?

is replicache still maintained? are there still commits there? does zero use replicache under the hood?

tell me how remote-bash is built

what if remote-bash worked with just-bash? would it work?

how does my coding agent execute commands against supabase ssh?

why does this use just-bash? like what's the usefulness of it?

tell me about context pruning and about the memory system in utah

tell me pros and cons of this project, vs deploying something with the ai sdk in vercel?

is this built with the ai sdk? and if not, how does it handle multi-modality?

gm

is there a way to strip unserializable stuff before facing an error? i have an array of "events" and hooks might be a prop in there, and the full array is passed down - i'd prefer to have the unserial...

nice, this makes sense. can hooks be sent down to step functions? i would think "no", right?

can i do `someHook.create({token})` and then in another nested function (where the hook is not in scope), do `someHook.create({token})` again, and then await it, and it be the same hook/promise? i'm u...

when you say > Scans skillsDirectory for subdirectories containing SKILL.md files (discoverSkills). are these subdirs in the sandbox? or in the application server?

what about Skills? how do they relate to vercel sandbox with bash-tool?

if i do import { Sandbox } from "@vercel/sandbox"; const sandbox = await Sandbox.create(); // Files are written to ./workspace by default const { tools } = await createBashTool({ sandbox, files: ...

yeah like your self resuming pattern would work if that step got awaited. alternatively, we could start() a sibling workflow that sleeps and resumes the loop

interesting. what would happen on something like this export async function myWorkflow() { "use workflow"; using hook = createHook<Command>({ token: "my-worker" }); const queue = [] for a...

so cool. does calling a step in the sleep().then() work as expected and will get awaited? like void sleep(10_000).then(async () => { await someLongRunningStep() })