Send a session

Time

5 minutes.

You need

• Your team's runner: On your server
• This laptop signed in with loopgate login
• The session's folder in a Git repository, on a branch, with its origin fetched
• The same harness, at the same version, signed in on the runner: Engines, GitHub and a repository

Steps

1. Let the turn finish, then leave the harness. A session that is still open is refused.

2. In the session's folder, send it with what should happen next. The words are optional.

   Copy

   loopgate send "finish the tests and open a PR"

   You should see: the session (<harness> · <id> · <n> turns), its first words, <n> commits · <n> changed files, <branch> → <runner> · Workspace access there, the files that travel, Ignored files are not transferred. and Transcripts can hold what you pasted. Send? with [y/N].

3. Type y.

   You should see: Sent to <runner> · <address> and Bring it back with: loopgate bring <run>.

4. Open the address. Anyone on your team can open it from the portal too.

   You should see: the run's conversation opening with Continues your <harness> session · <n> turns before. With words, the step is working on them; without, it waits for you and has cost nothing.

5. Bring it back, from the same folder on your laptop.

   Copy

   loopgate bring <run>

   You should see: Brought back <run> · <folder> and the command that resumes the session in your harness.

Good to know

• The branch's commits and its uncommitted files travel. Ignored files stay behind.
• The session arrives with Workspace access. Your words reach the step once, verbatim.
• A session is in one place at a time. Sending it again says This session is away. Bring it back with loopgate bring <run>.
• Resuming the laptop copy while it is away can create competing histories. Bring it back first.
• loopgate moves lists every transfer with its state, its runner and its run.
• --to <runner> picks a runner when your org has several. --now copies only what an open session has written so far.
• When the runner has no copy of the repository, an owner or admin's send clones it there. A member's asks them to.

If something is off

• No matching runner is available. Register one in Devices. Add one from the portal's Devices → Add a runner: On your server.
• No session for this repository was found. Run send from the session's folder, or name it with --session <harness>/<id> after leaving the harness.
• This native session is open here. Leave the harness before moving it. Quit the harness, then send again.
• <harness> needs installation or sign-in on this runner. Sign it in on the runner's Settings → Engines.
• The harness versions differ. Use the same tested version on both machines: loopgate engines install <harness> on each.

Next

• Share a run
• The commands