Environments
Your work, with room of its own.
A head start for your next project
Choose a template. Everything is yours to configure.
Creating an environment saves its configuration. Compute starts when you do.
A space of your own.
Start this desktop, then connect to pick up your work.
XFCE desktop · Keyboard and mouse controlAt a glance
The configuration requested for this environment.
Port mappings
Port publishing and network access require host permissions.
Configuration
Configure resources, software, connectivity, and privacy.
Advanced YAML configuration
Changes are validated before saving. Stop active work to edit this configuration.
Delete environment
Remove its configuration and private runtime data.
Save once. Start somewhere new.
Capture installed software and files, then create an independent environment.
Commands & activityGuest commands and operation logs
Select a command or start the desktop to see activity.
Host diagnostics
Make sure your host is ready for what’s next.
A checkup for your host
FlintVM doctor checks dependencies, resource limits, and runtime prerequisites.
Run checks to see what’s available on this host.
Detailed output
No checks run in this service session.
Teams
Bring people together. Keep their environments private.
Team membership does not share VMs, credentials or networks. Every VM has a private network link; connections to the FlintVM host and other guest links are blocked. Connections between your own VMs are not available yet.
Pending invitations
Invitation delivery information loads with your teams.
Notifications
Updates from your administrator.
Accounts
A personal workspace for everyone you invite.
People with access
Invite someone to create their own account and environments.
Create a user directly
Invitations and updates
Reach people on this FlintVM host.
Email delivery
Email delivery status loads from the server.
Connected sign-in methods
Connect a provider to this account. Your environments and team access stay with you.
Keep at least one sign-in method connected.
Agent connections
Give your AI a workspace. Keep control of its access.
Connect your harness
Use OAuth with a compatible local client, or create a scoped API key. Credentials only access your own environments.
Streamable HTTP · PKCE OAuth · API keys · Optional built-in stdio adapter
The stdio adapter uses a private key file. Keep that file outside your project and readable only by you. Client-specific setup is documented in docs/mcp.md.
Your connections
Administration
Understand your host. Set clear boundaries.
Resource usage
30-second observations · Up to six hours of retained history
Servers
Capacity for every workspace. Room for maintenance.
Add a server
VM placement and evacuation
Evacuation stops, verifies and moves disks before restarting desktops. Source copies stay fenced until you remove them. An unreachable server is never treated as safely stopped.