Recent releases added workspace support, plugin selection, token-estimator controls, telemetry, and agent middleware. The migration path is additive: existing single-repo CLI flows continue to work.
No existing --repo workflow needs to change.
New optional entry points:
--workspace <workspace.toml>forplan,pack, andbenchmark--config <path>for loading an alternate config file
New config areas that may appear in redcon.toml or workspace TOML:
[summarization][tokens][plugins][telemetry]
Workspace files also support [[repos]] entries.
Legacy config sections such as [pack] and [output] are still read for compatibility, but new configuration should use [budget] and [compression].
If you parse run.json, expect additive fields rather than shape replacement.
New fields can include:
cachesummarizertoken_estimatorimplementationsworkspacescanned_reposselected_reposagent_middleware
Consumers should ignore unknown keys rather than assuming a closed schema.
Existing engine calls remain valid:
from redcon import RedconEngine
engine = RedconEngine()
run = engine.pack(task="refactor auth middleware", repo=".")New additive API surfaces:
from redcon import (
AgentTaskRequest,
RedconMiddleware,
LocalDemoAgentAdapter,
prepare_context,
)
result = prepare_context("update auth flow", workspace="workspace.toml")New public exports include:
RedconMiddlewareAgentTaskRequestAgentMiddlewareResultprepare_context(...)enforce_budget(...)record_run(...)AgentAdapterLocalDemoAgentAdapter
- keep existing single-repo automation unchanged
- adopt workspace TOML only for cross-repo tasks
- adopt middleware only when integrating Redcon into an agent loop
- treat new artifact fields as additive metadata, not a breaking change