Refactor thread management to store conversation threads in ~/.deco/pilot/threads/ for improved development experience. Update main.ts to handle user API keys for enhanced authentication and tool access. Adjust prompts initialization to an empty array for better flexibility in prompt management.

Author: vibegui

mcp-studio/server/main.ts

@@ -14,7 +14,6 @@ import {
   ensurePromptsTable,
 } from "./db/schemas/agents.ts";
 import { handleWorkflowEvents, WORKFLOW_EVENTS } from "./events/handler.ts";
-import { createPrompts } from "./prompts.ts";
 import { tools } from "./tools/index.ts";
 import { type Env, type Registry, StateSchema } from "./types/env.ts";
 
@@ -54,7 +53,7 @@ const runtime = withRuntime<Env, typeof StateSchema, Registry>({
     state: StateSchema,
   },
   tools,
-  prompts: createPrompts,
+  prompts: [],
 });
 
 serve(runtime.fetch);

pilot/docs/ARCHITECTURE.md

@@ -52,7 +52,7 @@ Pilot never calls interfaces directly. It:
 
 ### 3. Thread-Based Conversations
 
-Threads are stored as JSON files in `./data/threads/`. Each thread:
+Threads are stored as JSON files in `~/.deco/pilot/threads/`. Each thread:
 - Has a 5-minute TTL (configurable)
 - Continues if messages arrive within TTL
 - Can be closed with `/new` command