2025-12-29 15:30:57 +05:30
|
|
|
{
|
|
|
|
|
"name": "@x/core",
|
|
|
|
|
"private": true,
|
|
|
|
|
"type": "module",
|
|
|
|
|
"main": "./dist/index.js",
|
|
|
|
|
"types": "./dist/index.d.ts",
|
|
|
|
|
"scripts": {
|
Refactor builtin file tools beyond workspace scope
Replace workspace-scoped builtin file tools with general-purpose file-* tools that accept relative, absolute, and ~/ paths. Relative paths still resolve against the configured workdir.
File operations within the workdir are auto-approved. File operations outside the workdir now emit file permission metadata and require user approval, with support for once, session, and persistent grants.
Add a shared filesystem layer for text-focused read/write/edit/list/search operations, including binary-file safeguards for text reads. parseFile and LLMParse continue to read file buffers for document/image parsing.
Update copilot prompts, background/live-note agents, knowledge workflows, and renderer labels/UI to use the new file-* tool surface and permission details.
Add package-local Vitest setup for @x/core with colocated filesystem unit tests covering path resolution, canonical permission paths, binary detection, read/write/edit behavior, glob, and grep.
2026-05-25 16:21:40 +05:30
|
|
|
"build": "rm -rf dist && tsc -p tsconfig.build.json",
|
|
|
|
|
"dev": "tsc -w -p tsconfig.build.json",
|
|
|
|
|
"test": "vitest run",
|
|
|
|
|
"test:watch": "vitest"
|
2025-12-29 15:30:57 +05:30
|
|
|
},
|
|
|
|
|
"dependencies": {
|
feat: run code mode on an in-app ACP client with live approvals (#593)
* feat(code-mode): add ACP client engine (Layer 2 core)
Own the Agent Client Protocol client instead of shelling out to `acpx`, so code
mode can stream structured events (tool calls, diffs, plan) and surface live
permission requests. Headless acpx can't do live approvals (it only supports
--approve-all), which is why we drive the agent adapters ourselves.
- code-mode/acp/{agents,client,permission-broker,session-store,manager,types}.ts:
headless engine driving the Claude/Codex ACP adapters; one warm session per chat
with create-or-resume via session/load; approval policy (ask | auto-approve-reads
| yolo) in the broker.
- claude-exec.ts: cross-platform claude resolver (Windows .cmd EINVAL fix + macOS/Linux
GUI-PATH safety net) shared with the legacy acpx path in builtin-tools.ts.
- add @agentclientprotocol/sdk + claude/codex adapters to core.
* feat(code-mode): route code mode through code_agent_run tool + live approvals
Replace the acpx shell-out with a structured code_agent_run tool that drives the
ACP engine directly, streaming the agent's tool calls / diffs / plan into the chat
and surfacing permission requests inline.
- shared: code-mode.ts zod schemas; add code-run-event + code-run-permission-request
RunEvent variants (stream to the renderer over the existing runs:events channel);
codeRun:resolvePermission IPC channel.
- core: CodePermissionRegistry (promise-based mid-run approvals — the LLM tool-loop's
pre-call gate can't model a mid-execution wait); register codeModeManager +
codePermissionRegistry in awilix.
- core: code_agent_run builtin tool (streams via ctx.publish, asks via the registry,
cancels on ctx.signal, returns the agent summary). CodeModeConfig.approvalPolicy
(ask | auto-approve-reads | yolo; default ask). Exclude the tool from the headless
background-task / live-note / inline-task agents so they can't block on an approval.
- main: codeRun:resolvePermission handler -> registry.resolve.
- rewrite the code-with-agents skill and the runtime "Code Mode (Active)" block to call
code_agent_run instead of emitting npx acpx commands.
* feat(code-mode): render coding runs inline (live timeline + permission card)
Render a code_agent_run tool call as a live CodingRun block instead of generic
tool output: the agent's text, tool-call rows (kind icon + status + changed-file
names from diffs), a plan checklist, and resolved-permission lines — plus an
inline Allow / Always-allow / Deny card wired to codeRun:resolvePermission.
- chat-conversation.ts: ToolCall carries codeRunEvents + pendingCodePermission;
code_agent_run is excluded from tool-grouping so it renders standalone.
- App.tsx: handle code-run-event / code-run-permission-request, clear the pending
card on tool-result, handleCodePermissionResponse, render via CodingRunBlock.
* fix(code-mode): run the ACP adapter as Node under Electron + resolve it from main
Two runtime failures that only surfaced inside the packaged/bundled Electron app
(the headless harness used real node, so neither showed there):
- "ACP connection closed": the main process spawns the adapter via
process.execPath, which inside Electron is the Electron binary, not node — so
the child never ran as Node and its ACP stdio stream closed immediately. Set
ELECTRON_RUN_AS_NODE=1 on the adapter env (a no-op under real node).
- "Cannot find module '@agentclientprotocol/claude-agent-acp'": the adapters were
transitive (core) deps, unreachable from the esbuild-bundled main.cjs. Add them
as direct deps of the main app so require.resolve finds them at runtime (and so
they ship when packaged).
Also capture the adapter's stderr + exit code and enrich connection errors, so a
future failure reports the real cause instead of the opaque "ACP connection closed".
* chore(code-mode): remove dead acpx code paths and stale copy
Code mode now runs through the code_agent_run tool (owning the ACP client), so the
legacy acpx shell-out paths are dead. Remove them:
- core: envForCommand (acpx-only CLAUDE_CODE_EXECUTABLE injection) from
executeCommand; getCodeModeCommandLabel (acpx run-status label).
- renderer: the acpx-detection "switch agent / auto-flip the code-mode chip" flow —
App.tsx executeCommand detection, the permission-request onSwitchAgent button +
badge, and the composer's code-mode-detected listener.
- copy: Settings -> Code Mode and the code-with-agents skill summary no longer
mention acpx; tidy stale comments (claude-exec, command-executor).
No behavior change for code mode; the general executeCommand tool is unaffected.
* feat(code-mode): approval-policy selector in Settings
Surface the approval policy (Ask every time / Auto-approve reads / YOLO) in
Settings -> Code Mode, instead of being config-file only. The broker already
reads CodeModeConfig.approvalPolicy; this plumbs it through the
codeMode:getConfig / setConfig IPC + main handlers and adds the picker UI
(with a one-line explanation of each level). Defaults to "ask".
* fix(code-mode): harden ACP engine — turn-scoped connections, chip-authoritative agent, reliable stop
Three robustness fixes that co-modify manager.runPrompt and the code_agent_run
tool, so they land together:
- Lifecycle: scope each ACP adapter connection to the agent turn. Dispose it a
short grace (60s) after the turn ends instead of holding it for the app's life;
the next turn resumes via session/load (both agents support it). Wire
disposeAll() on app quit (was dead code). Fixes the unbounded per-chat leak of
booted agent processes.
- Agent selection: make the composer chip the source of truth. Thread codeMode
into ToolContext; code_agent_run uses it instead of the model's guessed `agent`
arg, which anchored on the thread's earlier agent and ignored a chip change.
Prompts updated to match; the run is labelled by the agent that actually ran.
- Stop/abort: guarantee a stopped turn unwinds. On abort the manager sends ACP
session/cancel, then force-kills the adapter after a 2s grace and resolves the
turn as cancelled — a wedged adapter can no longer hang the run and lock the
chat. code_agent_run returns a clean cancelled result.
* fix(code-mode): hide Codex's native console window on Windows
Codex's engine ships as a native console-subsystem binary (codex.exe). Launched
from our console-less Electron process tree, Windows allocated a fresh *visible*
console window for it; closing that window wedged the run in a pending state.
(Claude Code is a Node CLI, so it never triggers this.)
The window is created by @openai/codex's launcher (bin/codex.js), which spawns
codex.exe with no windowsHide. Patch it via pnpm to pass windowsHide: true
(CREATE_NO_WINDOW) so the console stays hidden — no window, nothing to close.
* refactor(code-mode): move ACP session files out of WorkDir/config
Per-run ACP session state is runtime state that accumulates one file per
chat run, not user/app config. Relocate it from WorkDir/config to a
dedicated WorkDir/code-mode/sessions/ so it can be listed, cleaned up, and
managed on its own without crowding config. Drop the now-redundant
codesession- filename prefix (the directory conveys it).
2026-06-05 14:45:08 +05:30
|
|
|
"@agentclientprotocol/claude-agent-acp": "^0.39.0",
|
|
|
|
|
"@agentclientprotocol/codex-acp": "^0.0.44",
|
|
|
|
|
"@agentclientprotocol/sdk": "^0.22.1",
|
2026-02-14 12:16:28 +05:30
|
|
|
"@ai-sdk/anthropic": "^2.0.63",
|
|
|
|
|
"@ai-sdk/google": "^2.0.53",
|
|
|
|
|
"@ai-sdk/openai": "^2.0.91",
|
|
|
|
|
"@ai-sdk/openai-compatible": "^1.0.33",
|
|
|
|
|
"@ai-sdk/provider": "^2.0.1",
|
2026-02-04 23:21:13 +05:30
|
|
|
"@composio/core": "^0.6.0",
|
2025-12-29 15:30:57 +05:30
|
|
|
"@google-cloud/local-auth": "^3.0.1",
|
|
|
|
|
"@modelcontextprotocol/sdk": "^1.25.1",
|
|
|
|
|
"@openrouter/ai-sdk-provider": "^1.2.6",
|
2026-01-30 13:30:06 +05:30
|
|
|
"@react-pdf/renderer": "^4.3.2",
|
|
|
|
|
"@types/react": "^19.2.7",
|
2025-12-29 15:30:57 +05:30
|
|
|
"@x/shared": "workspace:*",
|
2026-02-14 12:16:28 +05:30
|
|
|
"ai": "^5.0.133",
|
2025-12-29 15:30:57 +05:30
|
|
|
"awilix": "^12.0.5",
|
|
|
|
|
"chokidar": "^4.0.3",
|
2026-03-28 00:41:46 +05:30
|
|
|
"cors": "^2.8.6",
|
2026-02-04 23:21:13 +05:30
|
|
|
"cron-parser": "^5.5.0",
|
2026-03-28 00:41:46 +05:30
|
|
|
"express": "^5.2.1",
|
2026-01-16 15:51:29 +05:30
|
|
|
"glob": "^13.0.0",
|
2025-12-29 15:30:57 +05:30
|
|
|
"google-auth-library": "^10.5.0",
|
|
|
|
|
"googleapis": "^169.0.0",
|
Refactor builtin file tools beyond workspace scope
Replace workspace-scoped builtin file tools with general-purpose file-* tools that accept relative, absolute, and ~/ paths. Relative paths still resolve against the configured workdir.
File operations within the workdir are auto-approved. File operations outside the workdir now emit file permission metadata and require user approval, with support for once, session, and persistent grants.
Add a shared filesystem layer for text-focused read/write/edit/list/search operations, including binary-file safeguards for text reads. parseFile and LLMParse continue to read file buffers for document/image parsing.
Update copilot prompts, background/live-note agents, knowledge workflows, and renderer labels/UI to use the new file-* tool surface and permission details.
Add package-local Vitest setup for @x/core with colocated filesystem unit tests covering path resolution, canonical permission paths, binary detection, read/write/edit behavior, glob, and grep.
2026-05-25 16:21:40 +05:30
|
|
|
"isomorphic-git": "^1.29.0",
|
2026-02-07 16:11:13 +05:30
|
|
|
"mammoth": "^1.11.0",
|
2025-12-29 15:30:57 +05:30
|
|
|
"node-html-markdown": "^2.0.0",
|
|
|
|
|
"ollama-ai-provider-v2": "^1.5.4",
|
2026-01-07 12:29:20 +05:30
|
|
|
"openid-client": "^6.8.1",
|
2026-02-07 16:11:13 +05:30
|
|
|
"papaparse": "^5.5.3",
|
|
|
|
|
"pdf-parse": "^2.4.5",
|
2026-04-28 19:53:40 +05:30
|
|
|
"posthog-node": "^4.18.0",
|
2026-01-30 13:30:06 +05:30
|
|
|
"react": "^19.2.3",
|
2026-02-07 16:11:13 +05:30
|
|
|
"xlsx": "^0.18.5",
|
2025-12-29 15:30:57 +05:30
|
|
|
"yaml": "^2.8.2",
|
|
|
|
|
"zod": "^4.2.1"
|
|
|
|
|
},
|
|
|
|
|
"devDependencies": {
|
2026-03-28 00:41:46 +05:30
|
|
|
"@types/cors": "^2.8.19",
|
|
|
|
|
"@types/express": "^5.0.6",
|
2026-02-07 16:11:13 +05:30
|
|
|
"@types/node": "^25.0.3",
|
|
|
|
|
"@types/papaparse": "^5.5.2",
|
Refactor builtin file tools beyond workspace scope
Replace workspace-scoped builtin file tools with general-purpose file-* tools that accept relative, absolute, and ~/ paths. Relative paths still resolve against the configured workdir.
File operations within the workdir are auto-approved. File operations outside the workdir now emit file permission metadata and require user approval, with support for once, session, and persistent grants.
Add a shared filesystem layer for text-focused read/write/edit/list/search operations, including binary-file safeguards for text reads. parseFile and LLMParse continue to read file buffers for document/image parsing.
Update copilot prompts, background/live-note agents, knowledge workflows, and renderer labels/UI to use the new file-* tool surface and permission details.
Add package-local Vitest setup for @x/core with colocated filesystem unit tests covering path resolution, canonical permission paths, binary detection, read/write/edit behavior, glob, and grep.
2026-05-25 16:21:40 +05:30
|
|
|
"@types/pdf-parse": "^1.1.5",
|
|
|
|
|
"vitest": "catalog:"
|
2025-12-29 15:30:57 +05:30
|
|
|
}
|
|
|
|
|
}
|