Skip to main content

StratAgent

Tests

Give your coding agent a workspace built for your project.

Describe what you want to build. StratAgent helps your coding agent turn that request into clear responsibilities, relevant skills and reviewed tool proposals. See why each choice fits, what is missing and exactly which files will change before you approve them.

Work inside Claude Code, Codex or Antigravity, using the model you already have. No additional LLM API key is required. A generic export is available for other integrations; supported outputs and host limitations are documented below.

StratAgent is a provider-independent agent workspace architect: it connects your project request and local dependency evidence with current resource research, then turns the reviewed plan into portable workspace files you can verify, update and remove.

“Build a React dashboard with a Python API and PostgreSQL. Include testing and privacy review. No payments.”

Describe your project → Review the proposed workspace → Approve exact changes
                      → Verify and maintain the setup

Developer preview · Python 3.11+ · macOS, Linux & Windows · MIT

0.10.0 release notes · Offline walkthrough · Support · Security

0.10.0 source and release candidate: simpler setup, selected project context and grounded recommendation review. The public 0.9.0 preview keeps its versioned installation and behavior.

What makes StratAgent useful?

  • See the existing setup. Inspect project-local guidance, skill/role metadata, recorded ownership and possible overlaps before proposing additions. Existing files remain under their current ownership; matching names do not prove equivalent capabilities. Inspection scope.
  • Keep a sufficient setup. In the 0.9.0 workflow, your agent assesses needs, existing/host coverage and alternatives before adding tools. You can accept a no-change outcome with no search or new environment files; concrete gaps guide research. How assessments work.
  • A clear division of work. Compare focused ownership with specialist roles, including responsibilities, dependencies and acceptance criteria grounded in the project request.
  • Choices you can inspect. Research current GitHub and MCP Registry sources. Review relevance, alternatives, source provenance, license/static findings and coverage gaps before selecting resources. Search is bounded; popularity does not establish safety.
  • Changes you control. Review the exact file changes, authorize them and verify the installed result. Existing user files, conflicting edits and stale approvals are protected by the apply/update lifecycle.
  • A setup you can maintain. Keep one reviewed plan with host-specific outputs and recorded provenance. Update or remove managed files with drift checks and recovery as the project evolves.

StratAgent prepares the environment; your coding host builds the application. It does not autonomously launch agents or install and run arbitrary GitHub code.

Work through your coding agent

0.10.0 developer preview. Start with the isolated installer below. Earlier previews retain their versioned installation and behavior.

After installing StratAgent locally, tell your existing coding agent:

Use StratAgent to prepare this project's agent workspace. Explain the roles, useful resources and file changes before applying anything. Keep my current files and excluded features intact.

Start-to-finish setup guide. Your part is simple:

  1. Describe the outcome and constraints. Explain the project, what matters and what to leave out.
  2. Review the meaningful choices. See whether the existing setup is enough. Review needs, coverage, alternatives and gaps; public search terms and file changes follow only when needed.
  3. Keep or change the setup. Accept the reviewed no-change assessment, or authorize exact file changes and have the agent verify the installed result.

The agent carries the commands, JSON proposals, session IDs and approval digests. Existing session progress is reused; conflicts, stale context and interrupted changes are explained instead of silently resetting your work.

For one-time project integration, the agent previews stratagent connect --json, reviews the packaged first-party skill and applies its exact connection approval. Only local skill files are added; host settings, permissions and MCP servers need separate activation. A host refresh/new session may be needed for discovery. The agent then follows start and next --json, loading detailed schemas or full diffs when the current step needs them.

Agent-first workflow and limits. Advanced CLI and session-scoped MCP integrations remain available below.

Put it to work

Your project idea What to review in its workspace plan Example
React/Next.js frontend + FastAPI/PostgreSQL API Frontend/API ownership, interface coordination, testing and relevant skill/MCP candidates SaaS manifest fixtures
A pandas data-review pipeline Data-quality, testing and privacy responsibilities; offline constraints and resource gaps Data project fixture
A small offline CSV inventory checker, without a web UI Focused ownership and test review, without unnecessary web/payment tooling Runnable project + walkthrough

The first two examples are dependency fixtures, not finished applications. The CSV example includes working code and a recorded Codex pilot.

Try it locally

From a reviewed source checkout, install once without shell activation:

git clone https://github.com/eturkok/stratagent.git
cd stratagent
python3 scripts/install.py --workspace /absolute/path/to/your-project --host codex

The installer prints the exact launcher and an instruction for your existing coding agent. Use python on Windows and choose your current host. See the setup guide for offline wheels and upgrades. Attested preview assets are available only after the publication workflow completes; PyPI setup is separate.

For repeated use, ask your agent to check maintain --json. It summarizes local changes against a reviewed hash-only checkpoint. handoff --host claude --json prepares an inert scope/decision summary for a host change. See maintenance and handoff and the paired outcome evaluation.

The release verification guide covers attested wheels and native offline bundles with SBOMs. The source installer prints a launcher rather than changing PATH; use that launcher wherever the examples below say stratagent. See OS support.

Explore without network access or a model:

stratagent plan "Build a Python data-review API. Include testing and privacy. No payments."
stratagent demo --workspace ./demo-workspace/preview
stratagent demo --workspace ./demo-workspace/applied --apply
stratagent verify --workspace ./demo-workspace/applied

plan is a read-only, disclosed rule-based preview. The offline demo uses original synthetic fixtures: inspect its preview, then explicitly apply generated skill/role files and inert MCP proposals in a separate directory. Use fresh demo directories on repeat runs. It does not download third-party content or execute agents.

From your idea to a reviewed environment

Advanced: wire the model bridge and run the review/apply steps manually

Start a model-assisted session in an existing project directory; use a disposable copy first:

stratagent session-start "Build a React dashboard and Python API with PostgreSQL, testing and privacy. No payments." \
  --workspace /absolute/path/to/project --platforms claude,codex,antigravity
  1. Connect your current model. Use the returned session ID with stratagent serve --workspace /absolute/path/to/project --orchestration SESSION_ID in your host's MCP configuration. The scoped bridge lets the model read project context and submit research/architecture proposals; StratAgent does not call an LLM API itself.
  2. Approve live research. Review the proposed public search terms, destinations and budgets. Run session-search with the exact approval returned by session-request. The model then compares fresh candidates, explains missing resources and may request clarification or a separately approved refinement.
  3. Review the blueprint. Inspect blueprint --session SESSION_ID --content, source findings and generated files. Resolve blockers and allow individual repositories only after review.
  4. Stage, approve and verify. Stage the exact file diff, approve its complete hash, then check the installed outputs:
stratagent stage blueprint --session SESSION_ID --workspace /absolute/path/to/project
stratagent apply STAGE_ID --approve EXACT_APPROVAL_HASH --workspace /absolute/path/to/project
stratagent verify --workspace /absolute/path/to/project

IDs and hashes above are placeholders from your own command results. Use the same workspace throughout. Search approval is not installation approval. The model cannot grant either approval through the scoped bridge.

Follow the complete model → research → review walkthrough for host setup and exact commands. Prefer a simpler CLI entry point? prepare performs live discovery with a disclosed rule-based draft unless you supply a model/human proposal; it never silently applies the environment.

Portable by design, cautious by default

Target Current output
Claude Code Skill and role files; separate, inactive MCP proposals
Codex Agent Skills, including exported role instructions; disabled MCP proposals
Antigravity Skill and role files; disabled MCP proposals
Generic Portable instruction bundles and MCP review evidence; no universal host configuration assumed

Model-agnostic means structured proposals from your existing model or a human, not a mandatory provider SDK. Platform-agnostic means adapters share the same planning and approval core—not that every host/version has been certified. Codex role exports are not native multi-agent orchestration.

  • Reviewed content only: installation currently supports eligible text-only skill/subagent bundles. Unsupported code/assets and unknown licenses block installation. Source hashes and scans reduce risk; they do not prove safety.
  • MCP stays inactive: server proposals never overwrite active host settings or launch packages. Optional npm artifact/tool audits are separate from Registry metadata review, not permission to execute.
  • No silent changes: approvals bind exact content and outputs; identical setup verifies/no-ops, while collisions, drift and stale/partial research block application. Keep local project state private.

This is a working developer preview, not a production/GA release. Native lifecycle CI covers macOS/Linux/Windows on Python 3.11 and 3.14. Host formats are reviewed against official documentation; broader native-host and human-usefulness checks are explicitly waived for the current scope, with their evidence limits recorded in release readiness.

Use stratagent platforms to inspect versioned adapter capabilities. These renderer contracts are included in exact-plan approvals and installation provenance; they describe generated files, while actual host/version validation is tracked separately in the interoperability matrix.

Follow the host setup guide for Claude Code, Codex and Antigravity skill/role locations and scoped local MCP bridge configurations. Claude's reserved local skill names are mapped to portable exports with an sa- prefix; original source evidence remains unchanged.

Where we are taking StratAgent

Our goal is to make StratAgent worth returning to: a coding agent should produce a more useful result with it, with less setup effort and fewer unnecessary additions. We want the smallest justified environment for the job. An informed recommendation to add nothing should be a successful outcome.

The 0.9.0 preview inspects the existing environment and supports a grounded needs assessment. Keep a sufficient setup through explicit review, or use concrete gaps to guide research and resource choices. Task-performance improvements and exhaustive semantic coverage remain to be demonstrated.

The product track continues beyond the current inspection, reviewed setup and lifecycle capabilities:

  • Build on existing-environment observations. Bounded inventory and reviewed keep/research assessments are implemented; broader semantic deduplication remains further work.
  • Demonstrate recommendation value. Needs, evidence, coverage and alternatives now have a structured review path; evaluate actual task outcomes against the same coding host without StratAgent.
  • Make ongoing work easier. Give a concise account of what changed, what still fits and what needs review, with explicit limits when handing work between supported hosts.

We will judge progress by useful outcomes, setup effort, unnecessary recommendations and voluntary repeat use. Broad user preference, task-performance gains and seamless cross-host handoff have not been established. The product direction records the strategy and evidence gaps; the engineering plan tracks implementation and release readiness separately.

Go deeper

MIT license · Third-party notices

Metadata

Release files for stratagent-cli 0.10.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for stratagent-cli 0.10.0
File Size Uploaded Provenance Actions
stratagent_cli-0.10.0.tar.gz 364.1 kB With provenance Details for stratagent_cli-0.10.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for stratagent-cli 0.10.0
File Interpreter ABI Platform Actions
stratagent_cli-0.10.0-py3-none-any.whl Python 3 none any Details for stratagent_cli-0.10.0-py3-none-any.whl

Total release size: 508.2 kB

Release files / stratagent_cli-0.10.0.tar.gz

Download URL stratagent_cli-0.10.0.tar.gz
Size 364.1 kB
Tags Source
SHA-256 checksum
How to use checksums
af3ac3b48b8841ed530346a5e0dd627a3ce7370b8e2e196a5f1467e11a64c387
BLAKE2b-256 checksum
How to use checksums
fc30be7f836c801ce36f416076527ffdbbf9f52c441dde6db7c57a5498efa647
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 11, 2026.

Transparency log

Release files / stratagent_cli-0.10.0-py3-none-any.whl

Download URL stratagent_cli-0.10.0-py3-none-any.whl
Size 144.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
0dcb697debeebdf068fc1ce7174f9b43630644bbe18106c8f22efa07c15571e2
BLAKE2b-256 checksum
How to use checksums
4bad1c7655c7024428b606c6b0c26dc374b4c4f6f7206d3d9a184109c87473cd
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 11, 2026.

Transparency log

Security for stratagent-cli 0.10.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for stratagent_cli-0.10.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 11, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.10.0 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page