For AI agents: the complete documentation index is available at https://docs.flezise.com/26.09/llms.txt, the full documentation bundle is available at https://docs.flezise.com/26.09/llms-full.txt, and this page is available as Markdown at https://docs.flezise.com/26.09/release-notes/overview.md.
Docs
  • 26.09

    • Recent updates

    This page lists notable changes to Flezise, newest first. It opens with the capabilities available in the current release; later entries record what changes as each release ships.

    September 17, 2026

    Automated code review

    Every code change an agent produces is now checked by a panel of reviewer agents for security, performance, and quality problems, and for whether the change matches the requirement it came from, before a person reviews it. Critical findings can trigger a correction round first.

    Signed compliance evidence

    A run can produce a signed, offline-verifiable evidence bundle: the audit trail, the model-call logs, the gate results, and the acceptance-criteria screenshots, mapped to EU AI Act and ISO/IEC 42001 controls.

    Preview environments

    After an agent implements a change, Flezise brings the app up in a preview environment and hands you a URL to click through the running result. Multi-service stacks come up in full, so the change is checked against software that actually runs.

    Generated AGENTS.md files

    Flezise generates an AGENTS.md for a repository from your approved specs, so any coding agent that works in the repo starts with the project's own coding standards, design, and interfaces.

    Pull request automation

    A delivered change arrives as a pull request whose title and description are written from the approved story and the diff. An optional loop watches the pull request's checks and pushes fix commits when CI fails.

    Code intelligence from the CLI

    The swecli platform command group exposes the code graph, context packs, and evidence verification that agents use, so you can query the same signals from your terminal.

    Dev environments per stack

    Each project picks a stack, and the matching dev-environment pack installs its runtime, package manager, and tools before the agent runs, so a sandbox starts ready to build.

    Subscription model providers

    Connect Claude, OpenAI Codex, GitHub Copilot, and Kimi through their subscription sign-in instead of an API key, and route work to them like any other provider.