AgentsServer v1.0.7-beta.21

AgentsServer 1.0.7-beta.21

This beta packages the recent server fixes for Codex endpoint switching,
startup queue recovery, and inter-chat messages.

• Apply a saved normal/custom Codex selection when the temporary runtime work
  delaying it finishes. Preserve the existing conversation and goal, and release
  the old native writer before another Codex process resumes that conversation.
• Recover chat queues independently at startup. Opening one chat no longer waits
  for every other transcript to be scanned. Persist queue checkpoints so later
  restarts read only new events, while retaining message order and Stop pauses.
• Fix shared chats showing “Shared conversation temporarily unavailable” after
  successful token entry. Keep shared-chat reads and reconnects working when
  the server adds queue-recovery metadata.
• Use the asynchronous mailbox for same-server inter-chat delivery, including
  older paired Send and Ask callers. Disable legacy request/reply execution and
  automatic final-reply turns. Keep existing conversations and mailbox access.
• Hide duplicate internal status messages only when stored provider receipts
  prove their origin; preserve genuine user messages with identical text.
• Include the intervening goal-continuation, provider-context, attachment,
  reasoning-stream and subagent fixes from the local beta builds.

This is a server-only beta; the existing desktop beta can use these fixes
without a new app build. The server updater installs it when the agent worker
is idle. Forcing installation restarts that worker and interrupts its active
agent turns; it does not migrate running agents between worker versions.

Existing installation locations, credentials, release signing, and update
channels are retained. This GitHub server release does not by itself publish
an npm package.

AgentsServer v1.0.7-beta.11

Side conversations now persist on the connected server and synchronize across desktop clients. Answers survive app closure; follow-up questions retain their provider context; Stop and Clear apply across connected clients. Side conversations remain separate from the main transcript.

The paired desktop app can show provider-reported allowance, reset times, and credits when available. Missing usage remains unknown, and custom API endpoints do not display another account’s allowance. Usage reads do not start model requests.

This server update supports the paired desktop update’s shared Codex and Claude goal controls and usage display. It also respects Claude’s configured data directory for native session history and goals. Install both the paired app and this server update to use synchronized side conversations and the usage indicator.

Validated against 5,163 server test cases across eight successful release shards (six skipped), plus native provider and signed desktop-package acceptance. All 109 packaged runtime files and the release signature were independently verified against committed source.

Canonical source: 9b04f852c5c6e698edbf47f9e64d9eb9b65a81be
Standalone export: 278f88d1d4110b23b1cab3d30013116b7021214d

AgentsServer v1.0.7-beta.9

AgentsServer 1.0.7-beta.9

After a Codex CLI upgrade, Recheck CLI makes the installed version available
to new chats. Running chats retain their original process until their work
finishes; idle chats resume their existing native history on the updated CLI.
This avoids restarting the whole server just to pick up a provider upgrade.

Server updates also accept existing user-owned Python installations created
with group-write permissions. Preparation and activation preserve those
permissions instead of requiring manual changes to a shared Python runtime.

Validation includes concurrent real GPT-6 Sol requests through the desktop
app with ChatGPT authentication, an uninterrupted older turn, and a contextual
follow-up preserving its native thread ID. A controlled launcher-version change
exercises process handoff around the installed CLI. Focused tests also cover
late callbacks, approvals, goals, shutdown and existing Python permissions.

API contract 28, dependencies, the release signing key and Team Hub storage
schema are unchanged. Installing this server correction still requires the
agent-owning worker to restart after it becomes idle. Subsequent Codex CLI
upgrades use the new process handoff.

This is a server beta using the existing signed update path. It does not
publish a desktop app, change npm tags, or migrate the installation to npm.

AgentsServer v1.0.7-beta.10

AgentsServer 1.0.7-beta.10

Side chats can finish long answers without an AgentsDock-imposed answer
deadline. Remove the shared 150-second cutoff and Claude's separate native
control cutoff. Codex side chats use the same startup and request settings as
ordinary Codex chats.

Stop, Clear, disconnection and server shutdown still cancel their owned side
work. A long answer no longer loses its native conversation just because time
has passed. Follow-up context and the main conversation remain separate.

The desktop correction also removes its former 210-second request cutoff;
both the corrected app and server are needed to remove both limits.

API contract 28, release signing and existing installation methods are
unchanged. Install through the normal managed updater when current work is
idle.

AgentsServer v1.0.7-beta.8

AgentsServer 1.0.7-beta.8

Codex Side chat can inspect the parent workspace and use ordinary tools under
the parent's existing permissions. This removes AgentsDock's blanket tool and
file restriction while retaining a separate native conversation. Follow-up
questions keep their side context; requests to change files must be explicit.
Side approvals use the existing interaction controls, and closing Side chat
cleans up its own work without stopping the parent conversation.

Interrupted Claude mailbox checks retain proof that their generated input is
internal, preventing that input from appearing as a user-authored message.

Validation includes real Codex file inspection, a follow-up, an explicitly
requested local write, parent-conversation preservation, and native desktop
interaction through the production transport. Focused adapter, approval and
history-repair checks pass. The signed candidate is also gated by the server
release suite.

API contract 28, dependencies, the release signing key and Team Hub storage
schema are unchanged from 1.0.7-beta.2. Install through the managed updater with
Install when idle to preserve active work. This release changes the worker
that owns agents and therefore still requires a restart after it becomes idle.

This is a server beta using the existing signed update path. It does not
publish a desktop app, change npm tags, or migrate the installation to npm.

AgentsServer 1.0.3

AgentsServer 1.0.3

Stable update from 1.0.2. Team Network remains a beta feature.

Workspace Changes

• Support the desktop's new Changes tab with on-demand repository-wide
  status, staged and unstaged diffs, whole-file staging and unstaging, and
  commits of the reviewed staged set.
• Review base, current and incoming text conflicts; save and stage a resolution;
  continue an existing merge, rebase, cherry-pick or revert. Abort requires an
  explicit confirmation. A further conflict remains visible rather than being
  reported as a completed operation.
• Restrict these endpoints to authenticated native operators. Shared-chat
  guests do not gain repository access. Check repository revisions and Git's
  index lock before mutations to reject stale reviews and concurrent changes.
• Preserve recoverable state on storage failures and report recovery guidance
  if an operation changed references before its index could be published.

This first cut requires AgentsDock 1.0.3. It does not add branch creation,
push, PR/MR management, or background repository polling. Binary conflicts and
operations requiring executable Git hooks or custom filters need the terminal;
the server does not silently bypass those hooks or filters.

Codex Side chat startup

• Stop creating a fresh Codex runtime database for every side question, which
  could trigger provider-history re-indexing and time out before answering.
  Use the configured provider runtime and sign-in without copying credentials.
• Keep each side question in its own temporary thread and owned process, with
  workspace access and tools disabled. Cancellation closes that side process;
  it does not stop, steer or resume the main conversation.

Compatibility and updating

• API contract remains 28; no Team Hub schema, dependency or signing-key
  change from 1.0.2. Existing clients retain their current behavior.
• Install through the existing Stable server updater. Publishing a release
  does not restart or automatically replace any running server.

AgentsServer 1.0.2

AgentsServer 1.0.2

Stable update from 1.0.0, including the changes validated in
1.0.1-beta.1 and 1.0.1-beta.2, plus secure Team Network endpoint recovery.
Team Network remains a beta feature within this stable server release.

Recover Team Network after an address change

• Report when the host's configured IPv4 address is no longer assigned to
  its machine. An authenticated operator can select a current local address
  without restarting the main server, replacing its CA or revoking members.
• Let an approved member update its saved host endpoint without rejoining.
  The candidate must pass TLS verification with the existing pinned CA and
  client certificate and identify the same host, Hub, peer and team before
  the endpoint is saved.
• Preserve approved credentials, routes and active/inactive selection. Failed
  probes and concurrent trust, renewal or endpoint changes cannot silently
  replace the saved endpoint or reconnect a deactivated member.
• Retain the prior host configuration after a failed change and restore a
  previously live listener when possible. Preserve notification callbacks
  through reconfiguration and rollback.

Recovery is an explicit operator action; no address discovery, automatic
network switching or inbox polling is added. Updating the host does not change
addresses already saved by members. Members need this release's endpoint
control to migrate their own saved connection. See
endpoint recovery.

More reliable Team Network collaboration

• Fix valid @@ mail from an approved joined server being rejected as
  unavailable by the receiving host's gateway. Retain exact recipient identity,
  revocation and idempotent retry checks. Previously rejected mail is not
  automatically resent; the sender can submit it again after the host updates.
• Keep new join requests pending until approved, rejected or cancelled when
  both host and joining server support durable approval. Waiting survives
  restarts and lost responses without granting access automatically. Remove
  the 16-pending-request limit shared by teammates behind one source IP while
  retaining overall resource and flood bounds.
• Add indexed, permission-scoped Mail and Bulletin search with explicit
  queries and pagination.
• Let agents use native Team Network tools to read the exact recipient or
  Bulletin selected with @@, including sender-filtered history pages. Reading
  does not grant permission to send or post.
• Clarify sender formatting guidance so ordinary text and technical values
  keep their whitespace. Existing message bodies are not rewritten.

Already expired joins need a fresh request; rejected or cancelled requests are
not revived. Legacy peers retain their original deadlines. Durable pending
joins are not supported by older server binaries.

Independent Side chat

• Answer temporary side questions and follow-ups for Codex and Claude using
  recent visible conversation text and the side conversation's own history.
  Side chat does not send, steer, stop or queue a main turn, pause its goal, or
  add messages to the main chat's history.
• Give each question separate provider execution and cancellation, with
  bounded context and authenticated requests. Exclude hidden reasoning,
  attachments and tool results from its context; isolate inherited runtime
  instructions and workspace access. Unsupported provider isolation fails
  explicitly.
• Include Side chat cleanup in the cooperative shutdown budget and align the
  installer's launchd wait with that complete budget.

Side chat history is temporary, and each follow-up uses a fresh isolated
provider invocation. Side chat and indexed search need a supporting desktop
build. Provider tools must be installed and authenticated for the service user.

Compatibility and updating

• API contract remains 28. Team Hub schema advances from 22 in 1.0.0
  to 23 for indexed message search, as already shipped in 1.0.1-beta.2.
  Back up before upgrading; a schema-crossing downgrade requires a compatible
  backup rather than simply replacing the runtime.
• No dependency or release signing-key change from the preceding stable and
  beta releases. Older clients retain their negotiated behavior; new controls
  require the corresponding advertised server capability.
• Install through the existing server updater on the Stable channel. Both
  1.0.0 and 1.0.1-beta installations can upgrade to 1.0.2. Publishing the
  package alone does not install it or restart a running server.

AgentsServer v1.0.1-beta.2

AgentsServer 1.0.1-beta.2

Changes since 1.0.1-beta.1.

Independent Side chat

• Support temporary side questions and follow-up conversations for Codex and
  Claude. The desktop's Side chat uses a bounded snapshot of recent visible
  messages, plus its own separate question-and-answer history.
• Side questions do not send, steer, stop or queue a main chat turn, pause its
  goal, or write messages into its history. Each question owns its provider
  process and cancellation; hiding the desktop panel does not cancel it.
• Isolate provider tools, workspace access and inherited runtime instructions.
  Context excludes hidden reasoning, tool results and attachments. Missing
  provider isolation support fails explicitly instead of using the main agent.
• Authenticate each request, validate and bound its payload, distinguish
  changed-content retries, and cancel only the owned question on disconnect.
  No inbox polling or background UI subscription is introduced.

Team Network

• Add indexed, permission-scoped Mail and Bulletin search, with explicit
  queries and pagination rather than per-keystroke requests or polling.
• Let agents read messages from the exact recipient selected with @@ through
  the native Team Network tools. Keep durable route checks and recipient scope.
• Clarify sender formatting guidance so ordinary text, words and technical
  values keep their whitespace. Existing message bodies are not rewritten.

Compatibility and availability

• Side chat and indexed search require a matching desktop build. Older clients
  keep their existing behavior; newer clients explain when a server lacks the
  necessary capability. Follow-up history is an additive capability.
• Search adds the indexed-search database migration. The side-question service
  has no persistent conversation database or transcript migration.
• Install this beta through the existing server updater on the Beta channel.
  Publishing the package does not install it or restart a running server.
• Desktop 1.0.1 local build 1170 includes the matching Side chat interface;
  installing this server alone does not add that interface to older apps.
• Uncommitted cron-history and subagent-display work is excluded from this
  package. The existing stable release is unchanged.

AgentsServer v1.0.1-beta.1

AgentsServer 1.0.1-beta.1

Fix Team Mail from joined servers

Fix valid @@ mail sends from a joined server failing with “Team Network mail
is unavailable.” The receiving host's secure-peer gateway rejected the
recipient inbox-identity field used by durable chat-scoped mail routes before
the message could be stored. This affected approved members too; rejoining or
changing their permissions was not a solution.

The gateway now preserves that field for the existing transactional checks.
Revoked or replaced recipients, malformed identities and unknown fields remain
rejected. Stable-key retries still return the original mail receipt rather
than creating duplicate messages.

Updating

• Update the receiving Team Network host to this beta to apply this fix.
  No desktop update or member re-enrollment is required for this correction.
• Previously rejected mail was not delivered and is not resent automatically.
  After the host updates, the sender can submit it again.
• No API-version, database-schema, dependency or signing-key change. No new
  polling or background inbox refresh has been added.
• Join approvals remain separate: the reusable server invite link still
  requires the host to approve each joining server's request.

Team joins no longer expire after ten minutes

• New join requests stay pending until approved, rejected or cancelled when
  both host and joining server run this revised beta. Waiting survives
  restarts and recovery from a lost response; it does not grant extra access
  or approve a request automatically.
• Remove the limit of 16 pending requests per source IP, so teammates sharing
  one network do not block each other. Overall resource and flood bounds,
  signature and identity validation, cancellation and revocation remain.
• A long-held connection reaching its observation limit no longer expires
  the underlying join. No five-second inbox polling is added.
• Already expired requests need a fresh join after both servers are updated;
  rejected and cancelled requests are not revived. Legacy peers retain their
  original deadlines. Downgrading to an older server does not preserve pending
  non-expiring joins.
• Desktop support for continuously observing long waits and displaying old
  expired requests is committed separately, not distributed in this server
  archive.

This is an explicitly authorized same-version replacement of
1.0.1-beta.1. If that version is already installed, manually reinstall from
the revised, signature-verified server archive using the existing service
user and configuration. Check for updates and Force update cannot install
this same-version replacement. The installer retains the previous runtime
for rollback. Publication itself does not restart any server.

Validation and scope

Focused regression checks cover a freshly approved member's exact @@
resolution, durable grant admission and first send to another member through
private-socketpair mTLS, threaded replies, idempotent retries and recipient
revocation/rejoin during a send. These use isolated data, not live user mail.
Join checks cover approval after eight days, restart, lost-response recovery,
shared-IP admission, cancellation/approval races, observer cleanup and legacy
compatibility.

This is a narrowly scoped beta after 1.0.0. Other in-progress desktop,
cron-history and subagent-display changes are not included. The stable release
channel remains on 1.0.0.

AgentsServer v1.0.0

AgentsServer 1.0.0

What this release includes

This is the stable upgrade from AgentsServer 0.1.25, the previous published
stable release. It brings together the subsequent 0.1.26 and 1.0 beta work:
durable chat-to-chat messaging, expanded Team Network collaboration, browser
chat sharing, native goal steering, more accurate history, and safer recovery
and updates. Existing capabilities such as Team Hub hosting, secure pairing,
scheduled jobs, provider history import and Codex goals have been extended and
hardened; they are not all new features of this release.

Already on 1.0.0-beta.8? This stable replacement additionally repairs
source-proven cross-chat delivery wrappers imported as user messages, and keeps
ordinary Codex parents supervised while their subagents finish. History repair
uses the saved delivery receipt and exact native provider-turn identity,
preserving the original agent message and genuine user input. There is no additional API,
dependency, signing-key or storage-schema change from beta.8.

Replacing the original 1.0.0: the version number is intentionally unchanged.
Already-installed 1.0.0 servers will not discover this as a newer version;
explicitly reinstall the verified replacement package to receive this repair.
Installing only the desktop replacement does not apply a server history fix.

• Previous stable release: 0.1.25
• Full implementation comparison through beta.8
• Changes included in beta.8

Chat-to-chat messaging that survives reconnects

• Explicit, accepted structured @Chat references can establish an exact
  bidirectional permission pair. Later authorized runs can discover and use
  that pair without another mention. Permissions do not spread to other chats,
  the recipient's other routes, or forks.
• Negotiated asynchronous pair messages use a durable per-chat mailbox. Send
  returns a message identity after acceptance; a reply is a separate explicit
  message, not an automatically forwarded final answer or an obligation to reply.
• Agents can discover unread senders and read ordered, paged batches with exact
  message IDs, original timestamps and reply relationships. Stable read keys
  survive provider/server reconnects. Exact retries return the saved receipt;
  they do not create another message or consume a different batch.
• Busy recipients are not interrupted or steered by mailbox arrivals. Bounded,
  body-free availability hints use existing provider checkpoints. An eligible
  idle recipient can wake once for a new unread batch; queued user work, Stop,
  deletion and current permissions remain authoritative.
• Revocation, cancellation and current route revisions are rechecked through
  final admission and read retries. Already-delivered mail remains readable
  after its sender is archived, without making that sender available for new
  sends or automatic work.
• Remove arbitrary stored-route and hourly-message quotas for configured
  asynchronous pair messaging. Discovery and reads are paginated; message-size
  limits, explicit permission checks and legacy exchange limits remain.
• Fix provider-tool message bodies supplied through stdin, including replies;
  preserve exact acceptance/cancellation receipts rather than guessing that a
  failed or disconnected request should be submitted again.

Legacy exchange modes retain their negotiated behavior. “Accepted,” “read by
agent” and “replied” are distinct states. Opening a message in the desktop is
not an agent read receipt. See the mailbox contract and
paired-route semantics.

Expanded Team Network collaboration — still beta

• Add server-addressed Team Mail and separate it from shared Bulletin content.
  Mail supports optional subjects, exact-parent threads, scoped replies,
  attachments, recipient dismissal and versioned read/unread attention state.
  Marking mail unread does not erase its historical delivery/read receipts.
• Add durable, revocable chat-scoped mail grants tied to the exact recipient
  server identity. Read access, message text and imported metadata do not grant
  permission to send. Agent replies require the appropriate existing route.
• Add author-versioned Bulletin edits and supported deletion/moderation flows,
  preserving revision and authorization history. Editing a post does not create
  a replacement mail item or silently change its recipients or attachments.
• Deliver negotiated, coalesced Mail/Bulletin availability hints through the
  existing stream. These do not poll message bodies or automatically dispatch
  a remote agent.
• Expand authenticated Host controls, invitation/operator management and
  server-bound Teamspace access. Opt-in secure-peer Join requests can complete
  after approval while preserving the original consent, deadline and identity;
  cancellation, expiry and a later connection choice prevent stale activation.
• Harden secure-peer connection recovery, certificate rotation, attachment
  streaming and reclamation, and snapshot/restore continuity. Host maintenance
  drains admitted writes, and verified current-schema reads avoid unnecessary
  migration writer locks.

Team Network remains a beta feature inside this stable server release.
Cross-server Team Mail goes to a server inbox; it is not a request to start
or steer a remote chat. Same-server chat-mailbox wake behavior is separate.

Share one chat in a browser

• View only creates an explicitly requested, immutable, paged snapshot of
  the readable conversation. Large histories are streamed into bounded pages
  rather than silently truncated to a small transcript prefix.
• Interactive shares trusted control of one live chat, including its
  supported queue, goal, approval, settings and scheduled-job actions. It uses
  the packaged AgentsDock chat renderer and preserves native event identities
  and chronology across paging and reconnects.
• Normal links are token-free; recipients enter a separately supplied reusable
  access token. View-only snapshots also support an optional token-in-link URL.
  Expiry/revocation remain effective across browser sessions and reconnects.
• Share creation can return a different reachable HTTP/HTTPS origin for the
  same server, such as its LAN address, without changing the authenticated
  management connection. Interactive shares retain their exact origin binding;
  create a new share to use another address.
• Both modes can play and seek registered videos actually attached to sent
  messages or published in the shared chat. Media uses scoped authorization and
  byte-range responses; unused uploads and arbitrary workspace paths are not
  exposed. Codec support still depends on the browser.
• Durable request receipts prevent reconnects or uncertain submissions from
  automatically repeating prompts or controls. Shared APIs do not expose native
  administration, tmux or general filesystem browsing/downloads.

Interactive sharing is trusted collaboration, not a provider sandbox: a
guest can ask the existing agent to use its normal tools and may create work
that outlives the share. Revocation cannot undo accepted work, remove scheduled
jobs already created, or retract text/video bytes a recipient saved. Sharing
does not configure ingress or make a private address reachable. HTTP is
unencrypted; use HTTPS on untrusted networks. See
View only and Interactive.

Native goals, steering and subagents

• Keep an ordinary Codex run owned when its native parent turn ends before its
  children. Once the currently owned children finish, collect their native
  notifications using an empty-input continuation on the same thread. No goal,
  synthetic user prompt, repeated reminder or polling loop is required.
• Preserve that parent's runtime authority, chronological answers and controls
  through collection. A spontaneous native continuation wins over a queued
  continuation request; Stop, stale owners and uncertain delivery cannot
  silently replay the original prompt or submit a duplicate continuation.
• Preserve a Codex goal's local owner across the ordinary first turn that
  creates it and later native continuation turns. An intermediate final answer
  no longer prematurely ends the surrounding goal operation.
• Send now can steer compatible text and attachments into that same native
  goal without pausing it, replacing its run authority or starting a substitute
  user turn. Between continuation turns, one accepted follow-up waits on the
  existing stream for the next ready turn.
• Fix plain follow-ups rejected solely because the client automatically
  attached saved route metadata. The goal lane leaves those snapshots unused
  and retains its existing authority. Explicit new references, provider commands,
  changed runtime settings and stale-owner requests remain fenced.
• Recheck exact goal/run/turn ownership, process generation, budgets and
  Pause/Stop immediately before delivery. Uncertain sends are not automatically
  replayed, and accepted follow-ups produce one chronological user boundary.
• Keep public commentary, final answers, retry notices and compaction/runtime
  activity distinct. Reconnecting progress is not automatically a terminal
  failure, and later goal progress remains below the appropriate answer/input.
• Preserve native Codex child-thread titles separately from nicknames and
  paths, including live renames and explicit title clears. Recover stale names
  for known completed ch...