Sessions

Close your laptop. The work keeps going.

A session runs on your StellarView, not on the machine you are typing on. Your terminal is a window pointed at it. A build that takes four hours does not care whether you are still connected, and neither does the model working through it.

Start one

./slingshot vibe migration

Name it for the work. You can have several.

Come back to it with:  ./slingshot attach migration

Press Ctrl-B then D to leave it running. That detaches your terminal and leaves everything on the instance as it was.

See what is running

./slingshot sessions

Sessions:
    migration            2 windows — someone is on it
    hotfix               1 window

It says which ones somebody is already attached to, because that changes what happens when you join.

Come back

./slingshot attach migration

From this machine or any other. The session is on the instance, so it is wherever you connect from.

When somebody else is on it

Joining a session somebody is already using is read-only by default. You can watch and scroll. You cannot type.

tmux is perfectly happy to give two terminals one cursor, and two people typing into one session is a real way to lose an afternoon of somebody else's work. If you both intend it:

./slingshot attach migration --shared

How you know it failed

"No session called migration up there." It lists what is actually running. The name is case-sensitive and does not tolerate a typo.

The list is empty after you started one. Sessions belong to the user Session Manager logs you in as. If you started one by another route, on the host directly, it is a different tmux server and this will not see it.

Your terminal is a sliver. The remote session keeps whatever size it had when it started. Detach and attach again to give it the new geometry.

What a session is not

It is not a backup. Everything a session is holding that has not been committed lives only in that session, and nothing recovers it if the instance goes away. Before you stop is the check that catches that.