create-orcha 0.1.4 → 0.1.6

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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "create-orcha",
3
- "version": "0.1.4",
3
+ "version": "0.1.6",
4
4
  "description": "Create a complete OrchaJS project with example agents and a local playground.",
5
5
  "type": "module",
6
6
  "license": "MIT",
@@ -11,6 +11,8 @@ cp .env.example .env
11
11
  npm run dev
12
12
  ```
13
13
 
14
+ The included Node.js scripts load `.env` before starting the application.
15
+
14
16
  Open [http://127.0.0.1:4310](http://127.0.0.1:4310).
15
17
 
16
18
  Try the general `assistant`, ask `orderSupport` about `ord_1001`, `ord_1002`,
@@ -47,7 +49,8 @@ npm run orcha:dev # validate and watch the Orcha registry
47
49
  npm run orcha:test # run registered agent tests
48
50
  ```
49
51
 
50
- The default Node configuration stores sessions in `.orcha/sessions`. The
52
+ The default Node configuration stores sessions in
53
+ `.orcha/sessions/<agentName>/ses_<timestamp>_<uuid>.jsonl`. The
51
54
  playground accesses parent sessions through `agent.list()`, `agent.get()`, and
52
55
  `agent.events()`, and child sessions through `agent.subagentHistory()`, so
53
56
  changing the storage adapter does not require UI or server changes.
@@ -20,7 +20,7 @@ files under `.orcha/`.
20
20
 
21
21
  `run` and `test` use real providers and require credentials. `dev` and
22
22
  `build` are offline. Session logs are JSONL files under
23
- `.orcha/sessions/<sessionId>.jsonl`.
23
+ `.orcha/sessions/<agentName>/ses_<timestamp>_<uuid>.jsonl`.
24
24
 
25
25
  ## Registry
26
26
 
@@ -60,6 +60,10 @@ allows action modules to execute in its Node.js process.
60
60
  - `root` (optional): absolute or working-directory-relative project root;
61
61
  defaults to `ORCHA_PROJECT_ROOT` and then `process.cwd()`.
62
62
 
63
+ The Orcha library reads the host application's existing `process.env`.
64
+ Standalone Orcha CLI commands also load `.env` from the project root without
65
+ overriding environment variables already in the process.
66
+
63
67
  Provider configuration shapes:
64
68
 
65
69
  ```ts
@@ -512,7 +516,7 @@ real actions. The mocked action set must exactly match the compiled action set.
512
516
  }
513
517
  ```
514
518
 
515
- Test sessions use the `ses_test_` prefix and end with a `test.completed`
519
+ Test sessions use the `ses_test_<timestamp>_<uuid>` format and end with a `test.completed`
516
520
  event. Prefer semantic output assertions; verify exact identifiers and values
517
521
  through action-argument assertions.
518
522
 
@@ -964,7 +968,7 @@ offline production compilation. Neither command invokes a provider.
964
968
 
965
969
  ### Run lifecycle
966
970
 
967
- 1. `run()` creates a `ses_<uuid>`, acquires the per-session execution lock,
971
+ 1. `run()` creates a `ses_<timestamp>_<uuid>`, acquires the per-session execution lock,
968
972
  appends `session.created`, then starts run 1.
969
973
  2. `resume()` reads and validates the existing session. Message continuation
970
974
  starts a new run; submitted client results continue the paused run.