Skip to main content
When a new team member joins, your AI agent can walk them through the workspace: show available templates, explain the environment it works in, and deploy their first instance. A workspace owner or admin first creates the new member’s environment (for example dev-alex) in Settings, Environments and gives it a monthly budget. The new member then connects their agent and picks that environment at sign-in; the agent works only there.

”I just joined the team. What resources and templates are available?”

The agent gives an overview:
  1. list_templates: shows available instance templates
  2. list_environments: the environment this agent works in
  3. list_gpu_types: shows GPU options with pricing
  4. billing_balance: checks workspace credits
Welcome to the workspace. Here’s what’s available: Instance templates: Your environment: dev-alex (picked when you connected me) GPU options (live hourly rates come from list_gpu_types): Workspace balance: $1,247.80 For development, I’d recommend starting with an RTX 4090 using the ubuntu-devbox template.

”Deploy my first instance.”

The agent sets up the new team member:
  1. create_instance: deploys alex-devbox with RTX 4090 using the devbox template
  2. instance_status: waits until running
  3. get_instance: retrieves connection details
  • Deployed alex-devbox (RTX 4090, 24 GB VRAM)
Connect: ssh root@203.0.113.55 Pre-installed: Python 3.11, CUDA 12.4, pip, git, htop, tmux. Your instance runs in dev-alex, separate from staging and production. All environments share the workspace credit balance. Terminate when done to stop billing.

”What is in my environment so far?”

The agent lists what it can see, which is its own environment:
  1. list_instances: the instances in dev-alex
  2. list_volumes: the volumes in dev-alex
  3. list_ssh_keys: the workspace’s SSH keys
dev-alex (your environment)
  • alex-devbox (RTX 4090): running
Team SSH keys: 4 keys registered (macbook-pro, ci-deploy, workstation, alex-laptop) I only see dev-alex. Staging and production are in the dashboard; to have me work in one of them, reconnect Runcrate and pick it at sign-in.

Tools used in this workflow