Repository navigation
altitude v0.9.0
Remotes
A remote can hand its tasks' sandboxes off its own machine. Give it two scripts and a
ceiling in serve.toml and it provisions a disposable host per sandbox, runs the task
there, and destroys it when the sandbox ends — the task store, the scheduler and the
tracker stay where they were. The host runs as an ordinary user rather than root, so it
can be a pod on a platform that will not give it a privileged process, and it mounts the
remote's project cache instead of copying it, so a build on a throwaway machine reads and
writes the cache that lives on the remote. A task that parks keeps its work: the host
archives the sandbox before it goes and the next one restores it, so waiting on you no
longer means starting over from the repository. A profile's setup now builds what a task
will actually see — the same mounts, the same ~ — and asks for no privilege, so what a
project installs lands where the task reads it rather than beside it. altitude serve worker --help is the whole setup guide, including what a host image has to carry and how
to bake the layers a start would otherwise rebuild: an image that names itself with
ALTITUDE_WORKER_ENVIRONMENT keeps the layers it built, and a new image gets new ones.
The repository's Dockerfile has a worker target to start from.
Isolation
A sandbox's memory is promised rather than measured: a ceiling is taken when the sandbox
is made and released when it goes, and what is outstanding is bounded, so a second and a
third delegation are no longer handed memory the machine has already spent. A workspace
now starts from the Node image rather than Ubuntu — minutes off a first start, and a
different base for every project's setup command to be written for. A mount says how much
room it needs, so a build is not refused at four gigabytes.
Tasks and agents
A thread's kind is named for what it wants from you, a blocking question or a
ready-for-review, and closing one is one act wherever it is closed. A reply is not a
hand-back: raising the thread is, so an agent that says what it is doing no longer stops
the task by saying it, and a thread opened by mistake is the agent's to close rather than
yours. An acceptance is announced where it happens, so a task completed in Linear leaves
the list on every machine watching it; a message that reaches a running task is reported
as forwarded rather than read back out of the tracker afterwards; and a task put back to
work joins the queue rather than starting a turn where it stands.
Tracker
A refused write to an issue is said again next pass instead of forking the conversation
into a second session, and a task waiting on you names you. A remote no longer tells you
it holds no login of yours when the sign-in was the provider's own, so delegated work
starts on a fresh setup rather than waiting for a second one.
Settings and projects
A machine you have not used before no longer means signing in again to everything that
was already signed in: where an agent or version-control login is on the host, onboarding
and settings offer to import it, naming where its tool keeps it and asking first, because
reading another tool's directory is reading your machine. Imported, it becomes the profile
the next task mounts.