delegation-layer 0.1.37 → 0.1.38

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": "delegation-layer",
3
- "version": "0.1.37",
3
+ "version": "0.1.38",
4
4
  "description": "Multi-provider AI agent delegation CLI and Agent Skill for running bounded coding tasks across provider CLIs.",
5
5
  "keywords": [
6
6
  "ai-agents",
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "delegation-layer",
3
3
  "displayName": "Delegation Layer",
4
- "version": "0.1.37",
4
+ "version": "0.1.38",
5
5
  "description": "Consult external AI harnesses and CCR-configured models for reviews, research, implementation, and debate through the resumable Delegate CLI.",
6
6
  "author": {
7
7
  "name": "Hesham Karam",
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "delegation-layer",
3
- "version": "0.1.37",
3
+ "version": "0.1.38",
4
4
  "description": "Consult external AI harnesses and CCR-configured models for reviews, research, implementation, and debate through the resumable Delegate CLI.",
5
5
  "author": {
6
6
  "name": "Hesham Karam",
@@ -40,9 +40,16 @@ but it does not authorize a fresh dispatch. Apply the remaining `task_record`
40
40
  error rules in [result handling](result-handling.md) before retrying or
41
41
  observing.
42
42
 
43
+ Run `continue` with the same state root as the predecessor. The new turn uses
44
+ the environment of the process that calls `continue`, not an environment saved
45
+ by the predecessor, so the exact recorded session must be available there. If
46
+ `continue` fails because it is not, report the failure and stop. Do not copy
47
+ credentials or settings from another environment, choose a fresh session or
48
+ another provider, or dispatch again to repair the failure.
49
+
43
50
  When the predecessor is bound to a managed workspace, `continue --task` carries
44
- the recorded workspace, working directory, provider session, and environment
45
- to the new task ID. It does not mutate the predecessor's immutable request or
51
+ the recorded workspace, working directory, and provider session to the new task
52
+ ID. The new turn runs in the calling environment. It does not mutate the predecessor's immutable request or
46
53
  reservation. A changed provider request is a new turn and must pass the normal
47
54
  workspace-use reservation. Read [managed workspace guidance](workspaces.md)
48
55
  before attaching another provider, review, or verification operation.
@@ -102,9 +102,11 @@ flag. This auxiliary budget is separate from and does not renew the provider
102
102
  task budget. The existing `codex:review` default remains 1 hour.
103
103
 
104
104
  `continue --task PREDECESSOR_ID` inherits the predecessor's managed workspace,
105
- working directory, provider session, and recorded environment, while creating
106
- a new task ID. A changed provider request is a new turn; it must not mutate the
107
- predecessor's immutable records. A retained workspace can be used by a
105
+ working directory, and provider session, while creating a new task ID. The new
106
+ turn runs in the calling environment, so the exact recorded session must be
107
+ available there; see [continuation](continuation.md). The predecessor's
108
+ admitted records stay unchanged. A changed provider request is a new turn; it
109
+ must not mutate the predecessor's immutable records. A retained workspace can be used by a
108
110
  read-only review by attaching its ID, for example:
109
111
 
110
112
  ```text
@@ -40,9 +40,16 @@ but it does not authorize a fresh dispatch. Apply the remaining `task_record`
40
40
  error rules in [result handling](result-handling.md) before retrying or
41
41
  observing.
42
42
 
43
+ Run `continue` with the same state root as the predecessor. The new turn uses
44
+ the environment of the process that calls `continue`, not an environment saved
45
+ by the predecessor, so the exact recorded session must be available there. If
46
+ `continue` fails because it is not, report the failure and stop. Do not copy
47
+ credentials or settings from another environment, choose a fresh session or
48
+ another provider, or dispatch again to repair the failure.
49
+
43
50
  When the predecessor is bound to a managed workspace, `continue --task` carries
44
- the recorded workspace, working directory, provider session, and environment
45
- to the new task ID. It does not mutate the predecessor's immutable request or
51
+ the recorded workspace, working directory, and provider session to the new task
52
+ ID. The new turn runs in the calling environment. It does not mutate the predecessor's immutable request or
46
53
  reservation. A changed provider request is a new turn and must pass the normal
47
54
  workspace-use reservation. Read [managed workspace guidance](workspaces.md)
48
55
  before attaching another provider, review, or verification operation.
@@ -102,9 +102,11 @@ flag. This auxiliary budget is separate from and does not renew the provider
102
102
  task budget. The existing `codex:review` default remains 1 hour.
103
103
 
104
104
  `continue --task PREDECESSOR_ID` inherits the predecessor's managed workspace,
105
- working directory, provider session, and recorded environment, while creating
106
- a new task ID. A changed provider request is a new turn; it must not mutate the
107
- predecessor's immutable records. A retained workspace can be used by a
105
+ working directory, and provider session, while creating a new task ID. The new
106
+ turn runs in the calling environment, so the exact recorded session must be
107
+ available there; see [continuation](continuation.md). The predecessor's
108
+ admitted records stay unchanged. A changed provider request is a new turn; it
109
+ must not mutate the predecessor's immutable records. A retained workspace can be used by a
108
110
  read-only review by attaching its ID, for example:
109
111
 
110
112
  ```text