dkarasiewicz · dkarasiewicz · Feb 2, 2026 · Jan 24, 2026 · Feb 2, 2026 · Feb 2, 2026
diff --git a/.env.example b/.env.example
@@ -24,6 +24,13 @@ SESSION_SECRET=your_session_secret
 SESSION_SECURE=false
 SESSION_SAME_SITE=lax
 
+# App URLs
+APP_URL=http://localhost:3000
+FRONTEND_URL=http://localhost:2211
+
+# Integration encryption
+INTEGRATION_ENCRYPTION_KEY=your_64_char_hex_key
+
 # CORS
 CORS_ENABLED=true
 CORS_ORIGIN=http://localhost:2211,*
@@ -66,3 +73,26 @@ LANGSMITH_PROJECT="Launchline"
 #Customer-ui
 NEXT_PUBLIC_API_URL=http://localhost:2211
 NEXT_PUBLIC_CORE_API_URL=http://localhost:3000
+
+# Linear Integration
+LINEAR_CLIENT_ID=
+LINEAR_CLIENT_SECRET=
+LINEAR_WEBHOOK_SECRET=
+
+# Slack Integration
+SLACK_CLIENT_ID=
+SLACK_CLIENT_SECRET=
+SLACK_SIGNING_SECRET=
+
+# Google Integration
+GOOGLE_CLIENT_ID=
+GOOGLE_CLIENT_SECRET=
+
+# GitHub Integration
+GITHUB_CLIENT_ID=your_github_client_id
+GITHUB_CLIENT_SECRET=your_github_client_secret
+GITHUB_WEBHOOK_SECRET=your_github_webhook_secret
+# GitHub App (preferred)
+GITHUB_APP_ID=your_github_app_id
+GITHUB_APP_SLUG=your_github_app_slug
+GITHUB_APP_PRIVATE_KEY=your_github_app_private_key
diff --git a/README.md b/README.md
@@ -2,294 +2,77 @@
 
 **Transparency without micromanagement. Impact without fake KPIs.**
 
-Launchline helps teams see what's *actually* happening - not what fits in spreadsheets.
+Launchline is an AI execution inbox for product teams. It turns signals from Linear, GitHub, and Slack into clear, actionable context so PMs can see what is actually happening without surveillance or vanity metrics.
 
----
+## Why Launchline
 
-## Why Launchline?
+Most teams do not lack effort. They lack shared context.
 
-Most teams waste resources not because people aren't working, but because **context is invisible**:
+- Dashboards show tickets closed, but miss blockers and invisible work.
+- Metrics reward activity, not impact.
+- One-size KPIs punish deep work and collaboration.
 
-- A developer who "closes fewer tickets" might be preventing production fires
-- Someone who writes less code might be unlocking others through great design
-- A PM who doesn't "ship features" might be keeping the team aligned
+Launchline focuses on reality: what is stuck, what is drifting, and who is unblocking the team.
 
-### The problem with traditional tracking
+## What you can demo today
 
-**Micromanagement metrics** (hours, commits, messages) → fake productivity  
-**Surface-level dashboards** (tickets closed) → miss the real story  
-**One-size-fits-all KPIs** → punish different working styles
+- **Execution Inbox** with auto-generated items after Linear connect
+- **Linea agent** that explains blockers, drift, and hidden impact
+- **Workspace-aware prompts** so each workspace can tune Linea
+- **Human-in-the-loop actions** (Linear updates, Slack messages, GitHub issues)
+- **Slack interaction** so teams can talk to Linea outside the web UI
 
-Some people thrive on daily increments. Others need deep focus and moments of inspiration. Traditional tools force everyone into the same mold - and punish those who don't fit.
+## Demo flow (5 minutes)
 
-### What Launchline does differently
+1. **Connect Linear** (Settings -> Connect Linear)
+2. **Show inbox items** (blockers, stalled work, unassigned priorities)
+3. **Ask Linea for sprint status** (suggestion prompt)
+4. **Show hidden impact** ("What has Sarah been doing?")
+5. **Generate a project update** (stakeholder-ready summary)
+6. **Optional: send a Slack update** from Linea
 
-Launchline is an **AI-augmented execution platform** that:
+## How it works
 
-- **Surfaces hidden impact** - code reviews, mentoring, firefighting, unblocking others
-- **Respects context** - understands *why* work is slow, not just *that* it is
-- **Embraces different styles** - recognizes value that doesn't show up in Jira
-- **Increases transparency** - gives managers clarity without surveillance
-- **Keeps it fair** - respects people who do their job, highlights those who go beyond
-
-We collect signals across your tools (Linear, GitHub, Slack), turn them into insights, and help you understand:
-
-- Where resources are actually going
-- What blockers exist *before* they derail your roadmap
-- How each team member's strengths can be better utilized
-- Which small actions have the biggest impact on your product
-
----
-
-## The vision
-
-### Today: Execution inbox
-
-An AI-powered PM inbox that surfaces blockers, priority drift, and decisions across tools.
-
-### Next: Intelligent resource allocation
-
-- **Predict blockers** before they happen (ML models + platform signals)
-- **Recommend work distribution** based on team strengths and historical patterns
-- **Show broader context** - what founders miss while focused on immediate priorities
-
-### Eventually: Impact transparency for everyone
-
-- **For developers**: See how your work shapes the product, even when it's not "shipping features"
-- **For teams**: Highlight underdeveloped areas, frequent pain points, customer impact zones
-- **For organizations**: Understand how small actions compound into outcomes
-
-We believe teams should organize around people's strengths - not force people into arbitrary processes.
-
----
-
-## Features
-
-- **PM Inbox**
-  - One place for blockers, priority drift, and project update opportunities
-- **Generative summaries**
-  - Human-readable explanations of context across Linear, GitHub, Slack
-- **Suggested actions**
-  - Structured, user-approved actions (update Linear, comment on GitHub, notify via Slack)
-- **Conversational threads**
-  - Chat-style interface for each Inbox item, powered by AI agents
-- **Tool integrations**
-  - Current: Linear, GitHub, Slack
-  - Planned: Notion, Jira, Figma, feedback tools
-
----
-
-## The bigger picture
-
-Product work is becoming too complex for humans alone.
-
-Modern products are built across dozens of tools, teams, and decisions. PMs are expected to keep everything aligned - but the system itself doesn't learn.
-
-Launchline is building the missing layer: a **product copilot** that understands context, history, and tradeoffs - not just tickets.
-
-### Execution → Memory → Copilot
-
-**Execution inbox**: Captures blockers, risks, and decisions across tools  
-**Product memory**: Understands how your team, product, and users behave over time  
-**Product copilot**: Helps steer priorities and tradeoffs - grounded in reality
-
-We start where the pain is highest: **execution**. Inbox → decisions → unblock → ship.
-
----
-
-## Architecture (high level)
-
-Signals flow through the system as follows:
-
-```text
-Signals (webhooks / SDK events)
-↓
-PostgreSQL (structured event store)
-↓
-LangGraph (memory + semantic relationships)
-↓
-Rule engine (blocker / drift / staleness detection)
-↓
-Inbox items
-↓
-Assistant UI + DeepAgent (chat + reasoning)
-↓
-Tool calls (user‑approved execution)
+```
+Signals (webhooks, SDK events)
+  -> PostgreSQL (event store)
+  -> LangGraph (memory + relationships)
+  -> Rules + LLM analysis
+  -> Inbox items
+  -> Linea agent + tool calls
 ```
 
 Key components:
 
-- **Backend**: Nest.js / Express (TypeScript) REST APIs and background workers.
-- **Frontend**: Next.js + React + Shadcn UI.
-- **Storage**: PostgreSQL for structured data, Redis for caching/rate limits.
-- **Queueing**: RabbitMQ (optional) for batched async jobs.
-- **AI layer**: LangGraph + LangChain DeepAgent for reasoning and summaries.
-
----
-
-## Open‑core model & licensing
-
-Launchline is **open‑core** and **self‑hostable**.
-
-- **Core application** (server, UI, agents, prompts, graphs, workflows)
-  - Licensed under **Business Source License 1\.1 (BSL 1\.1)** with a *no competing hosted service* restriction.
-  - See `LICENSE`.
-
-- **SDKs and client libraries** (TypeScript / JavaScript)
-  - Licensed under **MIT** for maximum adoption.
-  - See the `LICENSE` file inside each SDK package (for example `packages/sdk`).
-
-You can:
+- **Backend**: NestJS (REST + GraphQL), background workers
+- **Frontend**: Next.js + Assistant UI
+- **Storage**: Postgres + Redis
+- **AI layer**: LangGraph + LangChain + DeepAgents
 
-- Audit and self‑host the full platform.
-- Use the SDKs in commercial and proprietary applications.
-- Not offer Launchline (or a substantially similar service) as a competing hosted service.
+## Local development
 
----
-
-## Environment configuration
-
-Before running the application (locally or with Docker), copy `.env.example` to `.env` in the repo root and fill in the required environment variables.  
-**Do not commit real secrets or credentials.**  
-See `.env` for the full list of required variables (database, cache, API keys, etc).
-
----
-
-## Self‑hosting with `docker‑compose`
-
-### Prerequisites
-
-- Docker
-- Docker Compose
-- A `.env` file in the repo root (see above).
-
-### Start the stack
-
-From the repository root:
+1. Copy `.env.example` to `.env` and fill required values.
+2. Start dependencies:
 
 ```bash
 docker-compose up -d
 ```
 
-This will start **only the development dependencies/services** needed for local development:
-
-- PostgreSQL (and Redis / RabbitMQ if configured)
-
-> The full local production-ready stack (including backend and frontend containers) will be documented later.
-
-### Access
-
-- UI: `http://localhost:3000` (or the port from `LAUNCHLINE_PORT`)
-- API: `http://localhost:3000/api` (or your configured base path)
-
-You can now connect Linear, GitHub, and Slack, then start seeing Inbox items for blockers, drift, and updates.
-
----
-
-## Using the TypeScript / JavaScript SDK
-
-The SDK is MIT‑licensed and provides a thin client for calling the Launchline API.
-
-Install from npm:
-
-```bash
-npm install @launchline/sdk
-# or
-yarn add @launchline/sdk
-# or
-pnpm add @launchline/sdk
-```
-
-Basic usage:
-
-```ts
-import { LaunchlineClient } from '@launchline/sdk';
-
-const client = new LaunchlineClient({
-  baseUrl: 'http://localhost:3000',
-  apiKey: process.env.LAUNCHLINE_API_KEY,
-});
-
-async function main() {
-  const result = await client.agents.run({
-    agentId: 'my-agent-id',
-    input: { message: 'Summarize current blockers' },
-  });
-
-  console.log(result);
-}
-
-main().catch(console.error);
-```
-
-See the SDK package `README` for full API documentation and examples.
-
----
-
-## Local development (without Docker)
-
-1. Install dependencies:
+3. Start the stack (from repo root):
 
 ```bash
-npm install
-# or
-yarn install
-# or
-pnpm install
-```
-
-2. Ensure your local services (PostgreSQL, Redis, RabbitMQ) are running.  
-   You can use `docker-compose up -d` to start these dependencies.
-
-3. Create and configure your `.env` file as described above.
-
-4. Run database migrations:
-
-```bash
-pnpm nx migrate-run core
-```
-
-5. Start dev servers:
-
-```bash
-# Backend API (with HMR)
 pnpm nx serve-hmr core
-
-# Frontend (customer UI)
-pnpm nx start customer-ui -p 2201
+pnpm nx dev customer-ui
 ```
 
----
-
-## Contributing
-
-Issues and pull requests are welcome. The community can shape the roadmap - thoughtful contributions are encouraged.
-
-For contribution and collaboration guidelines (licensing, code review, PR expectations, triage), see `./CONTRIBUTING.md`.
-
-By contributing, you agree that:
-
-- Changes to the core application are licensed under **BSL 1.1**.
-- Changes to SDKs and libraries follow the license of that package (usually **MIT**).
-
-We believe PM tools should be auditable, extensible, and community-owned.
-
----
+UI: `http://localhost:4200`
+API: `http://localhost:3000/graphql`
 
 ## License
 
-- Core application, prompts, graphs, and workflows: **Business Source License 1\.1 (BSL 1\.1)** with a *no competing hosted service* restriction. See `LICENSE`.
-- SDKs and client libraries: **MIT**. See each package\-specific `LICENSE`.
-
----
-
-## Third-Party Services
-
-### Analytics & Notifications
-
-This application currently uses [PostHog](https://posthog.com) for:
-- **Analytics**: User behavior tracking and product analytics
-- **OTP Email Delivery**: One-time password emails for authentication
+Launchline is open-core and self-hostable.
 
-**Note**: We plan to add support for custom SNS (Simple Notification Service) configurations in the future, allowing you to use your own email delivery service. For now, PostHog handles both analytics and transactional emails.
+- **Core platform**: Business Source License 1.1 (no competing hosted service)
+- **SDKs and client libraries**: MIT
 
+See `LICENSE.txt` for details.