@melaya/runner 1.0.54 → 1.0.55
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/dist/connection.js +20 -0
- package/package.json +1 -1
package/dist/connection.js
CHANGED
|
@@ -317,6 +317,26 @@ export async function connect(opts) {
|
|
|
317
317
|
MEL_RELAY_NONCE: relay.nonce,
|
|
318
318
|
LMSTUDIO_BASE_URL: "http://127.0.0.1:1234",
|
|
319
319
|
OLLAMA_BASE_URL: "http://127.0.0.1:11434",
|
|
320
|
+
// Tool-output directory convention (2026-06-07). File-producing
|
|
321
|
+
// tools (meme_generate, excel writers, …) read MELAYA_OUTPUT_DIR
|
|
322
|
+
// and default their save_to here. For local-runner pipelines we
|
|
323
|
+
// point it at ~/Documents/Melaya-Pipelines/<pipeline>/outputs/ so
|
|
324
|
+
// the file lands somewhere persistent on the user's box (NOT the
|
|
325
|
+
// ephemeral runDir which the runbook expects to survive across
|
|
326
|
+
// runs). The pipeline_dir copy at <runDir>/outputs/ that codegen
|
|
327
|
+
// would create on cloud-spawn is overridden here because the
|
|
328
|
+
// codegen template uses `os.environ.setdefault(...)` — the
|
|
329
|
+
// runner-set value wins. See AddNewTool.md §2d.
|
|
330
|
+
MELAYA_OUTPUT_DIR: (() => {
|
|
331
|
+
const dir = join(homedir(), "Documents", "Melaya-Pipelines", payload.pipelineName, "outputs");
|
|
332
|
+
try {
|
|
333
|
+
mkdirSync(dir, { recursive: true });
|
|
334
|
+
}
|
|
335
|
+
catch (e) {
|
|
336
|
+
console.log(chalk.yellow(` ! could not create output dir ${dir}: ${e.message}`));
|
|
337
|
+
}
|
|
338
|
+
return dir;
|
|
339
|
+
})(),
|
|
320
340
|
// Inject per-pipeline credentials (already scoped by the server)
|
|
321
341
|
...payload.credentials,
|
|
322
342
|
// If a Luma browser bridge is up (i.e. the user has signed in
|