@parall/claude-agent 1.19.0 → 1.20.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.
Files changed (4) hide show
  1. package/dist/workspace.d.ts.map +1 -1
  2. package/dist/workspace.js +11 -30
  3. package/package.json +4 -4
  4. package/src/workspace.ts +17 -31
package/dist/workspace.d.ts.map CHANGED
@@ -1 +1 @@
1
- {"version":3,"file":"workspace.d.ts","sourceRoot":"","sources":["../src/workspace.ts"],"names":[],"mappings":"AAkCA,wBAAgB,qBAAqB,CACnC,YAAY,EAAE,MAAM,EACpB,GAAG,CAAC,EAAE;IAAE,IAAI,EAAE,CAAC,GAAG,EAAE,MAAM,KAAK,IAAI,CAAA;CAAE,QA0BtC"}
1
+ {"version":3,"file":"workspace.d.ts","sourceRoot":"","sources":["../src/workspace.ts"],"names":[],"mappings":"AAoBA,wBAAgB,qBAAqB,CACnC,YAAY,EAAE,MAAM,EACpB,GAAG,CAAC,EAAE;IAAE,IAAI,EAAE,CAAC,GAAG,EAAE,MAAM,KAAK,IAAI,CAAA;CAAE,QA0BtC"}
package/dist/workspace.js CHANGED
@@ -1,35 +1,16 @@
1
1
  import * as fs from "node:fs";
2
2
  import * as path from "node:path";
3
- const CLAUDE_MD = `# CLAUDE.md
4
-
5
- You are an agent in Parall IM. You participate in chats, handle tasks, and interact exclusively through the Parall CLI.
6
-
7
- ## Message Model
8
-
9
- Incoming events are rendered as structured \`[Event: ...]\` blocks.
10
- Each event includes \`[Chat: ... (prll://cht_xxx)]\` — use that chat ID (or full URI) when replying.
11
-
12
- **Your plain-text output is not delivered to anyone** — it is recorded as suppressed thinking in your session steps and discarded from the chat.
13
- To say something in a chat, you **must** invoke the Parall CLI via the Bash tool. To stay silent, simply do not invoke it.
14
-
15
- ## Parall CLI
16
-
17
- All outbound interactions go through \`@parall/cli\`. Credentials are pre-injected as environment variables — no setup needed.
18
-
19
- - \`npx --yes @parall/cli@latest messages send prll://cht_xxx --text "..."\` — reply into the triggering chat
20
- - \`npx --yes @parall/cli@latest dm prll://usr_xxx --text "..." [--no-reply]\` — direct message another user
21
- - \`npx --yes @parall/cli@latest tasks update prll://tsk_xxx --status in_progress\` — task state
22
- - \`npx --yes @parall/cli@latest no-reply [--reason "..."]\` — explicitly declare this turn silent (audit signal; not required for silence, just clarifies intent)
23
-
24
- Available env: \`PRLL_API_URL\`, \`PRLL_API_KEY\`, \`PRLL_ORG_ID\`, \`PRLL_SESSION_ID\`, \`PRLL_CHAT_ID\`, \`PRLL_TRIGGER_MESSAGE_ID\`, \`PRLL_STEP_ID_FILE\`.
25
-
26
- ## Guardrails
27
-
28
- - A dispatch may coalesce multiple events. Decide per event whether to reply via \`messages send\` / \`dm\` — events you do not act on simply receive no reply.
29
- - If an event carries \`[Hint: no_reply]\`, do not send anything for that event. \`no-reply\` is optional and only useful as an explicit intent marker.
30
- - Never try to "speak" by typing sentences like "No response needed" / "Noted" / "OK" — they are discarded, so they accomplish nothing except polluting your session log.
31
- - Keep CLI replies concise and task-focused.
32
- `;
3
+ import { BRIDGE_WORKSPACE_INSTRUCTIONS, PRLL_BEHAVIOR, PRLL_IDENTITY, PRLL_REFERENCE_GUIDE, } from "@parall/agent-core";
4
+ // Same slot order as OpenClaw / Hermes: identity → channel-context
5
+ // (BRIDGE_WORKSPACE_INSTRUCTIONS plays that role for bridge runtimes) →
6
+ // behavior → reference guide. Keeps the agent-facing prompt schema strictly
7
+ // unified across runtimes.
8
+ const CLAUDE_MD = [
9
+ PRLL_IDENTITY,
10
+ BRIDGE_WORKSPACE_INSTRUCTIONS,
11
+ PRLL_BEHAVIOR,
12
+ PRLL_REFERENCE_GUIDE,
13
+ ].join("\n\n");
33
14
  export function ensureClaudeWorkspace(workspaceDir, log) {
34
15
  fs.mkdirSync(workspaceDir, { recursive: true });
35
16
  fs.mkdirSync(path.join(workspaceDir, ".claude"), { recursive: true });
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@parall/claude-agent",
3
- "version": "1.19.0",
3
+ "version": "1.20.0",
4
4
  "description": "Claude Code bridge runtime for self-hosted Parall agents",
5
5
  "license": "MIT",
6
6
  "repository": {
@@ -25,9 +25,9 @@
25
25
  "src"
26
26
  ],
27
27
  "dependencies": {
28
- "@parall/agent-core": "1.19.0",
29
- "@parall/cli": "1.19.0",
30
- "@parall/sdk": "1.19.0"
28
+ "@parall/agent-core": "1.20.0",
29
+ "@parall/cli": "1.20.0",
30
+ "@parall/sdk": "1.20.0"
31
31
  },
32
32
  "devDependencies": {
33
33
  "@types/node": "^22.0.0",
package/src/workspace.ts CHANGED
@@ -1,36 +1,22 @@
1
1
  import * as fs from "node:fs";
2
2
  import * as path from "node:path";
3
-
4
- const CLAUDE_MD = `# CLAUDE.md
5
-
6
- You are an agent in Parall IM. You participate in chats, handle tasks, and interact exclusively through the Parall CLI.
7
-
8
- ## Message Model
9
-
10
- Incoming events are rendered as structured \`[Event: ...]\` blocks.
11
- Each event includes \`[Chat: ... (prll://cht_xxx)]\` — use that chat ID (or full URI) when replying.
12
-
13
- **Your plain-text output is not delivered to anyone** — it is recorded as suppressed thinking in your session steps and discarded from the chat.
14
- To say something in a chat, you **must** invoke the Parall CLI via the Bash tool. To stay silent, simply do not invoke it.
15
-
16
- ## Parall CLI
17
-
18
- All outbound interactions go through \`@parall/cli\`. Credentials are pre-injected as environment variables — no setup needed.
19
-
20
- - \`npx --yes @parall/cli@latest messages send prll://cht_xxx --text "..."\` — reply into the triggering chat
21
- - \`npx --yes @parall/cli@latest dm prll://usr_xxx --text "..." [--no-reply]\` — direct message another user
22
- - \`npx --yes @parall/cli@latest tasks update prll://tsk_xxx --status in_progress\` — task state
23
- - \`npx --yes @parall/cli@latest no-reply [--reason "..."]\` — explicitly declare this turn silent (audit signal; not required for silence, just clarifies intent)
24
-
25
- Available env: \`PRLL_API_URL\`, \`PRLL_API_KEY\`, \`PRLL_ORG_ID\`, \`PRLL_SESSION_ID\`, \`PRLL_CHAT_ID\`, \`PRLL_TRIGGER_MESSAGE_ID\`, \`PRLL_STEP_ID_FILE\`.
26
-
27
- ## Guardrails
28
-
29
- - A dispatch may coalesce multiple events. Decide per event whether to reply via \`messages send\` / \`dm\` — events you do not act on simply receive no reply.
30
- - If an event carries \`[Hint: no_reply]\`, do not send anything for that event. \`no-reply\` is optional and only useful as an explicit intent marker.
31
- - Never try to "speak" by typing sentences like "No response needed" / "Noted" / "OK" — they are discarded, so they accomplish nothing except polluting your session log.
32
- - Keep CLI replies concise and task-focused.
33
- `;
3
+ import {
4
+ BRIDGE_WORKSPACE_INSTRUCTIONS,
5
+ PRLL_BEHAVIOR,
6
+ PRLL_IDENTITY,
7
+ PRLL_REFERENCE_GUIDE,
8
+ } from "@parall/agent-core";
9
+
10
+ // Same slot order as OpenClaw / Hermes: identity → channel-context
11
+ // (BRIDGE_WORKSPACE_INSTRUCTIONS plays that role for bridge runtimes) →
12
+ // behavior → reference guide. Keeps the agent-facing prompt schema strictly
13
+ // unified across runtimes.
14
+ const CLAUDE_MD = [
15
+ PRLL_IDENTITY,
16
+ BRIDGE_WORKSPACE_INSTRUCTIONS,
17
+ PRLL_BEHAVIOR,
18
+ PRLL_REFERENCE_GUIDE,
19
+ ].join("\n\n");
34
20
 
35
21
  export function ensureClaudeWorkspace(
36
22
  workspaceDir: string,