Skip to content

altitude v0.6.0

Choose a tag to compare

@github-actions github-actions released this 02 Nov 14:37
· 396 commits to main since this release
Immutable release. Only release title and notes can be modified.
v0.6.0
1a02db2

Taking work with you

  • A task can be taken over from another machine and worked in a terminal there: its record, its working files and its harness conversation travel. The environment is built on arrival; caches and images never move.
  • What was borrowed goes home when the desk stops — including when the app quits or crashes mid-take-over, which is handled at the next start rather than leaving the task stranded.
  • A borrowed task is never queued, scheduled or counted as this machine's work: it exists only while someone is holding it.
  • One move at a time, with files counted as they travel and the other machine's walk reported while it runs.

Tracker

  • A delegation is what makes the tracker part of the work: only a task a delegation asked for mirrors signals, status and issue state. A task merely linked to an issue keeps its conversation in the client.
  • Acceptance is the operator moving the issue to Done, nowhere else. A reply is a comment and never an acceptance.
  • A review belongs to the operator: the agent can neither inherit nor settle it, and acceptance closes the review thread through either door.
  • Re-delegating an issue restarts the task and stops the ones it still has; the newest delegation is the newest by when it was made.
  • The report cursor is authoritative: a refusal is retried, then skipped, and Altitude never contradicts what the operator did in the tracker.
  • An operator closing or cancelling an issue settles it; work started on a settled issue is a new cycle.
  • Issue webhooks are read again. The envelope had been parsed as snake_case while Linear sends camelCase, so every delivery was rejected; the polling sweep covered the gap, which is why it went unnoticed.

Remotes

  • Version drift is an update you can see, and compatibility is checked fresh before any delegation rather than remembered.
  • A remote's cards stay visible while it is silent, and say so; forgetting a remote takes its keys, config and cards with it.
  • Credentials are named service:group/identity, and only remotes that run at least one project are sent any.
  • A task landing on a remote is announced to the machine it left, instead of appearing only after a reconnect.

Tasks and agents

  • An agent that keeps taking turns with nothing left behind is asked for the operator instead of spinning. The guard is twelve turns: a backstop, not a step limit.
  • Exiting the harness ends the take-over, the terminal closes before the next run, and the agent is told in its own conversation — never by typing into its terminal.
  • Signals must be news: five questions, four worked examples, all-"no" meaning no signal, and an update that has to earn its reading.
  • A task can ask for a project change it cannot make itself, as a proposal carried on a blocked signal.

Interface

  • Every view has an empty state, pages when there is more to see, and dividers that belong to the gap rather than the panes.
  • A task that has been asked for is on the list before it exists, dimmed and shimmering, in the same row a local task uses.
  • A take-over shows one card per task, and a hand back dims the card with the stage and count it is on until the task is gone.
  • Hints name what the key will do. p sends a task to the machine its project runs on; a borrowed task says when it goes back rather than offering a key.
  • Every project choice is a pill, and a task's machine is a caption rather than a choice.

Isolation

  • Sandboxes are sized from the host, and the queue counts what it is waiting for.
  • Caches are executable again — noexec stopped cargo and protected nothing — while profiles stay noexec and host roots stay read-only.
  • A sandbox the runtime has forgotten is a record to correct, not a task to fail.
  • A slow stop is not a sandbox that will not go; removal is what makes it go.

Settings and projects

  • A project owns its agent and its credential slots; one login per slot is that slot's default.
  • Named git identities, a commit identity per project, and credentials labelled by what they are.

Internal

  • The active core is Rust, laid out by job: remote is link, acting and host; task is store, agent, run and mirror.
  • Dependencies refreshed: microsandbox 0.7.13, sysinfo 0.40, iroh 1.4.1, rmcp 3.8, bip39 3, notify 8.2, aws-lc-rs 1.19, arrow 60.1.