AI assistant for Daytona
Connect Daytona so Joshu can check development workspace status, spin up test environments, and manage cloud dev infrastructure.
Then $95 a month with no token fees, no resets, and no caps.
What you can ask Joshu in Daytona
You: List all active Daytona sandboxes and their current status.
Joshu queries your Daytona sandboxes, compiles each one with its state, labels, and last activity, and leaves a brief on your desk.
You: Spin up a Daytona sandbox for our payments service branch.
Joshu prepares the sandbox settings and the repository branch to clone, then creates the sandbox once you approve.
You: Stop the idle staging sandboxes in Daytona to conserve resources.
Joshu identifies sandboxes with no activity over twenty-four hours and stages a batch shutdown request for your review.
Cloud development sandboxes, snapshots, and repository branches in Daytona connect directly to your engineering operations.
What Joshu does
Joshu keeps track of your Daytona sandboxes to verify their status, launch sandboxes from your snapshots, and clean up idle ones. When a pull request needs testing or reproduction, Joshu can create a Daytona sandbox once you approve and report back when it is ready for development.
What you do
Authorize Daytona with OAuth and choose which organizations and snapshots Joshu may use. Joshu asks you to approve each sandbox it creates, stops, or deletes.
Why it sticks
Spinning up and tearing down cloud development environments often takes manual terminal steps that interrupt your flow. Joshu tracks your Daytona sandboxes and proposes starts and shutdowns ahead of time, so environments are ready when you sit down.
Permissions and limits
Joshu accesses Daytona through Composio-managed OAuth. It can inspect sandbox status, create new sandboxes, and change their state according to assigned permissions, after you approve each change. It cannot access cloud providers outside your connected Daytona account.
Frequently asked questions
Joshu connects to Daytona through OAuth and manages the cloud development sandboxes you authorize. It checks sandbox status, creates sandboxes and clones Git repositories into them, stops idle sandboxes, and connects sandbox readiness back to your engineering tickets. You work with an assistant who has a desk, a computer, and persistent memory, not a command line utility you must run manually for environment checks.
Yes. Every Joshu runs in its own isolated, sandboxed cloud computer. Workspace configurations and repository paths Joshu reads stay in that private sandbox. Joshu only accesses Daytona environments you authorize, and your data is never used to train public AI models.
No. Creating, starting, stopping, archiving, and deleting sandboxes wait for your approval, and so does running commands inside them. Joshu checks sandbox status and reads logs on its own.
Only the Daytona organizations and sandboxes granted during OAuth authentication. Joshu cannot view or modify environments in separate accounts you do not connect.
The Daytona CLI runs commands on your local terminal when you type them. Joshu is an assistant with long-term memory across Daytona, GitHub, Linear, Slack, and email. It can propose a sandbox when a pull request is assigned to you and suggest shutting it down when the work is done.
Joshu is $95 a month after a 14-day free trial. That includes your sandboxed cloud computer, a dedicated US phone number, an @joshu.me email address, persistent memory across your tools, and all tool connectors, including Daytona. There are no token fees. Paid data and media APIs from the tool catalog are extra, paid per call from a prepaid usage wallet.