ECLI
Engineering Command-Line Interface
ECLI is a companion engineering-workspace direction for the PySH ecosystem. It is being developed separately from the stable PySH release contract. PySH 1.0.0 does not require ECLI, and ECLI roadmap concepts must not be read as shipped PySH v1 capabilities.
ECLI integration concept
PySH stable release: 1.0.0
Status: companion workspace / roadmap
PySH works independently of ECLI
ECLI Design Direction
PySH Core
Stable shell, script runner, Python execution layer, Plugin API, and diagnostics remain independent of ECLI.
Editor Workspace
ECLI is intended to provide a dedicated engineering workspace around code, projects, and automation.
Integration Boundary
Future integration must use explicit interfaces rather than making ECLI a hidden dependency of the PySH shell.
Future Assistance
AI-assisted or higher-level workspace features are roadmap concepts and are not PySH v1 runtime capabilities.
PySH + ECLI Integration
PySH and ECLI may evolve toward a coordinated engineering workflow, but the stable PySH v1 contract remains complete and usable without ECLI.
Build with PySH today
Use the stable shell, .pysh scripts, Python execution layer, plugins, and diagnostics without ECLI.
Develop ECLI independently
Treat the workspace/editor layer as a separate project with its own release lifecycle.
Integrate through explicit contracts
Future integration must preserve PySH's stable public API, shell semantics, and security boundaries.
Interested in ECLI?
Join the community and follow project updates.
Join Community