Skip to content

Releases

v0.72.0

Choose a tag to compare

@github-actions github-actions released this 16 Nov 04:43

Changed

  • Records refuse steps their lifecycle does not have. A session's status, a session's archive, a waiting message, an agent, an idempotency record, a trigger's firing and a trigger's run each follow a written table of states. Every store checks its writers against the table: an append that would take an ended session along a step the table lacks, or a second answer written over a stored one, changes nothing and is refused. Tests drive each writer through every pair of states and every pair of racing writers, on every store that has one and on Postgres. The tables are rendered into Lean proofs and TLA+ models that the quality gate checks, together with models of the session lease and the trigger lease.
  • The session status type reads text and names its empty value. session.ParseStatus reads a status from text and session.NoStatus is the empty one a list uses to narrow by none.

Fixed

  • An idempotency answer already stored is no longer overwritten. A second Finish of a record wrote its answer over the first, so two requests that held one key could leave the answer of the second. It is now refused and the first answer stays.
  • A slow request no longer overrides the retry that replaced it. A request that outlived its idempotency reservation could store its answer over, or remove, the reservation of the retry that took its place. Its answer is now refused and its removal leaves the retry's reservation alone.

Release evidence

v0.71.0

Choose a tag to compare

@github-actions github-actions released this 15 Nov 19:22

Added

  • The documentation has a page for each reader. docs/README.md
    indexes every page by who asks; docs/local.md runs the server on one
    machine with everything it needs; docs/install.md covers the image
    and its signature, the database, keys, probes, the manifests and
    upgrading; docs/api.md covers the concepts, the flows a client
    follows and the errors to branch on; docs/authorizer.md is the
    contract an authorizer answers; and docs/security.md says what Topos
    sees and keeps and what an operator keeps safe.

Changed

  • Built with Go 1.27.4, which fixes GO-2026-6859.

  • A short deadline no longer leaves the next call without a service
    token.
    A call to another service that gave up while its token was
    being fetched, as the 300 ms Oversight check does after each token
    expires, now leaves the fetch to finish and hold the token, so the
    next call is answered at once.

  • SECURITY.md names the test that holds each commitment. It lists
    what Topos protects against a caller, a steered model, the code a
    session runs and a runner, and what it does not defend. Report a
    vulnerability through GitHub's private vulnerability reporting or by
    email; the organization's policy sets the response times.

Fixed

  • make token prints the token alone. The build's output goes to
    standard error, so TOKEN=$(make token) holds a token a server
    accepts.
  • Stopping make run stops the server. The target now execs
    out/toposd, so the server is make's own child whatever the shell
    does with its last command, and the SIGTERM that make passes its
    child when it is stopped reaches the server. A shell that stayed the
    server's parent took that signal itself and left the server running
    on its ports.
  • A server with no sandbox service creates a session of an agent that
    names no machine.
    With no TOPOS_CELLA_URL and TOPOS_HOST_SESSIONS
    off, such a session was refused at create with machine_unavailable,
    although a session that calls no tool needs no machine. It is now
    created on Cella's kind, as with a Cella, and its first call of a tool
    that acts on the machine answers machine_unavailable as the call's
    result; the turn goes on. An agent that names more of a host machine
    than its kind is still refused at create.
  • A list filter that names no owner narrows no list. An allow whose
    filter has no owners, such as {}, listed nothing for agent.list
    and for a trigger.list that names an owner, while session.list and
    an unnamed trigger.list read it as no narrowing. Every list now reads
    it as the shared authorizer contract does: an empty owners does not
    narrow by owner. An authorizer that sent {} to hide every agent must
    deny the list instead.
  • The repository's conformance runs hold every list to a decision.
    They now pass conformance.WithPageActions(), as docs/authorizer.md
    tells an authorizer's author to, so an endpoint that answers a list
    with a page of its own and no allow, which toposd cannot read,
    fails them.
  • The documentation says what the server does in four more places.
    docs/configuration.md says a boolean is read as Go's
    strconv.ParseBool reads one, so 1 and TRUE are true, lists
    OTEL_EXPORTER_OTLP_ENDPOINT and the OpenTelemetry variables beside
    it, and links the section of spec 028 that designs toposd check.
    docs/holding-triggers.md says an authorizer on the shared scaffold
    that does not know trigger.hold makes the hold routes answer
    authorizer_unavailable, not forbidden. The authorizer package
    says a fork whose send is refused is only logged, since toposd sets
    no event sink.

Security

  • An authorizer over plain http on another host needs the
    operator's consent.
    TOPOS_AUTHORIZER_URL with http:// on a host
    other than loopback now stops the start naming
    TOPOS_AUTHORIZER_INSECURE, as TOPOS_CELLA_URL does with
    TOPOS_CELLA_INSECURE, because the authorizer's bearer and every
    question with the caller's claims would travel in the clear. An
    installation that uses such a URL must, before it upgrades, either move
    the authorizer to https, or set TOPOS_AUTHORIZER_INSECURE=true for
    an authorizer reached over a network it trusts. A loopback URL, such as
    http://127.0.0.1:9000/authorize, needs nothing.
  • The network policy no longer admits the Dash0 collector. The collector
    is retired, so the egress rule to it is gone. Telemetry export stays off
    until a deployment sets OTEL_EXPORTER_OTLP_ENDPOINT.

Release evidence

v0.70.0

Choose a tag to compare

@github-actions github-actions released this 05 Nov 19:08

Added

  • A release can deploy itself. The release workflow has a deploy job
    between the build and the publish stage, which applies deploy/prod with
    the image pinned by digest, waits for the rollout and runs
    tools/smoke/release.sh against the live origin. It runs only where the
    repository variable TOPOS_RELEASE_DEPLOY is set, so a fork publishes
    every artifact and deploys nothing. deploy/prod holds the maintainer's
    production manifests and deploy/prod-bootstrap the identity the job
    deploys with. Neither is part of an installation: the base and the
    bootstrap are still what to install from.

  • GET {base}/version is public. With TOPOS_BASE_PATH set, the
    build's version, commit and build_time are also answered under
    the base path with no token, for example /v1/agents/version, so a
    deployment behind an ingress that forwards only that prefix shows which
    release it runs. The release smoke compares the served version with the
    tag.

Fixed

  • A session id has one spelling. Ids are read only in the uppercase
    form topos mints, so a lowercase spelling of an id no longer reaches the
    same session directory.

  • One-line text fields refuse hidden characters. A session title, app
    name or metadata value with a bidirectional control character or invalid
    UTF-8 is refused, and a long line the read tool cuts ends in an ellipsis.

  • Retry-After is read and written safely. A very large value from a
    model provider no longer turns into a negative wait, and topos writes the
    header in whole seconds, rounded up.

  • Request ids are checked. An X-Request-Id that is empty, longer than
    128 bytes or not printable is replaced with a minted one before the
    authorizer, the logs and the response see it.

  • A list filtered by labels lists nothing. When the authorizer's filter
    names labels, a list returns no objects, since no object carries a label
    to match.

  • Postgres migrations take a clean URL. A pool_ parameter on the
    database URL no longer reaches the migration connection.

Release evidence

v0.69.0

Choose a tag to compare

@github-actions github-actions released this 03 Nov 00:16

Added

  • A call records what it reaches. agent.tool_use records scope,
    the reach the call was decided on, before the call waits for a
    person: whether it can be undone (undo), the boundaries it crosses
    (crosses), the class and kind of its target, whether it is a first
    contact, and source, service when the decision service read the
    call and topos when the scope is Topos's own claims alone. A client
    can show "cannot be undone" or "makes the app public" beside the
    command. No member holds a path, a host, a branch or an app's name. A
    bash call without a decision service records no reach but its
    source: show its reach as not known. See
    docs/how-a-call-was-decided.md.
  • A confirmation can say how the person answered. A client can add
    answer_ms, details_opened, suggestion_shown and surface to a
    user.tool_confirmation. The server records them, and refuses a value
    of another type or outside its range as invalid_request. Send them
    only to a server whose GET /v1/openapi.yaml lists answer_ms; an
    older server refuses them.
  • Repeated refusals hand the session back to the person. After 3
    refusals in a row or 20 in a session, toposd records
    session.denials_reached. On a turn a person began, every call that
    changes something then waits for the person, with decided_by: denials, until their next message. A turn a trigger began stops with
    the new stop reason denials, and the person's next turn asks the
    same way, and so does a run of a rollout. Subagents share the counts.
    TOPOS_DENIALS_CONSECUTIVE and TOPOS_DENIALS_TOTAL set the limits,
    0 turns one off, and an authorizer's denials can lower them for a
    session. session.denials_reached is a new event type, which a runner
    of an earlier release refuses with schema_too_new: upgrade the
    server and the runners together.
  • A subagent's refused calls warn its caller. When calls of a
    subagent's run did not run because a rule or the person refused them,
    the result of its agent or send_message call starts with a fixed
    warning, and the tool.result records refused in its meta.
  • The decision service learns what each call reaches and how each
    answer was given.
    Each call is sent with Topos's claims about its
    reach (scope, target), the limits its machine enforces
    (environment.holds: egress, protected_refs, checkpoints), the
    visibility of the session's repositories (environment.repositories),
    its subagent depth, and what an agent or send_message call hands
    over. Each answer carries the four fields of its confirmation,
    waited_ms from the log, and remembered, and never the note or the
    pattern.
  • An authorizer can name the organization's hosts. An allow of
    session.create, session.fork or session.send may carry
    boundary, the hosts the organization owns. The session keeps the
    latest one, and a web_fetch tells the decision service whether its
    host is outside them.
  • A delivered repository records its visibility. The first machine's
    session.machine names each repository's visibility, private or
    public, from one read with no credential at the git host when the
    repository is delivered.

Changed

  • In learned, the decision service's new kinds of ask. An ask of
    kind wider (the call reaches wider than any the person allowed)
    waits for the person, as split does. An ask of kind short
    (answers that agree, still in the ask band) or few (approvals that
    are not enough), and any kind Topos does not know, is decided by the
    rules and the risk score.
  • A learned allow runs a call the risk score asks about only where the
    person's approvals cover it.
    TOPOS_DECISIONS_LOOSEN sets this for
    learned and decide. covered, the default, lets an allow decide
    only when the prediction carries cover.covered: true, and leaves
    every other allow to the rules and the risk score, with the
    suggestion recorded. A decision service that sends no cover no
    longer runs a call the risk score would ask about, so an installation
    in decide or learned with such a service sees more asks until the
    service sends cover. never lets the stricter of the allow and the
    rules' verdict decide.
  • The decision service is not sent a subagent's task. An agent,
    send_message or advisor call reaches the decision service without
    its input.

Fixed

  • A background command's files are gone once its log says it
    exited.
    On a machine that runs commands in a stage sandbox, a long
    command's script file was removed after the exit line was written, so
    a reader that saw the line could still find the file. The file now goes
    first, as it already did for a command run on the host itself.

v0.68.1

Choose a tag to compare

@github-actions github-actions released this 02 Nov 23:13

Changed

  • The API document describes decided_by, decided_by_rule and a
    create's rollout.
    An agent.tool_use's decided_by lists the
    layers that decide a call, decided_by_rule says what rule within the
    layer it names, and a create's rollout states its id's rule. A
    generated client or reference now shows what each means.
  • The API document describes decision_org, evidence_ratio and
    ask_kind.
    An agent.tool_use's decision_org names the
    organization of the key that its decision was sent under. A
    suggestion's evidence_ratio says how much the person's answers
    settle it, and its ask_kind says if an ask is unsure or split.

Fixed

  • A split ask does not mean that the answers disagree. The
    documents, the code comments and the notes of v0.68.0 said that it
    does. A split ask has an evidence_ratio of 0.5 or more, and an
    approval probability that is still between the profile's thresholds.
    The person's answers can agree or disagree, and more answers that
    agree can move the probability past a threshold. The behavior does not
    change: in learned, the service decides a split ask as before. See
    docs/how-a-call-was-decided.md, which gives an example.

v0.68.0

Choose a tag to compare

@github-actions github-actions released this 02 Nov 09:53

Added

  • A suggestion records why it asks. The suggestion of an
    agent.tool_use keeps the decision service's ask_kind and
    evidence_ratio when the service sends them: for an ask, unsure
    (too few answers) or split (answers that disagree), and how much the
    person's answers settle the suggestion. A client can show why a call
    asks without asking the service. A service that sends neither, and an
    event written before this release, leave both out. See
    docs/how-a-call-was-decided.md.
  • A session names the organization that owns its agent. A hosted
    session of an organization's agent records the organization's ID as
    org, fixed at its create and its fork. A session of a person's
    agent has none.
  • TOPOS_DECISIONS_ORG: initiator or agent. initiator, the
    default, keeps the keys of v0.67.0. With agent, the decision
    service keys a call of an organization's agent by the organization.
    The organization's cost profile then applies, and a person's answers
    there stay apart from their own context. Every other call keeps the
    initiator's subject. Set it after the clients and the authorizer of
    the decision service read organizations.
  • A call records the organization it was decided under.
    agent.tool_use records decision_org, the organization of the key
    that its decision was sent to the decision service under. A client
    that reads the service's records of a call reads the organization
    from it, and the initiator's subject from an event without it.

Changed

  • A decision names the layer that decided it. Topos sends each
    decision to the decision service with the source
    topos/<mode>/<decided_by>, such as topos/progressive/learned,
    topos/progressive/score or topos/confirm/always_allow, in place of
    topos/confirm or topos/progressive. The service can tell a call its
    suggestion decided from one a rule or the risk score decided, and the
    source matches the one a replay of the session's log names. A decision
    without a layer keeps topos/<mode>. A consumer that matches the
    whole source string, or reports reliability by one source, must accept
    the longer form. Reliability over the verdicts applied is the same.

Fixed

  • The documents say what each TOPOS_DECISIONS_MODE does when the
    decision service fails.
    Only decide makes the call wait for a
    person, recorded as fallback. In learned the rules and the risk
    score decide with no random review, and in shadow the rules decide.
    topos run does not read the mode and always decides as decide. The
    behavior did not change.

v0.67.0

Choose a tag to compare

@github-actions github-actions released this 01 Nov 21:09

Added

  • TOPOS_CELLA_INSECURE, the explicit consent for TOPOS_CELLA_URL to
    be http:// on a host other than loopback, for a control plane
    reached over a network you trust; bumps latere.ai/x/cella to
    v0.22.6, whose client refuses such a URL without it.

v0.66.0

Choose a tag to compare

@github-actions github-actions released this 01 Nov 20:46

Added

  • TOPOS_DECISIONS_MODE: shadow, learned or decide. In learned,
    the decision service decides a progressive call only where it has
    evidence about the person: its allow, its block, and an ask on
    answers that disagree. Where it has too few answers, or does not
    answer, the rules and the risk score decide as without a service, and
    automatic verdicts are still picked for review at the service's audit
    rate. decide is the behavior of v0.63 to v0.65 without shadow.
  • A person's answer to a network approval goes to the decision service
    as an answer to the call whose connection was refused, after the
    call's decision, the same as a confirmation of the call. Each approval
    is one answer. An allow that adds the host to the session's network
    answers this call only. A fetch outside the network already sent its
    confirmation as the fetch's answer.

Deprecated

  • TOPOS_DECISIONS_SHADOW=true is read as TOPOS_DECISIONS_MODE=shadow
    for this release, and refused beside TOPOS_DECISIONS_MODE.

v0.65.0

Choose a tag to compare

@github-actions github-actions released this 01 Nov 18:40

Added

  • agent.tool_use records which layer decided the call, decided_by:
    network, always_confirm, tool, plan, read_only,
    always_allow, remembered, sandbox, score, confirm, memory,
    question, learned or fallback; and the rule within it,
    decided_by_rule: the pattern that matched, the tool that held the
    call, the score's band, or the decision service's model (spec 012). A
    client can tell a rule from a learned decision without reading the
    reason.

Changed

  • A rollout's run ends when its machine is unavailable. In a session
    created with rollout, a tool call whose machine cannot be opened with
    machine_unavailable, such as a sandbox Cella refuses because its owner
    runs as many sandboxes as their limit allows, is answered and recorded
    as before; once the step's other calls are answered, the session ends
    with stop_reason failed and detail machine_unavailable, and the
    model is not asked again. No person attends a run to resume it, and its
    caller counts it failed for the machine whatever the agent does next,
    so the caller can run it again sooner and nothing is spent on an agent
    working around the missing machine. A subagent of a run that meets it
    ends the run the same way. A session of no rollout keeps the failure as
    the call's result, and its agent goes on.

Fixed

  • A session's end deletes the sandbox a failed machine open left. When
    Cella created a session's sandbox and the runner then could not reach
    it, as when Cella's environment briefly drops its connections, the
    session opened no machine, and its end left the sandbox running until
    Cella stopped it at the environment's idle stop. Meanwhile it held a
    place in its owner's limit of running sandboxes, so the owner's next
    session was refused machine_unavailable with quota_exceeded. The
    end now deletes that sandbox and the Secrets applied for it, as it does
    an open machine's.

v0.64.1

Choose a tag to compare

@github-actions github-actions released this 01 Nov 17:48

Fixed

  • The release publishes its image. The v0.64.0 release built and signed
    the image but stopped at its attestation, which could not find the
    registry login, so v0.64.0 has no published image; use this release.