coding-agents-kit v1.1.0

coding-agents-kit v1.1.0 — interface 1.

git clone --branch v1.1.0 https://github.com/DailybotHQ/coding-agents-kit && ./coding-agents-kit/install.sh

A minor release. Interface stays 1; no command, flag, key or schema
changes.

Changed

• ak usage lists the measurable blocks first. The table shows the CLIs
  and providers whose quota ak can read (at least one account read, or
  whose read failed) before the blocks where every account is n/d or
  no login — Z.AI now sits above Cursor and Grok. Each part keeps the kit
  order; --json is not reordered.
• Version 1.1.0 in every version source (lib/common.py, the three
  skills' metadata, the install and skill commands in the README and docs,
  the schemas' $id, the issue template).
• Agent kit: the vendored DeepWorkPlan pack moves to 7.9.0, herdr-peers to
  1.1.0 and AI Diff Reviewer to 3.3.16 (pinned in skills-lock.json); the
  addon registry (.dwp/config.json) records herdr v1.1.0, ai-diff-reviewer
  v3.3.16 and agentkit v1.1.0.

Verify

SHA256SUMS lists every shipped file (verify from a checkout of the tag: shasum -a 256 -c SHA256SUMS) and the source tarball (verify it from the directory you downloaded it to).

coding-agents-kit v1.0.1

coding-agents-kit v1.0.1 — interface 1.

git clone --branch v1.0.1 https://github.com/DailybotHQ/coding-agents-kit && ./coding-agents-kit/install.sh

A fix release. Interface stays 1; no command, flag, key or schema changes.

Fixed

• Every profile is its own account, @default included. A CLI home
  variable that names one of ak's profiles — inherited from an
  ak <cli> @work session, or exported by a dev container so that a plain
  claude --resume restored by Herdr opens its default account
  (CLAUDE_CONFIG_DIR, CODEX_HOME, PI_CODING_AGENT_DIR, CLINE_DIR,
  GROK_HOME, the XDG_* directories of opencode, the relocated HOME of
  cursor and antigravity) — made @default that profile: ak usage folded the
  CLI's own account into the profile's row (a container showed no @default
  for Claude or Codex), and ak <cli> @default launched the profile instead of
  the CLI's own home. Now @default always reads and runs the CLI's own home:
  such a variable (and an inherited AGENTKIT_ACTIVE_PROFILE for that CLI) is
  dropped for @default in launches, ak profiles run, ak usage, ak pick,
  ak doctor and ak profiles. A bare ak <cli> follows the documented
  precedence (AGENTKIT_DEFAULT_PROFILE_<CLI>, else @default) instead of
  inheriting the outer profile. A home moved outside ak's profile tree is still
  @default's home. ak capacity --self keeps naming the running account from
  the variable.

Verify

SHA256SUMS lists every shipped file (verify from a checkout of the tag: shasum -a 256 -c SHA256SUMS) and the source tarball (verify it from the directory you downloaded it to).

coding-agents-kit v1.0.0

coding-agents-kit v1.0.0 — interface 1.

git clone --branch v1.0.0 https://github.com/DailybotHQ/coding-agents-kit && ./coding-agents-kit/install.sh

The first stable release. Interface stays 1; no command, flag, key or
schema changes from 0.7.1.

Stability commitment

From 1.0.0 on, the kit's public interface follows Semantic
Versioning: anything below changes
incompatibly only in a new major version, and additions arrive in minor
versions.

• The command surface: ak <kind> [@profile] for every kind in
  providers.toml (claude, codex, cursor, opencode, pi, cline, grok,
  antigravity and the glm, azure and xai routes), and the verbs ak run,
  ak env, ak doctor, ak usage (and ak status), ak pick,
  ak capacity, ak lease, ak profiles, ak alias, ak install,
  ak setup and ak --skill, with their documented flags (ak --help).
• The permission posture: autonomy by default, and an opt-out that always
  wins (--ask, AGENTKIT_PERMISSIONS=ask).
• Interface 1: the ak doctor --json shape, ak env and the ak run
  grammar and envelope, still reported as "interface": 1.
• The JSON schemas: doctor-v1, usage-v1, pick-v1, capacity-v1,
  leases-v1, profiles-v1, setup-probe-v1 and setup-verify-v1
  (docs/schema/); a schema gains keys in place and changes incompatibly
  only under a new schema name.
• The installed layout and the env file: install.sh / install.ps1,
  the profile directories and the env-file variable names (*_API_KEY and
  their _<SUFFIX> per-profile forms).

Changed

• Version 1.0.0. Every version source (lib/common.py, the three
  skills' metadata, the install and skill commands in the README and docs,
  the schemas' $id, the issue template) names 1.0.0, and CONTRIBUTING.md
  and docs/doctor.md describe the semver policy.
• The README showcases the kit: a pitch line, badges, a sample ak usage
  table, the eight supported coding agents with how each keeps accounts apart
  and what ak usage reads, and the provider routes (Z.AI GLM, Azure OpenAI,
  xAI, the Gemini API).
• Agent kit: the vendored DeepWorkPlan pack moves to 7.7.1 and the vendored
  herdr-peers skill to v1.0.0 (both pinned in skills-lock.json; herdr-peers
  checked against its release SHA256SUMS), and the addon registry
  (.dwp/config.json) records agentkit v1.0.0 and herdr v1.0.0.

Verify

SHA256SUMS lists every shipped file (verify from a checkout of the tag: shasum -a 256 -c SHA256SUMS) and the source tarball (verify it from the directory you downloaded it to).

coding-agents-kit v0.7.1

coding-agents-kit v0.7.1 — interface 1.

git clone --branch v0.7.1 https://github.com/DailybotHQ/coding-agents-kit && ./coding-agents-kit/install.sh

Interface stays 1. Antigravity's API-key accounts sit with its Google
logins, and the kit's own agent kit is current.

Added

• The project logo. assets/logo-light.png and assets/logo-dark.png
  (transparent, 1200×351); the README serves the one that matches GitHub's
  theme.
• ak status is another name for ak usage.
• A named profile's suffixed credential variable is its login
  (GEMINI_API_KEY_WORK for @work, any CLI's [clis.<cli>.login] env):
  ak profiles, ak doctor, ak usage and ak pick see such a profile as
  logged in (token-var).

Changed

• A Gemini API key is listed under Antigravity. GEMINI_API_KEY[_SUFFIX]
  rows sit in the antigravity block (n/d, GEMINI_API_KEY_WORK set) instead
  of a block of their own, and a profile served by its key has that one row,
  not a second Google-login row. A profile without a key keeps its own login
  row (quota on Linux and in containers).
• The Antigravity launch warning is per OS. ak antigravity @name without
  GEMINI_API_KEY_<SUFFIX> warns about the machine-wide Google login only on
  macOS and Windows; on Linux and in containers the profile has a login of its
  own and nothing is shared.
• Agent kit: the vendored herdr-peers skill moves to v0.3.2 (pinned in
  skills-lock.json), and the addon registry (.dwp/config.json) records
  agentkit v0.7.1 and herdr v0.3.2.

Verify

SHA256SUMS lists every shipped file (verify from a checkout of the tag: shasum -a 256 -c SHA256SUMS) and the source tarball (verify it from the directory you downloaded it to).

coding-agents-kit v0.7.0

coding-agents-kit v0.7.0 — interface 1.

git clone --branch v0.7.0 https://github.com/DailybotHQ/coding-agents-kit && ./coding-agents-kit/install.sh

Interface stays 1. Every account in ak usage, and Antigravity's quota:
the table lists each CLI's accounts whether or not their quota is readable,
and an Antigravity Google login shows the windows agy's own /usage panel
shows. --json and every schema are unchanged except for one additive
adapter id.

Added

• ak usage reads Antigravity. A new antigravity-quota source: with the
  profile's Google login file (antigravity-oauth-token in agy's home — Linux
  and containers), two POSTs to agy's own Code Assist host (identifying as the
  Antigravity client, as agy does) give the account's
  plan (the Google AI subscription — AI Pro, AI Ultra — or free) and its quota summary, the one agy's
  own /usage panel shows: a five-hour and a weekly window for the Gemini
  models and for the Claude and GPT models (5-hour Gemini 34% in 1h 17m). ak pick and ak capacity
  count such an account like any measured one. On macOS the login is a Keychain
  item in a format the kit does not parse: the row is n/d, logged in
  (keychain_opaque, presence only). The login file is also Antigravity's
  login probe now, so ak profiles and ak doctor see a container login.

Changed

• ak usage lists every account under its CLI. Rows with no readable quota
  no longer fold into a closing connected block or an n/d line: each sits
  under its CLI's title like a measured one, n/d with how it is connected and
  the few-word reason, or no login with the command that logs it in. The
  table thus also says which accounts of every CLI are connected. --json is
  unchanged.
• Antigravity's profile note and docs say where its login lives per OS: a file
  per profile on Linux and in containers (sign in inside the profile), one
  OS-keyring slot per machine on macOS and Windows (use GEMINI_API_KEY_<SUFFIX>).

Verify

SHA256SUMS lists every shipped file (verify from a checkout of the tag: shasum -a 256 -c SHA256SUMS) and the source tarball (verify it from the directory you downloaded it to).

coding-agents-kit v0.6.1

coding-agents-kit v0.6.1 — interface 1.

git clone --branch v0.6.1 https://github.com/DailybotHQ/coding-agents-kit && ./coding-agents-kit/install.sh

Interface stays 1. Patch: the four kit findings of the first live swarm
drill (a lead, lanes on three vendors, a capped handoff and a lead
succession, with no human keystroke).

Fixed

• ak capacity --self inside a Codex session. Codex runs its tool
  shells from an app-server daemon that keeps the environment of whoever
  started it, so a Codex lane read "unknown account" (exit 3) and a capped
  lane could never hand off. An interactive ak codex that reuses a daemon
  running here now passes the account marker for the session
  (-c shell_environment_policy.set.AGENTKIT_ACTIVE_ACCOUNT=…, data:
  providers.toml [clis.codex.daemon] marker), and with no marker
  --self takes the account from a CLI home variable that names a profile
  directory inside ak's own tree (CODEX_HOME=<profiles>/codex/work1).
  The default home, a folder outside the tree, or two candidates still exit
  3 — never a guess.
• ak pick --owner X counted X's own leases as zero, so a lead that
  leased each lane's account under its own address got an account it had
  already handed out. Every active lease now counts, the owner's own
  included; a Codex account is excluded for its own holder too; the new
  --reuse @profile (repeatable, needs --owner) hands the owner's own
  lease on (e.g. to a lane's successor).
• Unknown-capacity kinds and one account per profile. ak capacity grok @default was ambiguous (the grok login and an xAI key) while ak lease grok @default accepted it. ak capacity, ak lease and ak pick now
  resolve a kind + @profile to the same account: the named CLI's or
  provider's own row, else, for a kind served by a provider key, the
  provider's (claude-glm @work is zai @work); still ambiguous → exit 2
  naming the exact commands. ak pick offers each profile once. Every
  pick-v1 candidate gains verdict (ak capacity's rule; unknown for
  an account chosen with --allow-unknown), the document gains reuse
  (additive), and a refusal of only no-quota accounts names
  --allow-unknown.
• Grok folder trust. ak grok … --trust-cwd wrote nothing, yet Grok
  stops at "Do you trust the contents of this directory?". It now appends
  [folders."<root>"] trusted = true to Grok's trusted_folders.toml
  (format grok-toml), where <root> is the folder Grok asks about: the
  repository's main working tree — also from a linked worktree — or the
  launch folder outside a repository. An existing answer is left alone.
• Docs and skills: docs/usage.md, docs/profiles.md (Codex and its
  app-server daemon), docs/permissions.md, docs/orchestration.md,
  docs/SECURITY.md, and the agentkit and agentkit-orchestrate skills
  describe the above; the unattended reference says never to answer Grok's
  repository-level trust screen.

Verify

SHA256SUMS lists every shipped file (verify from a checkout of the tag: shasum -a 256 -c SHA256SUMS) and the source tarball (verify it from the directory you downloaded it to).

coding-agents-kit v0.6.0

coding-agents-kit v0.6.0 — interface 1.

git clone --branch v0.6.0 https://github.com/DailybotHQ/coding-agents-kit && ./coding-agents-kit/install.sh

Interface stays 1. Capacity-aware agents: an agent can ask for its own
room at every task boundary, cheaply, and leads lease the accounts they hand
out. Every new surface is additive.

Added

• ak capacity [<kind>] [@profile] [--self] [--low PCT] [--critical PCT] [--max-age S] [--json] — one account's headroom and a verdict (ok,
  low, critical, unknown), computed by ak pick's own arithmetic so
  the two never disagree. Thresholds default to 25 / 10
  (AGENTKIT_CAPACITY_LOW, AGENTKIT_CAPACITY_CRITICAL). Exit 0 for every
  reading; --self exits 3 outside an ak launch (never a guess). Schema
  capacity-v1.
• AGENTKIT_ACTIVE_ACCOUNT=<kind>/@<profile> — set by every ak launch
  and ak run, @default included, for the CLI it starts (ak capacity --self reads it); a kind and a profile name only, never printed by
  ak env. AGENTKIT_ACTIVE_PROFILE is unchanged.
• A usage cache under the kit's state directory
  ($XDG_STATE_HOME/agentkit/usage-cache/, AGENTKIT_STATE_DIR): usage
  numbers only, 0600 files, atomic writes. ak capacity and ak pick
  reuse a reading younger than --max-age (300 s; 0 reads live) and write
  back what they read live; ak usage is the only command that always reads
  live, and it refreshes the cache.
• AGENTKIT_CAPACITY_CAP=[<kind-or-cli>]@profile=PCT[,…] — a
  lower-only drill cap (min(real, cap), "capped": true) applied by
  ak capacity and ak pick (where a capped account below a --need
  percent no longer qualifies); a kind names the account its quota lives on;
  an invalid value or an unknown name exits 2.
• ak lease <kind> @profile --owner ADDR [--ttl DUR] [--purpose TEXT],
  ak lease release …, ak lease ls [--json] — advisory, expiring
  account leases (schema leases-v1), changed under a portable lock and
  written atomically (0600). Codex takes one lease (lease = "exclusive"
  in providers.toml: one writer per auth.json); other accounts take many;
  only the owner releases.
• ak pick --owner ADDR skips Codex accounts leased to another owner and
  ranks by headroom / (1 + other leases); --max-age S. pick-v1
  gains owner and, per candidate, leases and capped (additive). Without
  --owner the ranking is unchanged.
• Skills: agentkit teaches ak capacity and ak lease;
  agentkit-orchestrate gains Capacity-aware lanes (check at task
  boundaries with ak capacity --self, leases, proactive handoff) and states
  the account pool rule exactly: work moves only among accounts the developer
  declared for the work, within each vendor's terms; agents never create
  accounts, renew logins or spend a Codex reset.

Changed

• ak usage, ak pick and ak capacity write the kit's usage cache (and
  nothing else); they still never write under a profile or the env file,
  refresh a login or spend a reset. ak pick reuses readings up to 300 s old
  by default (--max-age 0 reads live).
• ak profiles run sets AGENTKIT_ACTIVE_ACCOUNT for its command too, so an
  inherited marker never names the outer account.

Verify

SHA256SUMS lists every shipped file (verify from a checkout of the tag: shasum -a 256 -c SHA256SUMS) and the source tarball (verify it from the directory you downloaded it to).

coding-agents-kit v0.5.3

coding-agents-kit v0.5.3 — interface 1.

git clone --branch v0.5.3 https://github.com/DailybotHQ/coding-agents-kit && ./coding-agents-kit/install.sh

Interface stays 1. Patch: ak codex starts in a container whose Codex
home is shared with another machine.

Fixed

• Codex's app-server daemon in a shared home. A Codex home shared with
  another machine (a host profile, or one volume shared by several
  containers) records a daemon installed by that machine, and Codex refused
  to start (daemon executable not found). An interactive ak codex now
  adds --no-daemon when the home records a daemon that is not on this
  machine or not built for its OS, and never when the daemon is present.
  AGENTKIT_CODEX_NO_DAEMON=1 forces it. Declared as data
  ([clis.codex.daemon] in providers.toml).

Added

• ak doctor reports each account's daemon state (daemons: present,
  absent, missing or off; additive in doctor-v1), and the text form
  says when ak codex adds --no-daemon.

Verify

SHA256SUMS lists every shipped file (verify from a checkout of the tag: shasum -a 256 -c SHA256SUMS) and the source tarball (verify it from the directory you downloaded it to).

coding-agents-kit v0.5.2

coding-agents-kit v0.5.2 — interface 1.

git clone --branch v0.5.2 https://github.com/DailybotHQ/coding-agents-kit && ./coding-agents-kit/install.sh

Interface stays 1. A default profile per CLI, so a bare ak claude works
in a container whose host keeps Claude's login in the macOS Keychain.

Added

• AGENTKIT_DEFAULT_PROFILE_<CLI> (environment or env file): the account
  a bare ak <cli>, ak run <cli> and ak env <cli> use. A positional
  @profile, AGENTKIT_PROFILE and an explicit @default (the CLI's own
  home) win. The profile must exist (a default never creates one); a
  provider kind (claude-glm) keeps the CLI's own home.
• pick as the value (opt-in, off by default): the account with the most
  headroom by ak pick's policy among those whose login is portable (a file
  or a token variable, never a Keychain item); @default when none has room.
• ak usage, ak pick and ak profiles --json mark the default account
  ("default": true, additive in usage-v1, pick-v1, profiles-v1);
  ak doctor lists it (default_profiles, additive in doctor-v1) and
  names a default that does not exist.
• ak doctor on Linux or in a container names each account whose file
  names the account but whose login token is not there (a macOS Keychain
  login does not travel), with the fix.

Verify

SHA256SUMS lists every shipped file (verify from a checkout of the tag: shasum -a 256 -c SHA256SUMS) and the source tarball (verify it from the directory you downloaded it to).

coding-agents-kit v0.5.1

coding-agents-kit v0.5.1 — interface 1.

git clone --branch v0.5.1 https://github.com/DailybotHQ/coding-agents-kit && ./coding-agents-kit/install.sh

Interface stays 1. Patch: a Cursor login on Linux is recognised, and
ak profiles --json reports where Claude's token really is.

Fixed

• Cursor login on Linux: the default account keeps its login in
  ~/.config/cursor/auth.json (not ~/.cursor/auth.json), so ak usage and
  ak doctor reported n/d / login: unknown for a logged-in Cursor in a
  container or on a Linux host. The login probe now also reads the xdg root
  (~/.config/cursor); profiles are unchanged (<profile>/home/.cursor): a
  profile's HOME links the real ~/.config in, so it never borrows the
  default account's login.
• Claude login kind (ak profiles --json, profiles-v1): an account with
  .claude.json (oauthAccount) was reported as a file login although that
  file only names the account; the token is .credentials.json or, on macOS,
  a Keychain item. The login is now file only with .credentials.json,
  keychain when the Claude Code-credentials item exists (a profile's own
  -<sha256 prefix> item for a profile), none when neither exists, and
  unknown when only the account file is there and the Keychain cannot be
  asked (AGENTKIT_KEYCHAIN=off). Presence only: the secret is never read.
  @default copied into a container without its token now reads none.
  The doctor's logged_in is unchanged.
• The bundled skills' versions and pinned install lines follow the release.

Verify

SHA256SUMS lists every shipped file (verify from a checkout of the tag: shasum -a 256 -c SHA256SUMS) and the source tarball (verify it from the directory you downloaded it to).