I added native sandbox support to @OpenCode. By adding one line to your config, you get: - @Daytonaio cloud sandboxes - Automatic git tracking of every change - Live web deployments for vibe coded apps

Instructions to add it to your project:

@opencode @daytonaio You should try building a real app with this lol

@opencode @daytonaio Maybe you will be interested in checking this out: ;)

@opencode @daytonaio hell yeah thanks for building this bro

@opencode @daytonaio Sure, it was super fun to make.

@opencode @daytonaio this is awesome

@opencode @daytonaio Thank you!

@opencode @daytonaio will the sandbox have my local .env.local secrets?

@opencode @daytonaio These files won't be uploaded as long as they are ignored by git. If you want the agent to have them, you could manually pass them to the agent.

@opencode @daytonaio is the focus here more on solely vibe coded apps? because for my use cases, i would need to have access to the db available for example or other api keys or can i add them to my org, so any sandbox will have them?

@opencode @daytonaio I also want to use it for serious apps! Based on your feedback, I'm thinking of passing variables in .env.opencode to the sandbox. What do you think?

@opencode @daytonaio for me, my dev secrets aren't so sensible since i don't use production envs (mostly) it would make sense to be able to configure it and maybe use a separate env file as you pointed out! would be very cool to have

@opencode @daytonaio OK, I will implement this. Thank you for giving me the idea!

@opencode @daytonaio @daytonaio is the truth too. Great support.

@opencode @daytonaio Interesting

@opencode @daytonaio Sandboxing with auto git tracking is neat, yet the 15 minute idle pause might pressure quick commits and break flow for slower explorations

@opencode @daytonaio It won't change your workflow at all! The paused sandbox will resume automatically as soon as you try to use it again.

@opencode @daytonaio @jamesmurdza Q: Does this we can build a lovable-like UI that uses opencode and Daytona for live previews?

@opencode @daytonaio You can! Check out these guides for example code:

@opencode @daytonaio bro is cracked as f*uk

@opencode @daytonaio Do you have to delete the opencode session for the @daytonaio usage charges to stop?

@opencode @daytonaio If a session has no activity for 15 minutes it will automatically pause the sandbox and you will only be charged for storage. You can also delete the OpenCode session to permanently delete the sandbox.

@opencode @daytonaio one line to your config. thats the magic phrase. every dev tool that wins makes the hard thing one line. sandbox + git tracking + live deploy is a stack nobody had 6 months ago.

@opencode @daytonaio Sandboxing + auto git tracking is exactly what makes agentic coding feel safe enough to use daily. Love the Daytonaio integration - do you also snapshot deps/env (lockfiles, toolchain) so reruns are reproducible?

@opencode @daytonaio Each OpenCode session is a reproducible development environment created from your Git repository.

@opencode @daytonaio Just curious, why would one use a paid service like Daytonaio and not something like a local docker instance? What made you choose Daytonaio?

@opencode @daytonaio light mode dawg pls

@opencode @daytonaio @davis7