From 6e37e5e26bec608364a1a6700870c64037053ec2 Mon Sep 17 00:00:00 2001
From: Paul Gschwendtner <paulgschwendtner@gmail.com>
Date: Thu, 4 Dec 2025 17:12:54 +0000
Subject: [PATCH] feat: support absolute paths for `projectTemplate`

Sometimes a configuration object may be used two different configs with
different paths; and `projectTemplate` should be absolute for this
reason. This is not supported right now.
---
 runner/orchestration/file-system.ts | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/runner/orchestration/file-system.ts b/runner/orchestration/file-system.ts
index 94ca789..00935a1 100644
--- a/runner/orchestration/file-system.ts
+++ b/runner/orchestration/file-system.ts
@@ -8,7 +8,7 @@ import {
   safeWriteFile,
 } from '../file-system-utils.js';
 import {LlmContextFile, LlmResponseFile, RootPromptDefinition} from '../shared-interfaces.js';
-import {join} from 'path';
+import {join, resolve} from 'path';
 import {existsSync} from 'fs';
 import {mkdir, mkdtemp, readFile} from 'fs/promises';
 import {globSync} from 'tinyglobby';
@@ -60,7 +60,7 @@ export async function setupProjectStructure(
   const directoriesToCopy: string[] = [];
 
   if (env.executor instanceof LocalExecutor && env.executor.config.projectTemplate) {
-    const projectTemplatePath = join(env.rootPath, env.executor.config.projectTemplate);
+    const projectTemplatePath = resolve(env.rootPath, env.executor.config.projectTemplate);
 
     // Copy the template files first.
     directoriesToCopy.push(projectTemplatePath);