What is the Joshu Daytona connection?

Joshu connects to Daytona through OAuth and manages the cloud development workspaces and environments you authorize. It checks workspace uptime, configures development containers from Git branches, stops idle instances, and connects workspace 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.

Is my Daytona data secure?

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.

Will Joshu delete or stop Daytona workspaces without asking?

Joshu monitors and drafts by default. Starting new instances, stopping running workspaces, or deleting environments follows approval rules you configure, ensuring your active coding sessions remain uninterrupted.

What can Joshu access in Daytona?

Only the Daytona organizations and workspaces granted during OAuth authentication. Joshu cannot view or modify environments in separate accounts you do not connect.

What is the difference between the Daytona CLI and Joshu?

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 pre-provisions workspaces when pull requests are assigned and shuts them down when work is done.

Do I need a paid plan?

Joshu is $95 a month with a simple flat rate. That includes your sandboxed cloud computer, a dedicated US phone number, an @joshu.me email address, eight-level cortex memory, and all tool connectors, including Daytona. There are no surprise usage tiers or seat markups.

Home ConnectConnect Joshu to Daytona

Connect Joshu to Daytona

Connect Daytona so Joshu can check development workspace status, spin up test environments, and manage cloud dev infrastructure.

Daytona

“List all active Daytona workspaces and their current runtime status.”

Joshu queries your Daytona instances, compiles active workspaces with branch names and uptime, and leaves a brief on your desk.

“Spin up a Daytona cloud workspace for our payments service branch.”

Joshu configures the environment with repository settings, initiates the workspace launch, and holds for your approval before starting.

“Stop the idle staging workspaces in Daytona to conserve resources.”

Joshu identifies workspaces with no activity over twenty-four hours and stages a batch shutdown request for your review.

Cloud development workspaces, container environments, and repository branches in Daytona connect directly to your engineering operations.

What Joshu does

Joshu keeps track of your Daytona workspaces to verify environment health, launch pre-configured developer instances, and clean up idle cloud containers. When a pull request needs testing or reproduction, Joshu can trigger a Daytona workspace build and report back when the environment is ready for development.

What you do

Authorize Daytona with OAuth and define which organizations or workspace templates Joshu may manage. Specify whether workspace creation and shutdown actions require confirmation on your desk.

Why it sticks

Spinning up and tearing down cloud development environments often takes manual terminal steps that interrupt your flow. Joshu coordinates your Daytona environments in the background so ready-to-code environments are waiting when you sit down.

Permissions and limits

Joshu accesses Daytona using authorized API tokens. It can inspect workspace statuses, create new environments, and trigger state changes according to assigned permissions. It cannot access cloud providers outside your connected Daytona account.

Frequently asked questions

: Joshu connects to Daytona through OAuth and manages the cloud development workspaces and environments you authorize. It checks workspace uptime, configures development containers from Git branches, stops idle instances, and connects workspace 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.
: Joshu monitors and drafts by default. Starting new instances, stopping running workspaces, or deleting environments follows approval rules you configure, ensuring your active coding sessions remain uninterrupted.
: Only the Daytona organizations and workspaces 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 pre-provisions workspaces when pull requests are assigned and shuts them down when work is done.
: Joshu is $95 a month with a simple flat rate. That includes your sandboxed cloud computer, a dedicated US phone number, an @joshu.me email address, eight-level cortex memory, and all tool connectors, including Daytona. There are no surprise usage tiers or seat markups.