MemTensor · CaralHsi · Jan 21, 2026 · Jan 20, 2026 · Jan 20, 2026 · Jan 21, 2026
diff --git a/openwork-memos-integration/CLAUDE.md b/openwork-memos-integration/CLAUDE.md
@@ -0,0 +1,162 @@
+# CLAUDE.md
+
+This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+
+## Project Overview
+
+Openwork is a standalone desktop automation assistant built with Electron. The app hosts a local React UI (bundled via Vite), communicating with the main process through `contextBridge` IPC. The main process spawns the OpenCode CLI (via `node-pty`) to execute user tasks. Users provide their own API key (Anthropic, OpenAI, Google, or xAI) on first launch, stored securely in the OS keychain.
+
+## Common Commands
+
+```bash
+pnpm dev                              # Run desktop app in dev mode (Vite + Electron)
+pnpm dev:clean                        # Dev mode with CLEAN_START=1 (clears stored data)
+pnpm build                            # Build all workspaces
+pnpm build:desktop                    # Build desktop app only
+pnpm lint                             # TypeScript checks
+pnpm typecheck                        # Type validation
+pnpm clean                            # Clean build outputs and node_modules
+pnpm -F @accomplish/desktop test:e2e  # Playwright E2E tests
+pnpm -F @accomplish/desktop test:e2e:ui    # E2E with Playwright UI
+pnpm -F @accomplish/desktop test:e2e:debug # E2E in debug mode
+```
+
+## Architecture
+
+### Monorepo Layout
+```
+apps/desktop/     # Electron app (main/preload/renderer)
+packages/shared/  # Shared TypeScript types
+```
+
+### Desktop App Structure (`apps/desktop/src/`)
+
+**Main Process** (`main/`):
+- `index.ts` - Electron bootstrap, single-instance enforcement, `accomplish://` protocol handler
+- `ipc/handlers.ts` - IPC handlers for task lifecycle, settings, onboarding, API keys
+- `opencode/adapter.ts` - OpenCode CLI wrapper using `node-pty`, streams output and handles permissions
+- `store/secureStorage.ts` - API key storage via `keytar` (OS keychain)
+- `store/appSettings.ts` - App settings via `electron-store` (debug mode, onboarding state)
+- `store/taskHistory.ts` - Task history persistence
+
+**Preload** (`preload/index.ts`):
+- Exposes `window.accomplish` API via `contextBridge`
+- Provides typed IPC methods for task operations, settings, events
+
+**Renderer** (`renderer/`):
+- `main.tsx` - React entry with HashRouter
+- `App.tsx` - Main routing + onboarding gate
+- `pages/` - Home, Execution, History, Settings pages
+- `stores/taskStore.ts` - Zustand store for task/UI state
+- `lib/accomplish.ts` - Typed wrapper for the IPC API
+
+### IPC Communication Flow
+```
+Renderer (React)
+    ↓ window.accomplish.* calls
+Preload (contextBridge)
+    ↓ ipcRenderer.invoke
+Main Process
+    ↓ Native APIs (keytar, node-pty, electron-store)
+    ↑ IPC events
+Preload
+    ↑ ipcRenderer.on callbacks
+Renderer
+```
+
+### Key Dependencies
+- `node-pty` - PTY for OpenCode CLI spawning
+- `keytar` - Secure API key storage (OS keychain)
+- `electron-store` - Local settings/preferences
+- `opencode-ai` - Bundled OpenCode CLI (multi-provider: Anthropic, OpenAI, Google, xAI)
+
+## Code Conventions
+
+- TypeScript everywhere (no JS for app logic)
+- Use `pnpm -F @accomplish/desktop ...` for desktop-specific commands
+- Shared types go in `packages/shared/src/types/`
+- Renderer state via Zustand store actions
+- IPC handlers in `src/main/ipc/handlers.ts` must match `window.accomplish` API in preload
+
+### Image Assets in Renderer
+
+**IMPORTANT:** Always use ES module imports for images in the renderer, never absolute paths.
+
+```typescript
+// CORRECT - Use ES imports
+import logoImage from '/assets/logo.png';
+<img src={logoImage} alt="Logo" />
+
+// WRONG - Absolute paths break in packaged app
+<img src="/assets/logo.png" alt="Logo" />
+```
+
+**Why:** In development, Vite serves `/assets/...` from the public folder. But in the packaged Electron app, the renderer loads via `file://` protocol, and absolute paths like `/assets/logo.png` resolve to the filesystem root instead of the app bundle. ES imports are processed by Vite to use `import.meta.url`, which works correctly in both environments.
+
+Static assets go in `apps/desktop/public/assets/`.
+
+## Environment Variables
+
+- `CLEAN_START=1` - Clear all stored data on app start
+- `E2E_SKIP_AUTH=1` - Skip onboarding flow (for testing)
+
+## Testing
+
+- E2E tests: `pnpm -F @accomplish/desktop test:e2e`
+- Tests use Playwright with serial execution (Electron requirement)
+- Test config: `apps/desktop/playwright.config.ts`
+
+## Bundled Node.js
+
+The packaged app bundles standalone Node.js v20.18.1 binaries to ensure MCP servers work on machines without Node.js installed.
+
+### Key Files
+- `src/main/utils/bundled-node.ts` - Utility to get bundled node/npm/npx paths
+- `scripts/download-nodejs.cjs` - Downloads Node.js binaries for all platforms
+- `scripts/after-pack.cjs` - Copies correct binary into app bundle during build
+
+### CRITICAL: Spawning npx/node in Main Process
+
+**IMPORTANT:** When spawning `npx` or `node` in the main process, you MUST add the bundled Node.js bin directory to PATH. This is because `npx` uses a `#!/usr/bin/env node` shebang which looks for `node` in PATH.
+
+```typescript
+import { spawn } from 'child_process';
+import { getNpxPath, getBundledNodePaths } from '../utils/bundled-node';
+
+// Get bundled paths
+const npxPath = getNpxPath();
+const bundledPaths = getBundledNodePaths();
+
+// Build environment with bundled node in PATH
+let spawnEnv: NodeJS.ProcessEnv = { ...process.env };
+if (bundledPaths) {
+  const delimiter = process.platform === 'win32' ? ';' : ':';
+  spawnEnv.PATH = `${bundledPaths.binDir}${delimiter}${process.env.PATH || ''}`;
+}
+
+// Spawn with the modified environment
+spawn(npxPath, ['-y', 'some-package@latest'], {
+  stdio: ['pipe', 'pipe', 'pipe'],
+  env: spawnEnv,
+});
+```
+
+**Why:** Without adding `bundledPaths.binDir` to PATH, the spawned process will fail with exit code 127 ("node not found") on machines that don't have Node.js installed system-wide.
+
+### For MCP Server Configs
+
+When generating MCP server configurations, pass `NODE_BIN_PATH` in the environment so spawned servers can add it to their PATH:
+
+```typescript
+environment: {
+  NODE_BIN_PATH: bundledPaths?.binDir || '',
+}
+```
+
+## Key Behaviors
+
+- Single-instance enforcement - second instance focuses existing window
+- API keys stored in OS keychain (macOS Keychain, Windows Credential Vault, Linux Secret Service)
+- API key validation via test request to respective provider API
+- OpenCode CLI permissions are bridged to UI via IPC `permission:request` / `permission:respond`
+- Task output streams through `task:update` and `task:progress` IPC events
diff --git a/openwork-memos-integration/CONTRIBUTING.md b/openwork-memos-integration/CONTRIBUTING.md
@@ -0,0 +1,60 @@
+# Contributing to Openwork
+
+Thank you for your interest in contributing to Openwork! This document provides guidelines and instructions for contributing.
+
+## Getting Started
+
+1. Fork the repository
+2. Clone your fork: `git clone https://github.com/YOUR_USERNAME/openwork.git`
+3. Install dependencies: `pnpm install`
+4. Create a branch: `git checkout -b feature/your-feature-name`
+
+## Development
+
+```bash
+pnpm dev          # Run the desktop app in development mode
+pnpm build        # Build all workspaces
+pnpm typecheck    # Run TypeScript checks
+pnpm lint         # Run linting
+```
+
+## Code Style
+
+- TypeScript for all application code
+- Follow existing patterns in the codebase
+- Use meaningful variable and function names
+- Keep functions focused and small
+
+## Pull Request Process
+
+1. Ensure your code builds without errors (`pnpm build`)
+2. Run type checking (`pnpm typecheck`)
+3. Update documentation if needed
+4. Write a clear PR description explaining:
+   - What the change does
+   - Why it's needed
+   - How to test it
+
+## Commit Messages
+
+Use clear, descriptive commit messages:
+- `feat: add dark mode support`
+- `fix: resolve crash on startup`
+- `docs: update README with new instructions`
+- `refactor: simplify task queue logic`
+
+## Reporting Issues
+
+When reporting issues, please include:
+- OS and version
+- Steps to reproduce
+- Expected vs actual behavior
+- Any error messages or logs
+
+## Security
+
+If you discover a security vulnerability, please see [SECURITY.md](SECURITY.md) for responsible disclosure guidelines.
+
+## License
+
+By contributing, you agree that your contributions will be licensed under the MIT License.
diff --git a/openwork-memos-integration/LICENSE b/openwork-memos-integration/LICENSE
@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Accomplish Inc
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.