agent-nuvira 3.5.5 → 3.5.7
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/.agents/skills/index.json +16 -0
- package/.agents/skills/motion/SKILL.md +27 -0
- package/README.md +122 -1
- package/dist/cli/chat.d.ts +76 -17
- package/dist/cli/chat.d.ts.map +1 -1
- package/dist/cli/chat.js +330 -137
- package/dist/cli/chat.js.map +1 -1
- package/dist/cli/config.d.ts.map +1 -1
- package/dist/cli/config.js +17 -3
- package/dist/cli/config.js.map +1 -1
- package/dist/cli/doctor.d.ts +31 -2
- package/dist/cli/doctor.d.ts.map +1 -1
- package/dist/cli/doctor.js +143 -7
- package/dist/cli/doctor.js.map +1 -1
- package/dist/cli/execute.d.ts.map +1 -1
- package/dist/cli/execute.js +63 -22
- package/dist/cli/execute.js.map +1 -1
- package/dist/cli/failover-runner.js +4 -4
- package/dist/cli/failover-runner.js.map +1 -1
- package/dist/cli/gateway.js +13 -13
- package/dist/cli/gateway.js.map +1 -1
- package/dist/cli/loop-executor.d.ts +22 -0
- package/dist/cli/loop-executor.d.ts.map +1 -1
- package/dist/cli/loop-executor.js +60 -13
- package/dist/cli/loop-executor.js.map +1 -1
- package/dist/cli/parity.d.ts +12 -0
- package/dist/cli/parity.d.ts.map +1 -1
- package/dist/cli/parity.js +46 -1
- package/dist/cli/parity.js.map +1 -1
- package/dist/cli/stats.d.ts +62 -4
- package/dist/cli/stats.d.ts.map +1 -1
- package/dist/cli/stats.js +282 -5
- package/dist/cli/stats.js.map +1 -1
- package/dist/cli/tool-install-prompt.d.ts +2 -7
- package/dist/cli/tool-install-prompt.d.ts.map +1 -1
- package/dist/cli/tool-install-prompt.js +11 -28
- package/dist/cli/tool-install-prompt.js.map +1 -1
- package/dist/cli/ui/index.d.ts +2 -2
- package/dist/cli/ui/index.d.ts.map +1 -1
- package/dist/cli/ui/index.js +1 -1
- package/dist/cli/ui/index.js.map +1 -1
- package/dist/cli/ui/presenter.d.ts +43 -0
- package/dist/cli/ui/presenter.d.ts.map +1 -1
- package/dist/cli/ui/presenter.js +88 -1
- package/dist/cli/ui/presenter.js.map +1 -1
- package/dist/config/manager.d.ts +29 -1
- package/dist/config/manager.d.ts.map +1 -1
- package/dist/config/manager.js +178 -143
- package/dist/config/manager.js.map +1 -1
- package/dist/config/paths.d.ts +48 -1
- package/dist/config/paths.d.ts.map +1 -1
- package/dist/config/paths.js +59 -9
- package/dist/config/paths.js.map +1 -1
- package/dist/config/scratch-workspace.d.ts +134 -0
- package/dist/config/scratch-workspace.d.ts.map +1 -0
- package/dist/config/scratch-workspace.js +213 -0
- package/dist/config/scratch-workspace.js.map +1 -0
- package/dist/config/service-catalog.js +1 -1
- package/dist/config/service-catalog.js.map +1 -1
- package/dist/config/service-probe.js +1 -1
- package/dist/config/service-probe.js.map +1 -1
- package/dist/config/types.d.ts +22 -0
- package/dist/config/types.d.ts.map +1 -1
- package/dist/gateway/adapters.d.ts +24 -0
- package/dist/gateway/adapters.d.ts.map +1 -1
- package/dist/gateway/adapters.js +20 -8
- package/dist/gateway/adapters.js.map +1 -1
- package/dist/gateway/oversized-reply.d.ts +39 -0
- package/dist/gateway/oversized-reply.d.ts.map +1 -0
- package/dist/gateway/oversized-reply.js +54 -0
- package/dist/gateway/oversized-reply.js.map +1 -0
- package/dist/gateway/registry.d.ts +0 -10
- package/dist/gateway/registry.d.ts.map +1 -1
- package/dist/gateway/registry.js +149 -5
- package/dist/gateway/registry.js.map +1 -1
- package/dist/learning/auto-router.d.ts +30 -4
- package/dist/learning/auto-router.d.ts.map +1 -1
- package/dist/learning/auto-router.js +54 -38
- package/dist/learning/auto-router.js.map +1 -1
- package/dist/learning/cost-classification.d.ts +188 -0
- package/dist/learning/cost-classification.d.ts.map +1 -0
- package/dist/learning/cost-classification.js +294 -0
- package/dist/learning/cost-classification.js.map +1 -0
- package/dist/learning/cost-ledger-maintenance.d.ts +122 -0
- package/dist/learning/cost-ledger-maintenance.d.ts.map +1 -0
- package/dist/learning/cost-ledger-maintenance.js +289 -0
- package/dist/learning/cost-ledger-maintenance.js.map +1 -0
- package/dist/learning/cost-reconcile.d.ts +160 -0
- package/dist/learning/cost-reconcile.d.ts.map +1 -0
- package/dist/learning/cost-reconcile.js +238 -0
- package/dist/learning/cost-reconcile.js.map +1 -0
- package/dist/learning/cost-tracker.d.ts +134 -13
- package/dist/learning/cost-tracker.d.ts.map +1 -1
- package/dist/learning/cost-tracker.js +190 -68
- package/dist/learning/cost-tracker.js.map +1 -1
- package/dist/learning/model-pricing.d.ts +240 -0
- package/dist/learning/model-pricing.d.ts.map +1 -0
- package/dist/learning/model-pricing.js +309 -0
- package/dist/learning/model-pricing.js.map +1 -0
- package/dist/learning/model-selection.d.ts +15 -0
- package/dist/learning/model-selection.d.ts.map +1 -1
- package/dist/learning/model-selection.js +22 -2
- package/dist/learning/model-selection.js.map +1 -1
- package/dist/learning/model-warmup.d.ts.map +1 -1
- package/dist/learning/model-warmup.js +4 -1
- package/dist/learning/model-warmup.js.map +1 -1
- package/dist/learning/quota-ledger.d.ts +24 -0
- package/dist/learning/quota-ledger.d.ts.map +1 -1
- package/dist/learning/quota-ledger.js +40 -0
- package/dist/learning/quota-ledger.js.map +1 -1
- package/dist/learning/runtime-dependencies.d.ts +183 -0
- package/dist/learning/runtime-dependencies.d.ts.map +1 -0
- package/dist/learning/runtime-dependencies.js +349 -0
- package/dist/learning/runtime-dependencies.js.map +1 -0
- package/dist/learning/session-store.d.ts +1 -5
- package/dist/learning/session-store.d.ts.map +1 -1
- package/dist/learning/session-store.js +10 -1
- package/dist/learning/session-store.js.map +1 -1
- package/dist/learning/skill-store.d.ts.map +1 -1
- package/dist/learning/skill-store.js +6 -5
- package/dist/learning/skill-store.js.map +1 -1
- package/dist/learning/step-checkpoint.d.ts +32 -3
- package/dist/learning/step-checkpoint.d.ts.map +1 -1
- package/dist/learning/step-checkpoint.js +33 -4
- package/dist/learning/step-checkpoint.js.map +1 -1
- package/dist/mcp/settings.d.ts +15 -3
- package/dist/mcp/settings.d.ts.map +1 -1
- package/dist/mcp/settings.js +30 -15
- package/dist/mcp/settings.js.map +1 -1
- package/dist/parity/drivers.d.ts.map +1 -1
- package/dist/parity/drivers.js +31 -5
- package/dist/parity/drivers.js.map +1 -1
- package/dist/skills/bundled-skills-phase3.d.ts +14 -0
- package/dist/skills/bundled-skills-phase3.d.ts.map +1 -1
- package/dist/skills/bundled-skills-phase3.js +50 -0
- package/dist/skills/bundled-skills-phase3.js.map +1 -1
- package/dist/tools/child-agent-runtime.d.ts.map +1 -1
- package/dist/tools/child-agent-runtime.js +13 -7
- package/dist/tools/child-agent-runtime.js.map +1 -1
- package/dist/tools/followup-utils.d.ts +36 -0
- package/dist/tools/followup-utils.d.ts.map +1 -1
- package/dist/tools/followup-utils.js +66 -0
- package/dist/tools/followup-utils.js.map +1 -1
- package/dist/tools/modality/browser.js +2 -2
- package/dist/tools/modality/browser.js.map +1 -1
- package/dist/tools/modality/image-gen.d.ts +1 -1
- package/dist/tools/modality/image-gen.js +1 -1
- package/dist/tools/modality/image-providers.js +1 -1
- package/dist/tools/modality/image-providers.js.map +1 -1
- package/dist/tools/modality/motion-presets.d.ts +62 -0
- package/dist/tools/modality/motion-presets.d.ts.map +1 -0
- package/dist/tools/modality/motion-presets.js +399 -0
- package/dist/tools/modality/motion-presets.js.map +1 -0
- package/dist/tools/modality/motion-tool.d.ts +62 -0
- package/dist/tools/modality/motion-tool.d.ts.map +1 -0
- package/dist/tools/modality/motion-tool.js +220 -0
- package/dist/tools/modality/motion-tool.js.map +1 -0
- package/dist/tools/modality/motion.d.ts +298 -0
- package/dist/tools/modality/motion.d.ts.map +1 -0
- package/dist/tools/modality/motion.js +514 -0
- package/dist/tools/modality/motion.js.map +1 -0
- package/dist/tools/modality/vision.d.ts +1 -1
- package/dist/tools/modality/vision.js +1 -1
- package/dist/tools/modality/voice.js +2 -2
- package/dist/tools/modality/voice.js.map +1 -1
- package/dist/tools/neutts-synth.d.ts +3 -3
- package/dist/tools/neutts-synth.js +3 -3
- package/dist/tools/neutts-synth.js.map +1 -1
- package/dist/tools/process-liveness.d.ts +50 -0
- package/dist/tools/process-liveness.d.ts.map +1 -1
- package/dist/tools/process-liveness.js +82 -9
- package/dist/tools/process-liveness.js.map +1 -1
- package/dist/tools/registry.d.ts +1 -1
- package/dist/tools/registry.d.ts.map +1 -1
- package/dist/tools/registry.js +102 -4
- package/dist/tools/registry.js.map +1 -1
- package/dist/tools/run-terminal.d.ts.map +1 -1
- package/dist/tools/run-terminal.js +18 -1
- package/dist/tools/run-terminal.js.map +1 -1
- package/dist/tools/tool-loop.d.ts.map +1 -1
- package/dist/tools/tool-loop.js +71 -19
- package/dist/tools/tool-loop.js.map +1 -1
- package/dist/tools/toolsets.js +2 -2
- package/dist/tools/toolsets.js.map +1 -1
- package/dist/tools/web-research.d.ts +1 -1
- package/dist/tools/web-research.js +3 -3
- package/dist/tools/web-research.js.map +1 -1
- package/dist/utils/workspace-need.d.ts +84 -0
- package/dist/utils/workspace-need.d.ts.map +1 -0
- package/dist/utils/workspace-need.js +227 -0
- package/dist/utils/workspace-need.js.map +1 -0
- package/dist/web-dashboard/chat-console.d.ts +78 -0
- package/dist/web-dashboard/chat-console.d.ts.map +1 -1
- package/dist/web-dashboard/chat-console.js +122 -12
- package/dist/web-dashboard/chat-console.js.map +1 -1
- package/dist/web-dashboard/hub-data.d.ts +9 -1
- package/dist/web-dashboard/hub-data.d.ts.map +1 -1
- package/dist/web-dashboard/hub-data.js +2 -0
- package/dist/web-dashboard/hub-data.js.map +1 -1
- package/dist/web-dashboard/project-context.d.ts +1 -1
- package/dist/web-dashboard/project-context.d.ts.map +1 -1
- package/dist/web-dashboard/project-context.js +7 -1
- package/dist/web-dashboard/project-context.js.map +1 -1
- package/dist/web-dashboard/server.d.ts +33 -0
- package/dist/web-dashboard/server.d.ts.map +1 -1
- package/dist/web-dashboard/server.js +326 -23
- package/dist/web-dashboard/server.js.map +1 -1
- package/dist/web-dashboard/src/types.d.ts +109 -0
- package/dist/web-dashboard/src/types.d.ts.map +1 -1
- package/dist/web-dashboard/task-runner.d.ts +17 -1
- package/dist/web-dashboard/task-runner.d.ts.map +1 -1
- package/dist/web-dashboard/task-runner.js +40 -4
- package/dist/web-dashboard/task-runner.js.map +1 -1
- package/dist/web-dashboard/workspace-guard.d.ts +20 -21
- package/dist/web-dashboard/workspace-guard.d.ts.map +1 -1
- package/dist/web-dashboard/workspace-guard.js +20 -153
- package/dist/web-dashboard/workspace-guard.js.map +1 -1
- package/dist/web-dashboard/workspace-resolution.d.ts +23 -5
- package/dist/web-dashboard/workspace-resolution.d.ts.map +1 -1
- package/dist/web-dashboard/workspace-resolution.js +22 -4
- package/dist/web-dashboard/workspace-resolution.js.map +1 -1
- package/package.json +1 -1
- package/src/web-dashboard/public/assets/index-CzRU84ET.css +1 -0
- package/src/web-dashboard/public/assets/index-V0rIqVbg.js +236 -0
- package/src/web-dashboard/public/assets/index-V0rIqVbg.js.map +1 -0
- package/src/web-dashboard/public/index.html +2 -2
- package/src/web-dashboard/public/assets/index-DycGBWwy.js +0 -236
- package/src/web-dashboard/public/assets/index-DycGBWwy.js.map +0 -1
- package/src/web-dashboard/public/assets/index-aO3aG7ex.css +0 -1
|
@@ -1,5 +1,5 @@
|
|
|
1
1
|
/**
|
|
2
|
-
* Workspace guard — refuse to guess a working directory.
|
|
2
|
+
* Workspace guard (dashboard wording) — refuse to guess a working directory.
|
|
3
3
|
*
|
|
4
4
|
* The dashboard's chat turns run against a DIRECTORY. When the user attaches a
|
|
5
5
|
* project the turn is scoped to it. When they do NOT, the turn used to inherit
|
|
@@ -9,28 +9,23 @@
|
|
|
9
9
|
* kuttaaddon": a real, conversational-sounding answer about a project they never
|
|
10
10
|
* mentioned, which is worse than an error.
|
|
11
11
|
*
|
|
12
|
-
*
|
|
13
|
-
*
|
|
12
|
+
* WHAT REMAINS HERE: the message the USER reads (`projectAttachmentPrompt`), which
|
|
13
|
+
* is dashboard-specific — it names the composer's Select Project Folder box and
|
|
14
|
+
* the Browse button — plus re-exports of the rules. The RULES themselves moved to
|
|
15
|
+
* `utils/workspace-need.ts` because every surface needs them now (the CLI's tool
|
|
16
|
+
* context, the messaging gateway, `ask_user` adopting a folder named in a reply)
|
|
17
|
+
* and those must not depend on the dashboard. This module's callers and tests are
|
|
18
|
+
* unchanged: same names, same behaviour, one source of truth.
|
|
14
19
|
*
|
|
15
|
-
* The
|
|
16
|
-
*
|
|
17
|
-
*
|
|
18
|
-
*
|
|
19
|
-
*
|
|
20
|
-
*
|
|
21
|
-
*
|
|
22
|
-
* idea, "I want to test an agent on X" — is TEXT, and is answered inline even
|
|
23
|
-
* though it is full of development vocabulary. Gating it was the bug the user
|
|
24
|
-
* summarised as "intelligence is completely missing" about when a folder is
|
|
25
|
-
* required. See {@link isMetaOrTextAsk}.
|
|
20
|
+
* The rules, in summary (see `utils/workspace-need.ts` for the reasoning):
|
|
21
|
+
* - `needsProjectAttachment` — does this ask need a workspace at all? Narrow on
|
|
22
|
+
* purpose: chat, prose deliverables and META asks ("give me a test scenario")
|
|
23
|
+
* all answer inline and must never be gated behind a folder prompt.
|
|
24
|
+
* - `workspaceNeedForMissingFolder` — what the workspace is FOR: `'produce'`
|
|
25
|
+
* (a temporary folder serves it) vs `'read'` (only the real tree does, so the
|
|
26
|
+
* prompt below is still the right answer).
|
|
26
27
|
*/
|
|
27
|
-
|
|
28
|
-
* True when this ask needs a workspace it does not have.
|
|
29
|
-
*
|
|
30
|
-
* Exported for the tests and for the server's single call site — the rule lives
|
|
31
|
-
* in one place so the message and the decision can never drift.
|
|
32
|
-
*/
|
|
33
|
-
export declare function needsProjectAttachment(message: string): boolean;
|
|
28
|
+
export { needsProjectAttachment, workspaceNeedForMissingFolder, type MissingWorkspaceNeed, } from '../utils/workspace-need.js';
|
|
34
29
|
/**
|
|
35
30
|
* What the user sees instead of a wrong answer.
|
|
36
31
|
*
|
|
@@ -46,6 +41,10 @@ export declare function needsProjectAttachment(message: string): boolean;
|
|
|
46
41
|
* ask with "/Users/me/Documents/my-app" gets a scoped turn rather than the same
|
|
47
42
|
* ask again. THAT repeat was the reported "brutal failure … agent keep refusing
|
|
48
43
|
* even after i attach the folder".
|
|
44
|
+
*
|
|
45
|
+
* It is reached in exactly two cases now: the ask must READ or CHANGE work that
|
|
46
|
+
* already exists (a temporary folder holds none of it), or a temporary folder
|
|
47
|
+
* could not be created. A produce ask no longer dead-ends here.
|
|
49
48
|
*/
|
|
50
49
|
export declare function projectAttachmentPrompt(): string;
|
|
51
50
|
/** The followups offered with the refusal — real next actions, not filler. */
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"workspace-guard.d.ts","sourceRoot":"","sources":["../../src/web-dashboard/workspace-guard.ts"],"names":[],"mappings":"AAAA
|
|
1
|
+
{"version":3,"file":"workspace-guard.d.ts","sourceRoot":"","sources":["../../src/web-dashboard/workspace-guard.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;GA0BG;AAEH,OAAO,EACL,sBAAsB,EACtB,6BAA6B,EAC7B,KAAK,oBAAoB,GAC1B,MAAM,4BAA4B,CAAC;AAEpC;;;;;;;;;;;;;;;;;;;GAmBG;AACH,wBAAgB,uBAAuB,IAAI,MAAM,CAwBhD;AAED,8EAA8E;AAC9E,wBAAgB,0BAA0B,IAAI,KAAK,CAAC;IAAE,KAAK,EAAE,MAAM,CAAC;IAAC,MAAM,EAAE,MAAM,CAAA;CAAE,CAAC,CAKrF"}
|
|
@@ -1,5 +1,5 @@
|
|
|
1
1
|
/**
|
|
2
|
-
* Workspace guard — refuse to guess a working directory.
|
|
2
|
+
* Workspace guard (dashboard wording) — refuse to guess a working directory.
|
|
3
3
|
*
|
|
4
4
|
* The dashboard's chat turns run against a DIRECTORY. When the user attaches a
|
|
5
5
|
* project the turn is scoped to it. When they do NOT, the turn used to inherit
|
|
@@ -9,160 +9,23 @@
|
|
|
9
9
|
* kuttaaddon": a real, conversational-sounding answer about a project they never
|
|
10
10
|
* mentioned, which is worse than an error.
|
|
11
11
|
*
|
|
12
|
-
*
|
|
13
|
-
*
|
|
12
|
+
* WHAT REMAINS HERE: the message the USER reads (`projectAttachmentPrompt`), which
|
|
13
|
+
* is dashboard-specific — it names the composer's Select Project Folder box and
|
|
14
|
+
* the Browse button — plus re-exports of the rules. The RULES themselves moved to
|
|
15
|
+
* `utils/workspace-need.ts` because every surface needs them now (the CLI's tool
|
|
16
|
+
* context, the messaging gateway, `ask_user` adopting a folder named in a reply)
|
|
17
|
+
* and those must not depend on the dashboard. This module's callers and tests are
|
|
18
|
+
* unchanged: same names, same behaviour, one source of truth.
|
|
14
19
|
*
|
|
15
|
-
* The
|
|
16
|
-
*
|
|
17
|
-
*
|
|
18
|
-
*
|
|
19
|
-
*
|
|
20
|
-
*
|
|
21
|
-
*
|
|
22
|
-
* idea, "I want to test an agent on X" — is TEXT, and is answered inline even
|
|
23
|
-
* though it is full of development vocabulary. Gating it was the bug the user
|
|
24
|
-
* summarised as "intelligence is completely missing" about when a folder is
|
|
25
|
-
* required. See {@link isMetaOrTextAsk}.
|
|
26
|
-
*/
|
|
27
|
-
/**
|
|
28
|
-
* Asks that clearly target "the project/codebase" the reader is supposedly
|
|
29
|
-
* looking at — the phrase that started this: "assess this project".
|
|
30
|
-
*/
|
|
31
|
-
const PROJECT_REFERENCE_RE = /\b(?:this|the|my|our|current)\s+(?:project|repo|repository|codebase|code\s?base|workspace|app|application|code|folder|directory|solution)\b/i;
|
|
32
|
-
/** Project work: assess / review / refactor / fix / debug / test / build / audit… */
|
|
33
|
-
const PROJECT_WORK_RE = /\b(?:assess|assessment|review|audit|analyse|analyze|evaluate|inspect|examine|explore|refactor|debug|diagnose|fix|repair|migrate|upgrade|optimi[sz]e|document|test|build|compile|lint|typecheck|type-?check|run\s+the\s+tests?|set\s?up|scaffold|bootstrap)\b/i;
|
|
34
|
-
/**
|
|
35
|
-
* Filesystem deliverables: making or changing files on disk. These need a
|
|
36
|
-
* directory to land in whether or not the ask says "project".
|
|
37
|
-
*
|
|
38
|
-
* NOTE the nouns are artifacts that exist ON DISK. `class` was removed after it
|
|
39
|
-
* matched a school sense: "write an essay … for **class** 4" was read as
|
|
40
|
-
* "write a code class" and gated behind a folder prompt it did not need. A bare
|
|
41
|
-
* "class" is inherently ambiguous — code vs. school — so it is not evidence a
|
|
42
|
-
* directory is required.
|
|
43
|
-
*/
|
|
44
|
-
const FILESYSTEM_TASK_RE = /\b(?:create|write|make|add|generate|produce|build|edit|modify|update|patch|rename|move|delete|remove|save|export|append)\b[^.!?\n]{0,60}\b(?:file|files|folder|folders|directory|directories|script|module|component|document|markdown|readme|report|image|picture|photo|logo|diagram|chart|plot|icon|screenshot|video|audio)\b/i;
|
|
45
|
-
/**
|
|
46
|
-
* INLINE PROSE deliverables — an essay, a poem, a story, a letter. General
|
|
47
|
-
* chat produces these in the reply with no workspace at all, so they must never
|
|
48
|
-
* be gated, even when the request incidentally contains a code-ish word
|
|
49
|
-
* ("an essay on elephants for a **class** 4 student") or a file-ish noun
|
|
50
|
-
* ("write a **summary**").
|
|
51
|
-
*
|
|
52
|
-
* This is the user-reported false positive: after being asked to attach a folder
|
|
53
|
-
* once, an essay question was refused for the same reason, which read as the
|
|
54
|
-
* agent having stopped listening. Only an EXPLICIT file artifact (a named file,
|
|
55
|
-
* `.md`, a folder, a directory) overrides this and keeps the ask gated.
|
|
56
|
-
*/
|
|
57
|
-
const INLINE_PROSE_RE = /\b(?:write|compose|draft|create|make|produce|prepare)\b[^.!?\n]{0,40}\b(?:essay|poem|story|haiku|paragraph|letter|email|article|speech|assignment|homework|answer|explanation|description|summary|short\s+note|blurb|bio|memo)\b/i;
|
|
58
|
-
/** An explicit on-disk artifact — the only thing that overrides INLINE_PROSE_RE. */
|
|
59
|
-
const EXPLICIT_FILE_RE = /\b(?:file|files|folder|folders|directory|directories|path|\.md\b|\.txt\b|\.json\b|\.csv\b|\.docx?\b|\.pdf\b|readme|document)\b/i;
|
|
60
|
-
/**
|
|
61
|
-
* A producing verb aimed at an explicit on-disk artifact ("save it as poem.txt",
|
|
62
|
-
* "write the essay to essay.md"). This is what makes a PROSE deliverable a
|
|
63
|
-
* workspace task after all — the write target is a file, not the reply.
|
|
64
|
-
*/
|
|
65
|
-
const FILE_PRODUCING_RE = /\b(?:write|create|save|export|produce|generate|make|draft|compose|append)\b[^.!?\n]{0,40}\b(?:file|folder|directory|path|\.md\b|\.txt\b|\.json\b|\.csv\b|\.docx?\b|\.pdf\b)\b/i;
|
|
66
|
-
/** Media generation, phrased as a verb on the media itself ("generate an image"). */
|
|
67
|
-
const MEDIA_TASK_RE = /\b(?:generate|create|make|draw|render|design|produce)\b[^.!?\n]{0,40}\b(?:an?\s+)?(?:image|picture|photo|logo|diagram|chart|plot|icon|illustration|artwork|banner|thumbnail|video|audio|voiceover)\b/i;
|
|
68
|
-
// ─── META / INSTRUCTIONAL asks ──────────────────────────────────────────────
|
|
69
|
-
//
|
|
70
|
-
// The user is asking for a DESCRIPTION of work rather than the work itself: a
|
|
71
|
-
// test scenario, a prompt, a spec, a project idea, a capability challenge. The
|
|
72
|
-
// development vocabulary inside those asks names the SUBJECT, not the action,
|
|
73
|
-
// so no workspace is required — even when a producing verb appears ("…build the
|
|
74
|
-
// application…").
|
|
75
|
-
//
|
|
76
|
-
// THIS IS THE REPORTED BUG (2026-10-06). A user asked the dashboard chat to
|
|
77
|
-
// produce a project they could use to TEST an agent on a large, phased
|
|
78
|
-
// capability (planning → development → testing → docs → tool installs → build
|
|
79
|
-
// → git). The guard read "build the application" — a producing verb on a
|
|
80
|
-
// project noun — and refused with the folder prompt. The clarification "this
|
|
81
|
-
// is not a development ask - i need text" was refused IDENTICALLY, because the
|
|
82
|
-
// guard never looked at the FRAME of the request, only at the verbs and nouns
|
|
83
|
-
// buried inside it. The user's summary: "intelligence is completely missing"
|
|
84
|
-
// around when a folder is required and when it is not.
|
|
85
|
-
/**
|
|
86
|
-
* "I want to test an agent on … capability" — the ask is about evaluating the
|
|
87
|
-
* agent, which is answered with text (a scenario/spec), never by opening a
|
|
88
|
-
* folder. Requires an intent-to-test frame so a bare "test my agent's code"
|
|
89
|
-
* (which may well mean an attached checkout) is not swept up.
|
|
90
|
-
*/
|
|
91
|
-
const META_AGENT_TEST_RE = /\b(?:want|need|plan(?:ning)?|intend|would\s+like|trying|going|help(?:\s+me)?|how\s+to|how\s+do\s+i|i\s+am|i'?m)\b[^.!?\n]{0,40}\b(?:test|testing|evaluate|evaluating|benchmark(?:ing)?|assess(?:ing)?|challenge|validate|stress[- ]?test)\b[^.!?\n]{0,50}\b(?:an?|the|my|our|your)\s+(?:ai\s+|coding\s+|development\s+|software\s+|autonomous\s+)?agents?\b/i;
|
|
92
|
-
/** "give me a test scenario / a prompt / a spec / a project idea" — a content deliverable, answered inline. */
|
|
93
|
-
const REQUEST_FOR_SCENARIO_RE = /\b(?:give|provide|suggest|design|create|write|draft|generate|propose|come\s+up\s+with|share|need|want)\b[^.!?\n]{0,30}\b(?:prompt|scenario|test\s+case|test\s+plan|test\s+suite|benchmark|spec|specification|project\s+idea|project\s+spec|example\s+project|sample\s+project|use\s+case|exercise|task\s+description|evaluation\s+rubric|rubric)\b/i;
|
|
94
|
-
/** "a project which will require this" — an indefinite, hypothetical project, not a folder the user points at. */
|
|
95
|
-
const HYPOTHETICAL_PROJECT_RE = /\b(?:a|some|any)\s+(?:project|app|application|system|tool|service|repo(?:sitory)?|codebase)\b[^.!?\n]{0,40}\b(?:that|which)\b[^.!?\n]{0,40}\b(?:requires?|would\s+require|will\s+require|needs?|would\s+need|involves?|entails?|would\s+involve)\b/i;
|
|
96
|
-
/** An explicit statement that the user wants TEXT, not code — decisive on its own. */
|
|
97
|
-
const TEXT_ONLY_RE = /\b(?:i\s+(?:just\s+)?need(?:ed)?\s+(?:the\s+)?text|just\s+the\s+text|only\s+(?:the\s+)?text|text\s+only|no\s+code|without\s+(?:any\s+)?code|need\s+text|not\s+a\s+(?:development|coding|code|software|programming)\s+(?:ask|task|request|question|exercise|work)|this\s+is\s+not\s+a\s+development|no\s+development\s+needed|nothing\s+to\s+(?:build|code|develop|implement))\b/i;
|
|
98
|
-
/**
|
|
99
|
-
* A reference to a REAL workspace the user points AT ("this project", "our
|
|
100
|
-
* repo"). When present the ask is about a folder, so the meta rules stand down
|
|
101
|
-
* — "test this project" is still a workspace ask.
|
|
102
|
-
*/
|
|
103
|
-
const DEICTIC_WORKSPACE_RE = /\b(?:this|my|our|the\s+current|current)\s+(?:project|repo|repository|codebase|code\s?base|workspace|solution)\b/i;
|
|
104
|
-
/**
|
|
105
|
-
* True when this ask only DESCRIBES work — a scenario, spec, prompt, capability
|
|
106
|
-
* challenge, or a plain request for text — rather than asking to perform it.
|
|
107
|
-
*
|
|
108
|
-
* Order matters: an explicit on-disk artifact always wins ("write the scenario
|
|
109
|
-
* to scenario.md" is a workspace ask), then an explicit "I need text" wins over
|
|
110
|
-
* a deictic mention (the user's own clarification said "this project" while
|
|
111
|
-
* explicitly asking for text), then a deictic workspace reference otherwise
|
|
112
|
-
* vetoes the meta rules.
|
|
20
|
+
* The rules, in summary (see `utils/workspace-need.ts` for the reasoning):
|
|
21
|
+
* - `needsProjectAttachment` — does this ask need a workspace at all? Narrow on
|
|
22
|
+
* purpose: chat, prose deliverables and META asks ("give me a test scenario")
|
|
23
|
+
* all answer inline and must never be gated behind a folder prompt.
|
|
24
|
+
* - `workspaceNeedForMissingFolder` — what the workspace is FOR: `'produce'`
|
|
25
|
+
* (a temporary folder serves it) vs `'read'` (only the real tree does, so the
|
|
26
|
+
* prompt below is still the right answer).
|
|
113
27
|
*/
|
|
114
|
-
|
|
115
|
-
if (EXPLICIT_FILE_RE.test(text))
|
|
116
|
-
return false;
|
|
117
|
-
if (TEXT_ONLY_RE.test(text))
|
|
118
|
-
return true;
|
|
119
|
-
if (DEICTIC_WORKSPACE_RE.test(text))
|
|
120
|
-
return false;
|
|
121
|
-
return (META_AGENT_TEST_RE.test(text) ||
|
|
122
|
-
REQUEST_FOR_SCENARIO_RE.test(text) ||
|
|
123
|
-
HYPOTHETICAL_PROJECT_RE.test(text));
|
|
124
|
-
}
|
|
125
|
-
/**
|
|
126
|
-
* True when this ask needs a workspace it does not have.
|
|
127
|
-
*
|
|
128
|
-
* Exported for the tests and for the server's single call site — the rule lives
|
|
129
|
-
* in one place so the message and the decision can never drift.
|
|
130
|
-
*/
|
|
131
|
-
export function needsProjectAttachment(message) {
|
|
132
|
-
const text = (message ?? '').trim();
|
|
133
|
-
if (!text)
|
|
134
|
-
return false;
|
|
135
|
-
// A URL or an absolute path names its own subject — the user is being
|
|
136
|
-
// specific, so asking them to "attach a folder" would be noise.
|
|
137
|
-
if (/(?:^|[\s("'`])(?:\/|~\/|https?:\/\/|www\.)/.test(text))
|
|
138
|
-
return false;
|
|
139
|
-
// A prose deliverable is answered inline; only an explicit file artifact in
|
|
140
|
-
// the same message makes it a workspace task. Checked BEFORE the project/work
|
|
141
|
-
// rules so an incidental code-ish noun cannot gate an essay or a poem.
|
|
142
|
-
if (INLINE_PROSE_RE.test(text) && !EXPLICIT_FILE_RE.test(text))
|
|
143
|
-
return false;
|
|
144
|
-
// A META ask describes work instead of doing it — a test scenario, a prompt,
|
|
145
|
-
// a spec, a project idea, or plainly "I need text". The development words in
|
|
146
|
-
// it name the SUBJECT, so answer inline rather than demanding a folder. This
|
|
147
|
-
// is the fix for the reported "test an agent on <capability>" refusal.
|
|
148
|
-
if (isMetaOrTextAsk(text))
|
|
149
|
-
return false;
|
|
150
|
-
// A named file target means it lands on disk even if the content is prose.
|
|
151
|
-
if (FILE_PRODUCING_RE.test(text))
|
|
152
|
-
return true;
|
|
153
|
-
if (PROJECT_REFERENCE_RE.test(text))
|
|
154
|
-
return true;
|
|
155
|
-
if (FILESYSTEM_TASK_RE.test(text))
|
|
156
|
-
return true;
|
|
157
|
-
if (MEDIA_TASK_RE.test(text))
|
|
158
|
-
return true;
|
|
159
|
-
// Project WORK plus a project-ish noun anywhere ("review the backend code").
|
|
160
|
-
if (PROJECT_WORK_RE.test(text) &&
|
|
161
|
-
/\b(?:project|repo|repository|codebase|code\s?base|workspace|source|backend|frontend|api|server|cli|app|application|service|package|monorepo|tests?|suite|branch|dependencies)\b/i.test(text)) {
|
|
162
|
-
return true;
|
|
163
|
-
}
|
|
164
|
-
return false;
|
|
165
|
-
}
|
|
28
|
+
export { needsProjectAttachment, workspaceNeedForMissingFolder, } from '../utils/workspace-need.js';
|
|
166
29
|
/**
|
|
167
30
|
* What the user sees instead of a wrong answer.
|
|
168
31
|
*
|
|
@@ -178,6 +41,10 @@ export function needsProjectAttachment(message) {
|
|
|
178
41
|
* ask with "/Users/me/Documents/my-app" gets a scoped turn rather than the same
|
|
179
42
|
* ask again. THAT repeat was the reported "brutal failure … agent keep refusing
|
|
180
43
|
* even after i attach the folder".
|
|
44
|
+
*
|
|
45
|
+
* It is reached in exactly two cases now: the ask must READ or CHANGE work that
|
|
46
|
+
* already exists (a temporary folder holds none of it), or a temporary folder
|
|
47
|
+
* could not be created. A produce ask no longer dead-ends here.
|
|
181
48
|
*/
|
|
182
49
|
export function projectAttachmentPrompt() {
|
|
183
50
|
return [
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"workspace-guard.js","sourceRoot":"","sources":["../../src/web-dashboard/workspace-guard.ts"],"names":[],"mappings":"AAAA
|
|
1
|
+
{"version":3,"file":"workspace-guard.js","sourceRoot":"","sources":["../../src/web-dashboard/workspace-guard.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;GA0BG;AAEH,OAAO,EACL,sBAAsB,EACtB,6BAA6B,GAE9B,MAAM,4BAA4B,CAAC;AAEpC;;;;;;;;;;;;;;;;;;;GAmBG;AACH,MAAM,UAAU,uBAAuB;IACrC,OAAO;QACL,uCAAuC;QACvC,EAAE;QACF,gGAAgG;QAChG,+FAA+F;QAC/F,mCAAmC;QACnC,EAAE;QACF,wEAAwE;QACxE,4DAA4D;QAC5D,sEAAsE;QACtE,8FAA8F;QAC9F,gBAAgB;QAChB,2EAA2E;QAC3E,EAAE;QACF,gGAAgG;QAChG,8EAA8E;QAC9E,EAAE;QACF,4FAA4F;QAC5F,4DAA4D;QAC5D,EAAE;QACF,2FAA2F;QAC3F,gGAAgG;KACjG,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;AACf,CAAC;AAED,8EAA8E;AAC9E,MAAM,UAAU,0BAA0B;IACxC,OAAO;QACL,EAAE,KAAK,EAAE,2BAA2B,EAAE,MAAM,EAAE,mCAAmC,EAAE;QACnF,EAAE,KAAK,EAAE,0BAA0B,EAAE,MAAM,EAAE,iCAAiC,EAAE;KACjF,CAAC;AACJ,CAAC"}
|
|
@@ -25,10 +25,13 @@
|
|
|
25
25
|
* were inside a project the user had pointed at. See {@link WorkspaceSource}.
|
|
26
26
|
*
|
|
27
27
|
* The order is deliberate and safe-by-default: the folder the USER attached
|
|
28
|
-
* wins, then the one this conversation already attached, then one the user
|
|
29
|
-
*
|
|
30
|
-
*
|
|
31
|
-
*
|
|
28
|
+
* wins, then the one this conversation already attached, then one the user named
|
|
29
|
+
* in their own message, then the operator's default — and then, LAST, a
|
|
30
|
+
* TEMPORARY folder for an ask that must PRODUCE something (the caller passes it
|
|
31
|
+
* as `scratchPath`, and omits it for an ask that must read or change existing
|
|
32
|
+
* work). Every rung past `attached` carries a warning, because it is a folder
|
|
33
|
+
* the user did not choose THIS turn; the scratch rung carries the loudest one,
|
|
34
|
+
* because it is not a project at all (`scratchWorkspaceNotice`).
|
|
32
35
|
*/
|
|
33
36
|
/**
|
|
34
37
|
* Re-exported so a caller of this module needs one import, not two. The rules
|
|
@@ -40,8 +43,13 @@ export { directoryFromMessage, isUsableDirectory, normalizeWorkspacePath } from
|
|
|
40
43
|
/**
|
|
41
44
|
* Where this turn's folder came from. `none` means the turn has NO workspace —
|
|
42
45
|
* the case every write must refuse to guess about.
|
|
46
|
+
*
|
|
47
|
+
* `scratch` is the last rung before `none`: a temporary folder created for a
|
|
48
|
+
* turn that must PRODUCE a file and has no project to put it in. It is never
|
|
49
|
+
* the user's project, so it always carries a notice naming the path and the ways
|
|
50
|
+
* out of it (see {@link scratchWorkspaceNotice}).
|
|
43
51
|
*/
|
|
44
|
-
export type WorkspaceSource = 'attached' | 'session' | 'message' | 'default' | 'none';
|
|
52
|
+
export type WorkspaceSource = 'attached' | 'session' | 'message' | 'default' | 'scratch' | 'none';
|
|
45
53
|
export interface ResolvedWorkspace {
|
|
46
54
|
/** The absolute directory, when there is one. */
|
|
47
55
|
path?: string;
|
|
@@ -77,6 +85,16 @@ export interface TurnWorkspaceInput {
|
|
|
77
85
|
configuredCwd?: string;
|
|
78
86
|
/** This turn's user message — the last place a folder can come from. */
|
|
79
87
|
message?: string;
|
|
88
|
+
/**
|
|
89
|
+
* The TEMPORARY folder to fall back to — created and passed by the caller
|
|
90
|
+
* (`src/config/scratch-workspace.ts`) and only offered for an ask that must
|
|
91
|
+
* PRODUCE something. OMITTED for an ask that must READ or CHANGE existing work
|
|
92
|
+
* (`workspace-guard.workspaceNeedForMissingFolder` returns `'read'` there): a
|
|
93
|
+
* scratch folder is empty, so it can neither answer "assess this project" nor
|
|
94
|
+
* hold "fix the bug in src/app.ts", and using it would be the silent-wrong-tree
|
|
95
|
+
* defect this module exists to prevent.
|
|
96
|
+
*/
|
|
97
|
+
scratchPath?: string;
|
|
80
98
|
}
|
|
81
99
|
/**
|
|
82
100
|
* Decide the turn's workspace, in priority order, with the notice it must be
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"workspace-resolution.d.ts","sourceRoot":"","sources":["../../src/web-dashboard/workspace-resolution.ts"],"names":[],"mappings":"AAAA
|
|
1
|
+
{"version":3,"file":"workspace-resolution.d.ts","sourceRoot":"","sources":["../../src/web-dashboard/workspace-resolution.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAkCG;AAOH;;;;;GAKG;AACH,OAAO,EAAE,oBAAoB,EAAE,iBAAiB,EAAE,sBAAsB,EAAE,MAAM,4BAA4B,CAAC;AAE7G;;;;;;;;GAQG;AACH,MAAM,MAAM,eAAe,GAAG,UAAU,GAAG,SAAS,GAAG,SAAS,GAAG,SAAS,GAAG,SAAS,GAAG,MAAM,CAAC;AAElG,MAAM,WAAW,iBAAiB;IAChC,iDAAiD;IACjD,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,MAAM,EAAE,eAAe,CAAC;IACxB;;;;;OAKG;IACH,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,gFAAgF;IAChF,QAAQ,EAAE,OAAO,CAAC;CACnB;AAED;;;;;;;;GAQG;AACH,wBAAgB,yBAAyB,CAAC,SAAS,EAAE,iBAAiB,GAAG,MAAM,GAAG,SAAS,CAS1F;AAED,gFAAgF;AAChF,wBAAgB,sBAAsB,CAAC,IAAI,EAAE,MAAM,GAAG,MAAM,CAQ3D;AAED,MAAM,WAAW,kBAAkB;IACjC,0DAA0D;IAC1D,YAAY,CAAC,EAAE,MAAM,CAAC;IACtB,+EAA+E;IAC/E,WAAW,CAAC,EAAE,MAAM,CAAC;IACrB,uDAAuD;IACvD,aAAa,CAAC,EAAE,MAAM,CAAC;IACvB,wEAAwE;IACxE,OAAO,CAAC,EAAE,MAAM,CAAC;IACjB;;;;;;;;OAQG;IACH,WAAW,CAAC,EAAE,MAAM,CAAC;CACtB;AAED;;;;GAIG;AACH,wBAAgB,oBAAoB,CAAC,KAAK,EAAE,kBAAkB,GAAG,iBAAiB,CA8CjF"}
|
|
@@ -25,12 +25,18 @@
|
|
|
25
25
|
* were inside a project the user had pointed at. See {@link WorkspaceSource}.
|
|
26
26
|
*
|
|
27
27
|
* The order is deliberate and safe-by-default: the folder the USER attached
|
|
28
|
-
* wins, then the one this conversation already attached, then one the user
|
|
29
|
-
*
|
|
30
|
-
*
|
|
31
|
-
*
|
|
28
|
+
* wins, then the one this conversation already attached, then one the user named
|
|
29
|
+
* in their own message, then the operator's default — and then, LAST, a
|
|
30
|
+
* TEMPORARY folder for an ask that must PRODUCE something (the caller passes it
|
|
31
|
+
* as `scratchPath`, and omits it for an ask that must read or change existing
|
|
32
|
+
* work). Every rung past `attached` carries a warning, because it is a folder
|
|
33
|
+
* the user did not choose THIS turn; the scratch rung carries the loudest one,
|
|
34
|
+
* because it is not a project at all (`scratchWorkspaceNotice`).
|
|
32
35
|
*/
|
|
33
36
|
import { directoryFromMessage, isUsableDirectory } from '../utils/workspace-path.js';
|
|
37
|
+
// The scratch notice lives with the scratch folder itself, so the messaging
|
|
38
|
+
// gateway can use it without importing a dashboard module.
|
|
39
|
+
import { scratchWorkspaceNotice } from '../config/scratch-workspace.js';
|
|
34
40
|
/**
|
|
35
41
|
* Re-exported so a caller of this module needs one import, not two. The rules
|
|
36
42
|
* themselves live in `utils/workspace-path.ts` because a TOOL also uses them
|
|
@@ -100,6 +106,18 @@ export function resolveTurnWorkspace(input) {
|
|
|
100
106
|
notice: defaultWorkspaceNotice(input.configuredCwd),
|
|
101
107
|
};
|
|
102
108
|
}
|
|
109
|
+
// The last rung: a real folder for a produce ask that has no project. Only
|
|
110
|
+
// matched when it exists (the caller creates it), so a failed scratch setup
|
|
111
|
+
// degrades to `none` and the old ask-for-a-folder behaviour rather than to a
|
|
112
|
+
// path nothing can be written into.
|
|
113
|
+
if (isUsableDirectory(input.scratchPath)) {
|
|
114
|
+
return {
|
|
115
|
+
path: input.scratchPath,
|
|
116
|
+
source: 'scratch',
|
|
117
|
+
unscoped: false,
|
|
118
|
+
notice: scratchWorkspaceNotice(input.scratchPath),
|
|
119
|
+
};
|
|
120
|
+
}
|
|
103
121
|
return { source: 'none', unscoped: true };
|
|
104
122
|
}
|
|
105
123
|
//# sourceMappingURL=workspace-resolution.js.map
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"workspace-resolution.js","sourceRoot":"","sources":["../../src/web-dashboard/workspace-resolution.ts"],"names":[],"mappings":"AAAA
|
|
1
|
+
{"version":3,"file":"workspace-resolution.js","sourceRoot":"","sources":["../../src/web-dashboard/workspace-resolution.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAkCG;AAEH,OAAO,EAAE,oBAAoB,EAAE,iBAAiB,EAAE,MAAM,4BAA4B,CAAC;AACrF,4EAA4E;AAC5E,2DAA2D;AAC3D,OAAO,EAAE,sBAAsB,EAAE,MAAM,gCAAgC,CAAC;AAExE;;;;;GAKG;AACH,OAAO,EAAE,oBAAoB,EAAE,iBAAiB,EAAE,sBAAsB,EAAE,MAAM,4BAA4B,CAAC;AA4B7G;;;;;;;;GAQG;AACH,MAAM,UAAU,yBAAyB,CAAC,SAA4B;IACpE,IAAI,SAAS,CAAC,MAAM,KAAK,UAAU;QAAE,OAAO,SAAS,CAAC;IACtD,IAAI,CAAC,SAAS,CAAC,IAAI,EAAE,CAAC;QACpB,OAAO,CACL,oFAAoF;YACpF,mDAAmD,CACpD,CAAC;IACJ,CAAC;IACD,OAAO,SAAS,CAAC,MAAM,IAAI,cAAc,SAAS,CAAC,IAAI,KAAK,SAAS,CAAC,MAAM,IAAI,CAAC;AACnF,CAAC;AAED,gFAAgF;AAChF,MAAM,UAAU,sBAAsB,CAAC,IAAY;IACjD,OAAO,CACL,wFAAwF;QACxF,sBAAsB,IAAI,iEAAiE;QAC3F,yFAAyF;QACzF,wFAAwF;QACxF,gBAAgB,CACjB,CAAC;AACJ,CAAC;AAuBD;;;;GAIG;AACH,MAAM,UAAU,oBAAoB,CAAC,KAAyB;IAC5D,IAAI,iBAAiB,CAAC,KAAK,CAAC,YAAY,CAAC,EAAE,CAAC;QAC1C,OAAO,EAAE,IAAI,EAAE,KAAK,CAAC,YAAY,EAAE,MAAM,EAAE,UAAU,EAAE,QAAQ,EAAE,KAAK,EAAE,CAAC;IAC3E,CAAC;IACD,IAAI,iBAAiB,CAAC,KAAK,CAAC,WAAW,CAAC,EAAE,CAAC;QACzC,OAAO;YACL,IAAI,EAAE,KAAK,CAAC,WAAW;YACvB,MAAM,EAAE,SAAS;YACjB,QAAQ,EAAE,KAAK;YACf,MAAM,EACJ,cAAc,KAAK,CAAC,WAAW,0DAA0D;gBACzF,6EAA6E;SAChF,CAAC;IACJ,CAAC;IACD,MAAM,KAAK,GAAG,oBAAoB,CAAC,KAAK,CAAC,OAAO,CAAC,CAAC;IAClD,IAAI,KAAK,EAAE,CAAC;QACV,OAAO;YACL,IAAI,EAAE,KAAK;YACX,MAAM,EAAE,SAAS;YACjB,QAAQ,EAAE,KAAK;YACf,MAAM,EACJ,cAAc,KAAK,4DAA4D;gBAC/E,4DAA4D;SAC/D,CAAC;IACJ,CAAC;IACD,IAAI,iBAAiB,CAAC,KAAK,CAAC,aAAa,CAAC,EAAE,CAAC;QAC3C,OAAO;YACL,IAAI,EAAE,KAAK,CAAC,aAAa;YACzB,MAAM,EAAE,SAAS;YACjB,QAAQ,EAAE,KAAK;YACf,MAAM,EAAE,sBAAsB,CAAC,KAAK,CAAC,aAAa,CAAC;SACpD,CAAC;IACJ,CAAC;IACD,2EAA2E;IAC3E,4EAA4E;IAC5E,6EAA6E;IAC7E,oCAAoC;IACpC,IAAI,iBAAiB,CAAC,KAAK,CAAC,WAAW,CAAC,EAAE,CAAC;QACzC,OAAO;YACL,IAAI,EAAE,KAAK,CAAC,WAAW;YACvB,MAAM,EAAE,SAAS;YACjB,QAAQ,EAAE,KAAK;YACf,MAAM,EAAE,sBAAsB,CAAC,KAAK,CAAC,WAAW,CAAC;SAClD,CAAC;IACJ,CAAC;IACD,OAAO,EAAE,MAAM,EAAE,MAAM,EAAE,QAAQ,EAAE,IAAI,EAAE,CAAC;AAC5C,CAAC"}
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "agent-nuvira",
|
|
3
|
-
"version": "3.5.
|
|
3
|
+
"version": "3.5.7",
|
|
4
4
|
"description": "Agent-Nuvira: Multi-agent AI coding CLI — plan, write, review, test, and publish code with local models (Ollama) or cloud APIs (Groq, NVIDIA NIM, Google Gemini, OpenRouter)",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"main": "dist/index.js",
|