@corbat-tech/coco 2.34.0 → 2.36.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +7 -0
- package/dist/cli/index.js +7437 -5214
- package/dist/cli/index.js.map +1 -1
- package/dist/index.d.ts +1269 -2
- package/dist/index.js +3935 -575
- package/dist/index.js.map +1 -1
- package/package.json +4 -4
package/README.md
CHANGED
|
@@ -34,6 +34,7 @@ Best fit:
|
|
|
34
34
|
- Native tool use: files, git, shell, search/web, review, diff, build/test, MCP servers.
|
|
35
35
|
- Multi-provider support (API, subscription, and local models).
|
|
36
36
|
- Session-oriented REPL with slash commands, context compaction, and resumable workflows.
|
|
37
|
+
- Reusable runtime foundation for building future Coco-powered agents beyond the CLI.
|
|
37
38
|
- Reliability features for long sessions: provider retry/circuit-breaker, robust tool-call parsing, and safer stream error handling.
|
|
38
39
|
- Replay harness support to reproduce agent-loop behaviors from fixtures for regression testing.
|
|
39
40
|
|
|
@@ -155,6 +156,12 @@ For setup details and model matrix:
|
|
|
155
156
|
|
|
156
157
|
- [Provider Guide](docs/guides/PROVIDERS.md)
|
|
157
158
|
|
|
159
|
+
## Runtime Reuse
|
|
160
|
+
|
|
161
|
+
Coco's CLI runs on a reusable agent runtime that wires providers, tools, permissions, sessions, event logs, and workflow metadata behind a stable internal boundary. This keeps the programming CLI as the main product while making the same foundation reusable for future client-specific agents.
|
|
162
|
+
|
|
163
|
+
- [Runtime Architecture](docs/architecture/RUNTIME.md)
|
|
164
|
+
|
|
158
165
|
## Skills
|
|
159
166
|
|
|
160
167
|
Skills are instruction files (SKILL.md) that Coco injects into its context to follow project-specific conventions or workflows. They activate automatically by context or manually via `/skill-name`.
|