Cloud sessions and schedules
A cloud session is Forge Code running headless (forge -p) in a fresh E2B sandbox. It clones your repository,
works on the task, and stops. Nothing runs on your machine.
Start one
Section titled “Start one”- From a session:
/teleport cloud <what to do>sends the current conversation along and uses your repository’soriginremote and current branch. - From the console: Cloud sessions → describe the task, and optionally give an HTTPS repository URL and branch.
Repositories are cloned over HTTPS. For a private repository, use a URL with a read-only access token.
Follow it
Section titled “Follow it”/session lists your cloud sessions and their status. The console streams the output live and lets you cancel.
Get the result
Section titled “Get the result”When the session finishes, its transcript comes back as a teleport. /session → Pull the result, or
/teleport pull <id>, resumes it in your terminal. For repositories, the console also shows the diff.
Schedules
Section titled “Schedules”/schedule cloud 1d <prompt> or /schedule cloud "0 9 * * 1-5" <prompt> creates a schedule. Interval schedules
first run one interval from now; cron schedules use your time zone. Each run is a cloud session.
/schedule cloud list shows them, and /schedule cloud remove <id> deletes one.
Plugins in the cloud
Section titled “Plugins in the cloud”/cloud-plugins chooses whether cloud sessions install the marketplace plugins you have enabled locally.