repoburg 1.2.0 → 1.2.1

package/.run/backend _ build.run.xml

@@ -0,0 +1,12 @@
+<component name="ProjectRunConfigurationManager">
+  <configuration default="false" name="backend &gt; build" type="js.build_tools.npm" nameIsGenerated="true">
+    <package-json value="$PROJECT_DIR$/backend/package.json" />
+    <command value="run" />
+    <scripts>
+      <script value="build" />
+    </scripts>
+    <node-interpreter value="project" />
+    <envs />
+    <method v="2" />
+  </configuration>
+</component>

package/.run/backend _ lint.run.xml

@@ -0,0 +1,12 @@
+<component name="ProjectRunConfigurationManager">
+  <configuration default="false" name="backend &gt; lint" type="js.build_tools.npm" nameIsGenerated="true">
+    <package-json value="$PROJECT_DIR$/backend/package.json" />
+    <command value="run" />
+    <scripts>
+      <script value="lint" />
+    </scripts>
+    <node-interpreter value="project" />
+    <envs />
+    <method v="2" />
+  </configuration>
+</component>

package/.run/backend _ test.run.xml

@@ -0,0 +1,12 @@
+<component name="ProjectRunConfigurationManager">
+  <configuration default="false" name="backend &gt; test" type="js.build_tools.npm" nameIsGenerated="true">
+    <package-json value="$PROJECT_DIR$/backend/package.json" />
+    <command value="run" />
+    <scripts>
+      <script value="test" />
+    </scripts>
+    <node-interpreter value="project" />
+    <envs />
+    <method v="2" />
+  </configuration>
+</component>

package/.run/frontend _ build.run.xml

@@ -0,0 +1,12 @@
+<component name="ProjectRunConfigurationManager">
+  <configuration default="false" name="frontend &gt; build" type="js.build_tools.npm" nameIsGenerated="true">
+    <package-json value="$PROJECT_DIR$/frontend/package.json" />
+    <command value="run" />
+    <scripts>
+      <script value="build" />
+    </scripts>
+    <node-interpreter value="project" />
+    <envs />
+    <method v="2" />
+  </configuration>
+</component>

package/.run/frontend _ lint_fix.run.xml

@@ -0,0 +1,12 @@
+<component name="ProjectRunConfigurationManager">
+  <configuration default="false" name="frontend &gt; lint:fix" type="js.build_tools.npm" nameIsGenerated="true">
+    <package-json value="$PROJECT_DIR$/frontend/package.json" />
+    <command value="run" />
+    <scripts>
+      <script value="lint:fix" />
+    </scripts>
+    <node-interpreter value="project" />
+    <envs />
+    <method v="2" />
+  </configuration>
+</component>

package/CODEMAP.md

@@ -0,0 +1,182 @@
+# Repoburg Codemap
+
+This document provides a high-level overview of the Repoburg system, focusing on all its constituent projects and how they interact.
+
+## System Overview
+
+Repoburg's architecture consists of several key components working together:
+
+1.  **The `backend`**: A NestJS application that runs locally. It has access to the filesystem, manages core logic (sessions, context generation, action execution), and orchestrates the AI workflow. Each `backend` instance is managed by the `daemon`.
+2.  **The `frontend`**: A Next.js web application that serves as the main user interface for Repoburg's AI features. It communicates with a specific `backend` instance to manage sessions, view AI-generated plans, and configure the system.
+3.  **The `userscripts` (AI Studio PowerTools)**: A userscript that runs in the browser on the Google AI Studio website. It acts as the bridge between the AI chat interface and the local `backend` for the "manual mode" workflow.
+4.  **The `daemon`**: A long-running, headless background process that manages `backend` instances using `pm2`. It handles starting, stopping, and monitoring services for different projects and manages device authentication.
+5.  **The `website`**: The public-facing marketing, documentation, and user authentication portal, available at repoburg.com.
+6.  **The `daemon-desktop`**: An Electron-based desktop application that provides a graphical user interface (GUI) for the `daemon`. It allows users to manage services without using the command line.
+
+The core loop is: **Frontend** sends a prompt to the **Backend** -> **Backend** generates context and sends it to an LLM -> The LLM response is sent back to the **Backend** -> **Backend** parses it into a plan -> **Frontend** displays the plan for user review and action. The **Daemon** and **Daemon Desktop** work in the background, managing the lifecycle of the **Backend** service itself. The **Website** handles user accounts and authorizes local devices to use the service.
+
+---
+
+## Backend Architecture (`backend/`)
+
+The local server that contains the core application logic.
+
+### 🚀 Entry Point & Core
+
+-   **Entry Point**: `backend/src/main.ts`. Handles server setup, port selection, and global middleware.
+-   **Root Module**: `backend/src/app.module.ts`. Imports all other feature modules.
+-   **Architecture**: Standard NestJS modular architecture (`*.module.ts`, `*.controller.ts`, `*.service.ts`).
+
+### ✨ Key Feature Modules (`backend/src`)
+
+#### Session & Orchestration
+- **`/sessions`**: Manages the lifecycle of a user's work session (create, update, load).
+- **`/session-inputs`**: Handles a single turn of interaction (prompt creation, context generation).
+- **`/session-followup`**: Handles creating new sessions that inherit context from previous ones.
+- **`/session-transfer`**: Manages the import and export of session data.
+- **`/llm-responses`**: Receives and processes raw text responses from the LLM.
+- **`/llm-response-parser`**: Parses raw LLM text into structured actions.
+- **`/ai-actions`**: Manages the individual actions (`create_file`, `run_command`) proposed by the AI.
+- **`/action-execution`**: Performs the file system operations or runs shell commands.
+- **`/execution-logs`**: Stores logs from `action-execution`.
+- **`/interactive-chat`**: Orchestrates sending prompts to an LLM for both integrated and manual modes.
+
+#### Context & Prompting
+- **`/context-generation`**: Renders context strings from Eta.js templates using built-in helper functions.
+- **`/context-templates`**: CRUD module for managing the main context templates.
+- **`/system-prompts`**: CRUD module for managing the system prompts that define the AI's behavior.
+- **`/context-snippets`**: Manages dynamic, reusable context snippets callable with `!` in a prompt.
+- **`/custom-snippets`**: Manages static, reusable code snippets for the template editor.
+
+#### Core Services & Integrations
+- **`/workspace`**: Provides APIs to interact with the local file system (file tree, search, file content).
+- **`/llm-provider` & `/gemini`**: Defines the interface and provides the implementation for the integrated Google Gemini LLM.
+- **`/events`**: The WebSocket gateway for real-time communication between the backend, frontend, and userscripts.
+- **`/application-state`**: Manages global backend settings (e.g., active session, feature flags).
+- **`/mcp`**: Manages connections and tools for the Model Context Protocol (MCP).
+- **`/projects`**: Manages project-specific information.
+- **`/seeding`**: Seeds the database with default data (prompts, templates) on startup.
+- **`/core-entities`**: Contains all TypeORM entity definitions for the database schema.
+- **`/utils`**: Shared utility functions and decorators (e.g., fuzzy search, tracing).
+
+---
+
+## Frontend Architecture (`frontend/`)
+
+The main user interface for interacting with the Repoburg backend.
+
+### 🚀 Tech Stack & Structure
+- **Framework**: Next.js (App Router)
+- **Styling**: Tailwind CSS with shadcn/ui components.
+- **State Management**: Zustand.
+
+### ✨ Key Directories (`frontend/src`)
+
+- **`/app/components`**: Home to the application's React components, organized by feature:
+    - **`/pages`**: Top-level components for each main view (e.g., `MainHomePage`, `SettingsPage`).
+    - **`/editors`**: Specialized editor components for templates, prompts, and snippets.
+    - **`/plan` & `/session`**: Components for displaying AI-generated plans and the conversation history.
+    - **`/common`**: Shared components like the command palette and markdown renderers.
+- **`/components/ui`**: The library of low-level, reusable UI components from shadcn/ui.
+- **`/lib/api`**: A collection of strongly-typed functions that handle all HTTP communication with the `backend` API.
+- **`/store`**: Contains all Zustand state management logic, divided into slices for different features (e.g., `session.slice.ts`, `ui.slice.ts`).
+- **`/hooks`**: Custom React hooks, such as those for managing the Monaco editor theme and setup.
+- **`/types`**: Contains all TypeScript type definitions for API payloads and other shared data structures.
+
+---
+
+## AI Studio PowerTools (`userscripts/`)
+
+The userscript that bridges AI Studio with the local backend for the "manual mode" workflow.
+
+### 🚀 Tech Stack & Structure
+- **Language**: TypeScript.
+- **Bundler**: esbuild (`build.js`).
+- **Deployment**: A single bundled `.user.js` file hosted by the `website` and installed via a browser extension like Tampermonkey.
+
+### ✨ Key Files (`userscripts/src`)
+- **`index.ts`**: The main entry point. It initializes all features and connects to the `daemon` to find the active `backend` port.
+- **`webSocketHandler.ts`**: Manages the persistent WebSocket connection to the `backend`'s `/events` gateway to receive commands (e.g., prompts to paste).
+- **`clipboardInterceptor.ts`**: Patches the browser's native clipboard APIs to reliably capture text copied from AI Studio. This is crucial for the "Copy & Submit" workflow.
+- **`hotkeys.ts`**: Binds keyboard shortcuts (e.g., `Cmd+\`) to trigger actions.
+- **Core Actions**:
+    - `copyAndSubmit.ts`: Implements the "Copy & Submit" workflow, which captures the AI's response and sends it to the `backend`.
+    - `pasteAndRun.ts`: Implements the "Paste & Run" workflow, which takes text (from clipboard or WebSocket) and pastes it into the AI Studio prompt input.
+    - `scrollAndCopy.ts`: A helper action that scrolls to the bottom of the AI response and copies it.
+- **`settingsManager.ts` & `settingsUI.ts`**: Create and manage a settings panel injected directly into the AI Studio page.
+
+---
+
+## Daemon Architecture (`daemon/`)
+
+A lightweight, persistent background process that acts as a process manager and authentication proxy.
+
+### 🚀 Tech Stack & Structure
+- **Framework**: Express.js
+- **Process Management**: Uses `pm2` programmatically to manage `backend` instances.
+- **Entry Point**: `src/index.ts`.
+
+### ✨ Key Files (`daemon/src`)
+- **`serviceManager.ts`**: Core logic for interacting with `pm2` (start, stop, etc.).
+- **`stateManager.ts`**: Persists the list of managed services to a JSON file in `~/.repoburg/`.
+- **`auth/authManager.ts`**: Handles JWT validation for securing daemon endpoints.
+- **`api/`**: Contains the Express routers for the daemon's HTTP API (runs on `localhost:9998`).
+
+---
+
+## Website Architecture (`website/`)
+
+The public-facing website for documentation, user accounts, and device authorization.
+
+### 🚀 Tech Stack & Structure
+- **Framework**: Next.js (App Router)
+- **Authentication/Database**: Supabase for user management and a small amount of data storage.
+- **Styling**: Tailwind CSS with shadcn/ui components.
+
+### ✨ Key Directories (`website/src/app`)
+- **`/` (root)**: The main marketing/landing page.
+- **`/dashboard`**: The main page after a user logs in. It handles the device authorization flow.
+- **`/profile`**: Displays user account and subscription details.
+- **`/docs`**: Renders Markdown files from the same directory to serve as product documentation.
+- **`/api/`**: Serverless functions (Next.js Route Handlers) for various tasks:
+    - `/api/device/`: Handles the device authorization flow (`initiate` and `poll`).
+    - `/api/daemon/token`: Generates short-lived JWTs for securing daemon actions from the dashboard.
+    - `/api/version`: A public endpoint to report the latest version of the `repoburg` npm package.
+- **`/auth/callback`**: The OAuth callback route handled by Supabase.
+
+---
+
+## Daemon Desktop App (`daemon-desktop/`)
+
+A graphical user interface for managing the `daemon` and its services.
+
+### 🚀 Tech Stack & Structure
+- **Framework**: Electron with Vite.
+- **UI**: React with shadcn/ui components.
+- **Bundler**: Vite is used for the main, preload, and renderer processes.
+- **Builder**: Electron Forge handles packaging the application for different operating systems.
+
+### ✨ Key Files (`daemon-desktop/src`)
+- **`main.ts`**: The Electron main process entry point. It handles window creation, application lifecycle, and interactions with the `daemon` process.
+- **`preload.ts`**: The Electron preload script, securely exposing functions from the `main` process to the `renderer` process.
+- **`renderer.tsx`**: The entry point for the React application that runs in the Electron window.
+- **`App.tsx`**: The main React component that builds the user interface.
+- **`sharedTypes.ts`**: TypeScript definitions shared between the `main` and `renderer` processes to ensure type safety.
+
+---
+
+## System Interaction Flow
+
+### Authentication & Authorization
+- **Daemon <-> Website**: When a user runs `repoburg start`, the `daemon` initiates a device authorization flow by calling the `/api/device/initiate` endpoint on the `website`. It then polls the `/api/device/poll` endpoint.
+- **User -> Website**: The user is directed to the `/dashboard` page on the `website` to approve the device. Upon approval, the `website` generates a JWT and stores it for the polling `daemon` to retrieve.
+
+### Service Management
+- **Daemon Desktop -> Daemon**: The Electron app's `main.ts` makes HTTP requests to the `daemon`'s API (`localhost:9998`) to start, stop, and list services, effectively acting as a GUI for the daemon's capabilities.
+- **CLI -> Daemon**: The `repoburg` command-line tool also communicates with the `daemon`'s API to manage services.
+- **Daemon -> Userscript**: The `userscript` queries the `daemon`'s `/registry/get-active-port` endpoint to discover which port the active `backend` is running on.
+
+### Core AI Workflow
+- **Backend <-> Frontend**: The `frontend` makes API calls to a specific `backend` instance. It knows the correct port via the `bport` URL query parameter. Real-time updates are sent from backend to frontend via WebSocket.
+- **Backend <-> Userscript**: In manual mode, the `backend` sends `llm-input-generated` events to the `userscript` via WebSocket, telling it to paste a new prompt into AI Studio.
+- **Data from Userscript (HTTP)**: The `userscript` sends the AI's raw response back to the `backend`'s `/llm-responses/submit-external` endpoint.

package/backend/dist/src/seeding/data/context-templates/default-initial_full-project-context.d.ts

@@ -1,2 +1,2 @@
 export declare const template_name = "Default Initial";
-export declare const template_content = "\n\n<%~ await it.tree('--gitignore -I \"node_modules|dist|coverage\"') %>\n\n<%~ it.context_snippets_content %>\n\n<%~ it.adhoc_files_content %>\n\n<%~ it.adhoc_folders_content %>\n\n<%~ it.user_input %>\n\n";
+export declare const template_content = "\n\n<%~ await it.tree('--gitignore -I \"node_modules|dist|coverage\"') %>\n\n\n\n<%~ it.context_snippets_content %>\n\n<%~ it.adhoc_files_content %>\n\n<%~ it.adhoc_folders_content %>\n\nUser Request:\n\n<%~ it.user_input %>\n\n";

package/backend/dist/src/seeding/data/context-templates/default-initial_full-project-context.js

@@ -6,12 +6,16 @@ exports.template_content = `
 
 <%~ await it.tree('--gitignore -I "node_modules|dist|coverage"') %>
 
+
+
 <%~ it.context_snippets_content %>
 
 <%~ it.adhoc_files_content %>
 
 <%~ it.adhoc_folders_content %>
 
+User Request:
+
 <%~ it.user_input %>
 
 `;

package/backend/dist/src/seeding/data/context-templates/default-initial_full-project-context.js.map

@@ -1 +1 @@
-{"version":3,"file":"default-initial_full-project-context.js","sourceRoot":"","sources":["../../../../../src/seeding/data/context-templates/default-initial_full-project-context.ts"],"names":[],"mappings":";;;AAAa,QAAA,aAAa,GAAG,iBAAiB,CAAC;AAClC,QAAA,gBAAgB,GAAG;;;;;;;;;;;;CAY/B,CAAC"}
+{"version":3,"file":"default-initial_full-project-context.js","sourceRoot":"","sources":["../../../../../src/seeding/data/context-templates/default-initial_full-project-context.ts"],"names":[],"mappings":";;;AAAa,QAAA,aAAa,GAAG,iBAAiB,CAAC;AAClC,QAAA,gBAAgB,GAAG;;;;;;;;;;;;;;;;CAgB/B,CAAC"}