Projects 01
Projects are the cockpit
Every repo starts from a project surface with cards, terminals, browser targets, agents, environment posture, and settings in one place.
Project-first agentic command center
All your agents.
One mission.
Give every project a command center for agent work: cards, terminals, browser sessions, machines, and review handoffs in one live surface — while code and credentials stay on machines you trust.
01
Create a project
Point Skybolt at the repo or app you want agents to help run.
02
Choose a machine
Keep terminals, Docker, source, and CLI auth on a machine you trust.
03
Work from the cockpit
Track cards, agents, terminals, browser sessions, and handoffs in one view.
Platform
Control the project, not a fake cloud workspace
Skybolt keeps the control plane useful without pretending a cloud container is your dev environment. The work runs on your machines.
Machines 02
Execution stays on trusted machines
Choose the Local Machine or a trusted SSH Machine. The Execution Engine owns source files, terminals, Docker access, CLI auth, model keys, and project paths.
Terminals 03
Direct live terminal paths
The desktop engine opens terminals through the selected Project Execution Target and keeps raw PTY bytes local.
Cards & agents 04
Visible agent work
Kanban cards carry goals, ownership, completion packages, review state, and agent-session progress — every merge gated by you.
Browser & environment 05
Debug the app where it runs
Machine-backed browser sessions, console signals, command profiles, and mediated Docker/Compose actions stay project-scoped.
Sync 06
Metadata-first by default
Skybolt syncs status, cards, machine health, and journals. Repo source and secrets are never uploaded by default.
Machine model
Choose once. Keep the sensitive work local.
A trusted Machine advertises capability, opens terminals, brokers Docker/Compose actions, and previews apps — without uploading repo source by default.
loopback engine API
machine-local secrets
project execution targets
mediated Docker broker
01 [machine] local machine ready; ssh targets optional
02 [project] startup path /workspace/repos/skybolt accepted
03 [card] created -> Planning / Needs Discussion
04 [terminal] opened through default execution target
05 [privacy] transcript mode metadata_only
06 [handoff] review-ready package stored as scrubbed metadata
machines
online
capacity
3 / 6
sync
metadata
Privacy boundary
Local secrets stay local
The security model is the product. Skybolt syncs the coordination layer and leaves sensitive project material on the selected Machine unless you explicitly opt in.
Skybolt syncs
- project metadata
- machine status
- cards and approvals
- visible journals
Machines keep
- repo source
- terminal bytes
- Docker credentials
- CLI and model auth
Opt in explicitly
- redacted transcripts
- full transcripts
- chat context brain
- future cloud content
Initialize access
Join the Skybolt waitlist
Early access is opening in stages for engineers and small teams who want a project-first command center for agent-heavy development.