Agentstration 0.2.0-alpha.1

Agentstration 0.2.0-alpha.1

Agentstration 0.2.0-alpha.1 is a public alpha for local evaluation and contributor feedback. It expands the self-hosted Management, Runtime, Work, and Flow platform while retaining SQLite and deterministic execution as the zero-external-service defaults. It is not intended for production deployment, and public contracts and generated storage schemas remain subject to change during 0.x development.

Highlights

• Authentication is now required by default across the HTTP, MCP, and SignalR business surfaces. Workspace-scoped personal access tokens provide revocable, expiring credentials for scripts and CLI clients; their effective permissions are the intersection of live RBAC and the token allow-list.
• Declarative bootstrap is now an ordered profile catalog. Platform administrators can preview and apply profiles, select Tenant or Workspace targets, resolve typed resource bindings, install local Packs, and create editable Model Provider, Runtime Profile, Model Profile, Agent, Flow, and Entry resources. The standard source Development profiles bootstrap the disposable admin / admin fixture with Tenant dev and Workspace default.
• PostgreSQL 17 is available as an optional single-instance storage profile for the Management, Work, Flow, Runtime, Identity, and Quartz scheduler stores. SQLite remains the default. Secrets, Data Protection keys, Pack archives, and Work artifacts remain file-backed with either relational provider.
• Pack replacement now reconciles resources in place, preserves stable identities and historical Work/Flow Run snapshots, rejects locally modified resources, and requires explicit cleanup of user-owned Dashboard references. The Console also provides permission-gated cleanup of terminal Runs and selected Workspace resources.
• The Console and Workplace now provide English and French product UI catalogs with per-Principal language preferences. Flow authoring, topology inspection, completed-run replay, Workplace navigation, long-running conversation presentation, responsive layouts, and resource/YAML editing received substantial usability updates.
• Development and operations tooling now includes Swagger UI for the Development HTTP API, isolated Aspire development slots, readiness reporting, PostgreSQL-aware startup validation, and worktree-isolated PostgreSQL volumes.

Breaking changes

• The legacy GUID-based content Workspace, Inbox, ingestion, Memory, and Mission vertical has been removed, including its HTTP, Razor, worker, persistence, evaluation, and built-in MCP surfaces. There is no compatibility shim or migration for .agentstration/data.json; new work must use the current Management, Work, Flow, Runtime, Tool, Pack, and Trigger boundaries. The generic /mcp endpoint remains available but publishes no built-in Agentstration platform tools.
• Previously anonymous business API, MCP, and SignalR clients must now authenticate and satisfy the contextual Workspace authorization policy. Health, authentication, bootstrap, Razor, and static-asset endpoints retain their explicitly anonymous access where required.
• No supported in-place data migration from 0.1.0-alpha.1 is provided. Back up any evaluation data that must be retained and use a fresh data directory or database for this alpha. Switching between SQLite and PostgreSQL does not migrate data.

Release artifacts

The GitHub prerelease publishes these assets:

• agentstration-server-0.2.0-alpha.1.zip: the framework-dependent authoritative server and operations Console;
• agentstration-workplace-0.2.0-alpha.1.zip: the framework-dependent standalone end-user Workplace;
• SHA256SUMS: SHA-256 checksums for both ZIP archives;
• container-image.txt: the Docker Hub repository, immutable tag, moving channel tag, target platforms, and pushed manifest digest.

The server/Console container is built with provenance and SBOM attestations for linux/amd64 and linux/arm64 and published as:

docker.io/agentstration/agentstration:0.2.0-alpha.1
docker.io/agentstration/agentstration:alpha

The immutable version tag is the reproducible release identity. The alpha tag moves to the latest alpha release, and no latest tag is published.

The ZIP applications require the .NET 10 ASP.NET Core Runtime. In separate PowerShell sessions, extract and start the server and optional Workplace on their documented local ports:

# Server and operations Console
Expand-Archive .\agentstration-server-0.2.0-alpha.1.zip -DestinationPath .\agentstration-server-0.2.0-alpha.1
$env:ASPNETCORE_URLS = "http://localhost:5100"
$env:AI__Provider = "Deterministic"
dotnet .\agentstration-server-0.2.0-alpha.1\Agentstration.Web.dll

# Standalone Workplace; the server must already be available on port 5100
Expand-Archive .\agentstration-workplace-0.2.0-alpha.1.zip -DestinationPath .\agentstration-workplace-0.2.0-alpha.1
$env:ASPNETCORE_URLS = "http://localhost:5180"
dotnet .\agentstration-workplace-0.2.0-alpha.1\Agentstration.Workplace.Web.dll

Published applications do not activate the source Development launch profile or create a default credential. Open http://localhost:5100/bootstrap on a fresh instance to create the first Platform administrator, Tenant, and Workspace, or configure an explicit declarative bootstrap profile and secret.

Run the immutable server image with persistent local state and deterministic execution:

docker run --rm -p 5100:8080 -e AI__Provider=Deterministic -v agentstration-data:/data agentstration/agentstration:0.2.0-alpha.1

The image contains the authoritative server and Console, not the separately hosted Workplace. It defaults to SQLite under /data; the optional PostgreSQL profile requires an external PostgreSQL 17 service plus the documented provider and connection-string configuration.

Upgrade notes

• Source checkouts started through the default Web or AppHost Development profile now apply the versioned development bootstrap profile. Use http-NoBootstrap, https-NoBootstrap, or --no-launch-profile when that fixture must not be applied.
• PostgreSQL uses six module-owned schemas in one database and applies five EF Core migration sets plus the Quartz schema during readiness-gated startup. Its first supported use targets an empty database; it is not an import path for SQLite or the removed legacy PostgreSQL prototype.
• PostgreSQL backups must include the database and the file-backed Data Protection keys, local secrets, Pack archives, and Work artifacts as one consistent set.

Important alpha limitations

• This remains a single-process modular monolith. Runtime dispatch, recovery, and Quartz scheduling are not distributed or clustered, including when PostgreSQL is selected.
• Flow and Tool execution provides at-least-once behavior and does not claim exactly-once external effects.
• PostgreSQL does not provide multi-instance support, and switching relational providers does not move data.
• Provider servers and models are not installed or downloaded by Agentstration. Ollama, llama.cpp, and LocalAI integrations connect to separately managed services; deterministic mode is for reproducible evaluation rather than real model execution.
• Pack dependency resolution, signatures, and a remote Gallery remain planned. Pack reconciliation is compensating across stores rather than transactionally atomic.
• Public APIs, resource contracts, Pack formats, and generated schemas may change again before a stable release.

See the current capabilities, configuration guide, declarative bootstrap reference, and versioning strategy for the implemented boundaries and operational details.