v1.11.0

MyACE v1.11.0

A release focused on growing the starter-pack library, surfacing compile-time validation earlier, and polishing the frontend. Three new starter collections, four new starter skills, a name-collision preview in the profile composer, and a batch of UI fixes.

Highlights

Three new starter collections

• EU AI Act compliance — agents, skills, and rules for building and documenting AI features in line with the EU AI Act.
• DevOps Engineer — a base collection covering CI/CD, infrastructure, and release engineering workflows.
• Database & QA — database-focused and QA-focused collections, with handoff_to chains wired into the orchestration feature.

Four new starter skills

• API discoverability — bake a machine-readable API description into new services and discover existing ones.
• PR standards — pull-request creation, review depth, and merge-strategy gates.
• Release engineering — semver, changelogs, and release/hotfix process.
• Governance — data classification, dependency compliance, and audit-trail rules for enterprise work.

Compile-time validation preview

• Pre-compile name-collision preview — the profile composer now detects artifact-name collisions across collections before you compile, showing which collection wins, instead of discovering a silently-overridden artifact in the compiled output.

Completed handoff_to metadata

• The starter collections' agent files now carry structured handoff_to frontmatter consistent with their prose "## Handoff" sections, and the earlier name collisions between base/ and additional/ collections were fixed.

Frontend UI fixes

• Description widths — the Landing hero, Dashboard, and hub-page descriptions now span the same width as the content rows below them on desktop.
• GitHub icon restored — the lucide-react brand-icon removal broke the frontend build and crashed Landing/Login at runtime; a local GithubIcon SVG component replaces it across the five affected pages.
• Mobile collection detail header — the header action buttons no longer overflow the screen; they wrap below the back-arrow + metadata line, and the header is split into title / metadata / description rows.

API documentation

• API.md — a machine-readable orientation layer for the HTTP API (base URL, auth, route groups, curl examples), complementing the canonical /openapi.json spec.

Docs

• API.md added; README.md audited and restructured.
• Marvin (marv-o-matic) credited as the automated PR review bot.

Security & dependencies

• nanoid bumped to 3.3.18 to clear GHSA-2v37-7h3g-55p8.
• react/@types/react and the frontend-deps group bumped.

Downloads

Standalone CLI binaries for Linux, macOS (Intel + Apple Silicon), and Windows are attached below — no Python required. See the README for install instructions.

---

Metadata: tag v1.11.0 · commit 34bd692 · released 2026-09-01 · minor bump (features + fixes since v1.10.0)

Latest build (34bd69296520194eaaf53bca5095c271f58d4898)

Auto-built from main branch commit 34bd692.

These binaries are built on every push to main and may be less
stable than tagged releases. For production use, prefer a
tagged release.

v1.10.0

A feature-packed release: four new vendor cloud starter collections, the full orchestration feature (handoff_to, recipe gallery, pipeline composition wizard, and the new Edit-pipeline flow), inline artifact editing, owner/moderator unpublish, and a dashboard/onboarding refresh.

Highlights

Four new vendor cloud starter collections

MyACE's starter-pack library grows with Azure, AWS, Google Cloud, and Scaleway Cloud Architect collections — each a base/additional pairing of agents, skills, and rules for working in that cloud's ecosystem, with handoff chains wired into the orchestration feature.

Orchestration

• handoff_to field on agent artifacts — a structured, machine-readable way to declare which specialist an agent routes work to next (alongside the existing prose "## Handoff" section).
• Orchestration Gallery (/build/orchestration) — discovers every agent with mode: primary + a non-empty handoff_to across your collections and the community, and renders its routing graph (including back-edges like a failed check routing back to the builder).
• Pipeline composition wizard (/build/orchestration/build) — pick a profile, build a linear sequence of its agents, preview the chain, and generate a new orchestrator agent.
• Edit pipeline — the gallery's recipe detail view now has an Edit button that opens the wizard prefilled with the current recipe's fields.
• Dark-mode fix — the flow diagram's primary node and zoom controls were white-on-white in dark mode; both are now theme-aware.

Inline artifact editing

Collection Detail now supports click-to-edit for an artifact's priority, version, target compatibility, and body (validate-on-blur, Escape to revert), plus an "Add rule" form.

Unpublish

Owners and moderators can now unpublish an approved community collection post-hoc (sets it back to private/unpublished).

Dashboard & onboarding

The dashboard intro was condensed, a version footer was added, and the collections onboarding UI was improved.

Docs

• AGENTS.md rules 40–41 (moderator read-scope by lifecycle state; inline artifact editing) and rule 34's orchestration notes updated.
• README.md starter-pack counts and intro refreshed.

Downloads

Standalone CLI binaries for Linux, macOS (Intel + Apple Silicon), and Windows are attached below — no Python required. See the README for install instructions.

v1.9.0

A focused release: a 12th target framework (pi.dev), and a full navigation
redesign that regroups the sidebar by task with collapsible sections and
landing pages — plus two follow-up fixes catching what the redesign missed.

Highlights

pi.dev (Pi Coding Agent) adapter

MyACE now compiles to 12 target frameworks. The new adapter was verified
against pi.dev's real docs rather than guessed: rules/agents fold into
AGENTS.md (Pi reads it hierarchically, the same mechanism OpenCode/Goose
use), skills map to .pi/skills/<name>/SKILL.md, workflows map to Pi's real
slash-command "prompt templates" (.pi/prompts/<name>.md), and model
configs merge into .pi/settings.json. MCP config is deliberately left
unimplemented — pi.dev/docs/latest/mcp 404s and no primary-source config
shape could be confirmed, so it's flagged as a follow-up rather than
fabricated.

Grouped, collapsible navigation

• The sidebar's flat 9-item list is replaced with four task-based,
  collapsible sections — Collections, Build, My Machine, and
  Settings — each collapsed by default and auto-expanding for whichever
  section contains the current page, with an indented sub-menu and a
  rotating chevron to indicate state.
• Every section now has its own landing "hub" page — a short description
  plus a card per page in that section, so a first-time visitor understands
  what a section is for before clicking into it.
• Settings is renamed from "Account", and its personal-account page is
  renamed Account (now at /settings/account) so the group and its own
  child page stop sharing a name now that Moderation and System are visible
  siblings.
• Every page that moved keeps its old top-level path alive as a redirect
  (/profiles, /compile, /import, /setup-audit, /sync,
  /orchestration(/build), /moderation, /admin/system all forward to
  their new grouped location) — nothing bookmarked before this release
  breaks.
• The Dashboard's subtitle and each hub's description were rewritten, and
  all four README screenshots (login, dashboard, collections, compile) were
  recaptured against the new UI.

Fixed

• The public, logged-out /welcome page still advertised "11 target
  frameworks" and omitted pi.dev from its list — missed by the adapter PR
  since it never touches that page.
• A documentation sweep found several frontend-route mentions
  (Orchestration Gallery, Compile page, Sync Dashboard, and four
  "Settings page" references) still pointing at pre-redesign paths.

Docs

• AGENTS.md rule 38 documents the new navigation structure: the single
  source of truth (frontend/src/lib/navigation.ts), the collapse/expand
  behavior, the hub-page pattern, and the full legacy-redirect table.
• README.md's adapter table, feature list, and repository-structure tree
  are all updated for pi.dev and the new frontend/src/pages layout.

Downloads

Standalone CLI binaries for Linux, macOS (Intel + Apple Silicon), and
Windows are attached below — no Python required. See the
README
for install instructions.

v1.8.0

The biggest release yet: a full community-moderation system (roles,
approval queue, ratings, comments, notification preferences), plus four
independent platform upgrades — compile-time validation, sync/drift
detection, multi-agent orchestration tooling, and a public demo + local
setup audit for onboarding. Nine new features across five merged branches,
each carrying its own ADR(s) and a dedicated multi-angle code-review pass
before merge.

Highlights

Community moderation, ratings & comments

• Moderator role — a new user/moderator/admin tier, additive
  alongside the existing admin flag, assignable from the admin Users
  table (ADR-0007).
• Real moderation queue — publishing a collection now only submits it
  for review; approve/deny (moderator/admin only) is the sole path that
  makes it public (ADR-0008). Denied submissions can be edited and
  resubmitted without starting over.
• Ratings & comments — 1-5 star ratings and comments on approved
  collections, with self-rating blocked and sorting by rating/downloads/
  name on both the community listing and the moderation queue.
• Notification preferences — opt into a daily download digest or
  immediate comment notifications, per user.

Compile-time validation

• Compiling a profile now returns a warnings list alongside the
  compiled files — starting with name_collision, which catches two
  composed collections silently overriding the same artifact name (a
  problem that previously required a documented manual grep to catch).
  myace pull --strict turns a warning into a non-zero exit code; the
  web UI's compile page shows a dismissible amber panel.

Sync & drift detection

• myace pull now writes a local .myace/<target>.manifest.json
  recording what it wrote and its hash. myace check and the new
  myace watch diff that against the current disk state and the
  server's live compile, so you always know whether a pulled-down
  profile has been hand-edited or gone stale — with watch --auto-pull
  safely re-pulling on staleness while never touching a locally-edited
  file. An opt-in --report flag feeds a personal Sync Dashboard in the
  web UI, and a distributable CI Action lets
  any repo that vendors compiled output fail its build on drift.

Orchestration Gallery & pipeline wizard

• Agents can now declare handoff_to: [...] in frontmatter, making the
  multi-agent routing pattern this project's own starter packs already
  used a first-class, machine-readable fact instead of only prose. The
  new Orchestration Gallery (/orchestration) turns that into a
  browsable set of pipeline "recipes" with a flow diagram; Compose your
  pipeline (/orchestration/build) lets you assemble a new linear
  pipeline from an existing profile's agents and save it as a generated
  orchestrator — no hand-written frontmatter required.

Trust & onboarding

• Try it before you sign up — the new public /welcome landing page
  embeds a live compile demo (paste or edit an AGENTS.md-style rules
  file, see Claude Code/Cursor/OpenCode output side by side), no account
  required. It's the one deliberate public, unauthenticated route in the
  backend — rate-limited, size-capped at both the transport and content
  layers, and never persists anything (ADR-0011).
• Local Setup Audit — a new page scans every supported target
  framework's conventional config location on your own machine (via the
  same local companion server Import already uses) and reports coverage
  gaps and duplicate names across them with a rough 0-100 score.
• Community collection freshness — moderators can mark an approved
  collection as manually verified; cards show "Verified {date}" or
  "Needs re-check" once that goes stale (default ~6 months), with a
  weekly digest email flagging anything overdue. Deliberately honest
  about what "verified" means: a human looked at it recently, not an
  automated check against live tool docs (ADR-0012).

Fixed

Caught during development, before ever shipping:

• DELETE /collections/{id}/rating was hard-deleting instead of
  soft-deleting, violating this repo's own soft-delete rule.
• A moderator who also owned a collection could approve or deny their
  own submission, and the moderator meta-edit endpoint had no scope
  check — either could read/edit any user's private, never-submitted
  draft by UUID if guessed.
• The compile-time name-collision check compared collection names
  instead of IDs — since collection names aren't required to be unique,
  two identically-named collections could silently defeat the exact
  detection this feature exists to provide.
• myace watch --auto-pull could write a sync manifest recording hashes
  for files it never actually wrote (when a compile response contained
  an unsafe filename), leaving check permanently confused about that
  target's state.
• The new public demo endpoint's 20KB input cap was enforced only after
  FastAPI had already buffered and parsed the full request body — closed
  with a dedicated transport-level middleware that rejects oversized
  bodies before they're ever parsed.

Docs

• Six new ADRs (0007-0012) covering the moderator role, the moderation
  state machine, manifest-based drift detection, the structured
  handoff_to field, the public demo sandbox, and manual freshness
  verification.
• AGENTS.md grew from 29 to 37 numbered rules; README.md was
  rewritten around a visitor-friendly chapter structure.
• Known limitation: the handoff_to frontmatter added to the
  software-engineer starter pack won't reach an already-seeded
  deployment automatically — starter-pack seeding only runs once per
  collection. See docs/debugging.md for the manual fix.

Downloads

Standalone CLI binaries for Linux, macOS (Intel + Apple Silicon), and
Windows are attached below — no Python required. See the
README
for install instructions.

v1.3.0

A UX-focused release: the Dashboard, Collections, and Profiles pages get a
polish pass, two new starter collections join the catalog, and a
long-running community-collection bug is fully closed out.

Highlights

• Dashboard, Collections, and Profiles UX polish — the Dashboard's
  Collections/Profiles/Target Adapters stat cards now link to their
  respective pages; collection cards show two lines of description instead
  of one; the community collection detail page sorts its artifact list by
  type (rules, workflows, agents, skills) then alphabetically; the Profiles
  page gets a proper "+ Add profile" button; and the profile detail page
  now shows the default target and visibility alongside its collections,
  plus a new "Combined Resources" card summarizing the deduplicated
  artifact count by type across the whole profile.
• 2 new starter collections — Spec-Driven Development (adapted from
  GitHub's spec-kit) and AI/LLM Engineering (grounded in
  humanlayer/12-factor-agents), plus a new debugger agent for
  Software Engineer. The starter catalog is now 15 collections
  (3 base + 12 specializations).
• "Export to GitHub" removed from the UI — collection sharing is now
  exclusively through "Publish to Community". The backend endpoint is
  untouched for direct API use, just no longer surfaced in the frontend.

Fixed

• Community collection category counts showing (0) — the community
  collection detail page had the same per-tab-refetch bug PR #51 fixed on
  the owned-collection page, but was never touched by that fix. Two prior
  attempts (#99, #102) misdiagnosed this as a stale cached SPA shell
  because only the owned-collection page was inspected; #103 fixes the
  actual query and adds regression coverage on both pages.
• Stale cached SPA shell resurrecting already-fixed frontend bugs —
  nginx served index.html with no Cache-Control header, so a browser
  could keep running an old cached shell (pointing at a no-longer-served
  JS bundle) indefinitely after a redeploy. index.html now serves
  no-cache; hashed /assets/* keep long-lived immutable caching.
• Safari zip-download race — URL.revokeObjectURL() after a
  compiled-profile zip download could fire before Safari's native "Save
  As" dialog finished reading the blob, occasionally truncating the file.

Docs

• docs/adapters-research.md reworked from a point-in-time research
  report into a living reference — only the 11 shipped adapters are
  listed as built/verified, with real doc links.
• Settings screen now shows the running app version (fetched live from
  GitHub) and a link to the repo.
• Stale references to the removed "Export to GitHub" button cleaned up
  across README.md, AGENTS.md, SECURITY.md, and
  docs/plan-collection-actions.md.

Downloads

Standalone CLI binaries for Linux, macOS (Intel + Apple Silicon), and
Windows are attached below — no Python required. See the
README
for install instructions.

v1.2.0

A big one: a full audit of every compile target's output against each framework's real, current documentation, six new starter packs, automated Postgres backups, and a friendlier community-collections experience.

Highlights

• 6 new starter packs — Data Scientist, Full-Stack Developer, DevOps/Platform Engineer, Java/Spring Developer, iOS Developer, and Android Developer join the existing set, bringing the starter collection catalog to 13.
• Automated Postgres backups — a postgres-backup sidecar runs daily pg_dump with 7-day/4-week/6-month retention, documented in the README's new Backups section.
• Community collections got real pagination, type filtering, and a friendlier publish flow — GET /community now returns {items, total} with type/offset/limit params; base collections sort before additional ones; publishing to Community is now an honest, immediate self-serve action instead of a GitHub-PR flow that never actually gated anything.
• The Wiki is now auto-synced from docs/ on every push to main that touches it — docs/ stays the single source of truth; the Wiki is a generated, one-way mirror.

Fixed

Compile adapters — a full documentation audit found 6 of 12 were producing output the real target tool couldn't actually use:

• claude_code.py: subagents had no YAML frontmatter and likely weren't registering as real subagents at all; .claude/workflows//.claude/models/ were invented paths that don't exist — skills now go to the real on-demand .claude/skills/ location instead of being inlined into always-loaded CLAUDE.md, workflows to the still-supported .claude/commands/.
• cursor.py: wrong frontmatter fields entirely (real: description/globs/alwaysApply) — a rule missing them risks not loading into context at all. Dropped the long-gone .cursorrules and two invented paths; files are named instead of sequentially numbered.
• codex_cli.py: agents should be TOML under .codex/agents/, not Markdown at an invented path; no "workflow" concept exists in Codex CLI at all; config.toml's model/provider schema was invented.
• cline.py: none of its frontmatter fields matched Cline's real schema (only paths is real).
• continue_dev.py, goose.py: one stale path each (a dropped .prompt file format; .goosehints superseded by AGENTS.md as Goose's primary context file).
• cody.py retired — its target format was never real, and Cody Free/Pro were discontinued in 2025.
• The CLI's own local-rendering copies of the Claude Code/Cursor adapters (cli/myace_cli/adapters/) had the identical bugs — brought back in sync, with new test coverage.

Starter-collection content:

• Three cross-collection name collisions that silently dropped content when two collections were composed together (security-auditor, docs-writer, Security Checklist), plus a lower-risk fourth.
• A factual error (a nonexistent Android testing library) and a stale coroutines-test API reference.
• A silently-swallowed YAML frontmatter parse bug that degraded one skill's name, priority, compatibility, and description with no error surfaced anywhere.

Elsewhere:

• Compiling a profile and downloading it as a zip could silently download a different target framework's files than the one shown in the preview, if the target dropdown was changed after compiling without recompiling.
• nginx 502s after every backend container restart — resolved by switching proxy_pass to runtime DNS resolution instead of a cached-at-startup IP.
• "My Collections" was leaking every public starter pack into new users' owned-collections view.
• Community collections sorted additional before base alphabetically instead of base first.
• Several starter-pack agents had the wrong mode field (primary instead of subagent).

Docs

• docs/ADAPTERS_RESEARCH.md rewritten with verified schemas and doc citations for all 11 shipped adapters, including 4 that never had a dedicated writeup before this audit (Claude Code, Cursor, Codex CLI, OpenCode).
• Corrected several docs (README.md, docs/architecture.md, docs/invariants.md, docs/extending.md) that described cli/myace_cli/adapters/ as a working offline fallback for myace pull — it isn't wired up yet; pull always requires a reachable server today.
• New docs/plans/starter-collections-improvements.md tracks the audit's remaining follow-up work (a windsurf.py fix pending a naming decision, an amazon_q.py enhancement, and a few smaller structural items).

Downloads

Standalone CLI binaries for Linux, macOS (Intel + Apple Silicon), and Windows are attached below — no Python required. See the README for install instructions.

v1.1.0

v1.1.0 — Aider, Continue, Goose, Cody, and Amazon Q Developer adapters

v1.0.2

Patch release — fixes the opencode compile target, which was producing files no real OpenCode installation could actually read.

Fixed

• Compiling a profile to OpenCode produced JSON files everywhere. Verified against the official OpenCode docs: real OpenCode expects Markdown with YAML frontmatter for skills (.opencode/skills/<name>/SKILL.md), agents (.opencode/agents/<name>.md), and commands (.opencode/commands/<name>.md) — only the model/MCP config (opencode.json, a single merged file) is JSON. The adapter now matches the real format exactly, verified against the docs' own example files.
• Profiles compiled to OpenCode now round-trip cleanly back through MyACE's own scanner (re-importing a compiled skill preserves its version/priority/tags).

Also included since v1.0.1

• Version bump only, plus the fix above. See the v1.0.0 release notes for the full feature set.

Downloads

Standalone CLI binaries for Linux, macOS (Intel + Apple Silicon), and Windows are attached below.

v1.0.1

Patch release — fixes a real bug in v1.0.0 that only showed up when actually completing a GitHub sign-in end to end.

Fixed

• GitHub OAuth login 500'd fetching the user's profile. GitHub isn't an OIDC provider, so it has no .well-known/openid-configuration discovery document — the backend's OAuth client needed an explicit userinfo_endpoint, which it didn't have, and GitHub's /user response uses different field names (and can omit email) than the OIDC shape the rest of the login code assumed. Google and generic OIDC sign-in were never affected.

Also included since v1.0.0

• Version bump only, plus the fix above — no other functional changes. See the v1.0.0 release notes for the full feature set (auth hardening, admin controls, responsive UI, etc.).

Downloads

Standalone CLI binaries for Linux, macOS (Intel + Apple Silicon), and Windows are attached below.