@cryptiklemur/lattice 0.0.0

package/.editorconfig

@@ -0,0 +1,12 @@
+root = true
+
+[*]
+indent_style = space
+indent_size = 2
+end_of_line = lf
+charset = utf-8
+trim_trailing_whitespace = true
+insert_final_newline = true
+
+[*.md]
+trim_trailing_whitespace = false

package/.github/workflows/release.yml

@@ -0,0 +1,44 @@
+name: Release
+
+on:
+  push:
+    branches:
+      - main
+
+permissions:
+  contents: write
+  issues: write
+  pull-requests: write
+  id-token: write
+
+jobs:
+  release:
+    name: Release
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Setup Bun
+        uses: oven-sh/setup-bun@v2
+        with:
+          bun-version: latest
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 22
+          registry-url: https://registry.npmjs.org
+
+      - name: Install dependencies
+        run: bun install --frozen-lockfile
+
+      - name: Build
+        run: bun run build
+
+      - name: Release
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: npx semantic-release

package/.impeccable.md

@@ -0,0 +1,66 @@
+# Lattice Design Context
+
+## Users
+Single developer managing Claude Code across multiple machines. They're power users who value efficiency, keyboard shortcuts, and information density. They interact with Lattice as a command center — monitoring sessions, browsing files, running terminals, and chatting with Claude across their fleet of nodes.
+
+## Brand Personality
+**Precise. Technical. Calm.**
+
+Lattice is a quiet authority — confident without being loud, technical without being intimidating. It respects the developer's attention and gets out of the way. Every pixel earns its place.
+
+## Emotional Goals
+- **Control & Mastery**: "I have my entire fleet at my fingertips." The interface should communicate that the user is in command — clear status, predictable behavior, immediate feedback.
+- **Trust & Reliability**: "I can depend on this." Stability over novelty. Consistent patterns. No surprises. Professional confidence in every interaction.
+
+## Aesthetic Direction
+- **Dark-first**: Deep, low-chroma backgrounds with precise accent colors. Light themes available but dark is the native habitat.
+- **Monospace DNA**: JetBrains Mono for headings and emphasis gives Lattice its terminal-rooted identity. IBM Plex Sans for readable body text.
+- **Topological motif**: The lattice grid (dot-grid backgrounds, node connection lines, the 2x2 logomark) is the recurring visual thread.
+- **Three surface tiers**: Chrome (sidebar/headers, `base-200`), Stage (chat area, `base-100` with dot-grid), Elevated (panels/modals, `base-300` with shadow).
+- **OKLCH color space**: Perceptually consistent colors across all 23 base16 themes.
+- **Utilitarian density**: Information-rich without clutter. Compact spacing, small type sizes, efficient use of space.
+
+## Anti-patterns
+- No gratuitous animations or transitions — motion serves function only
+- No rounded-everything bubbly aesthetic — keep edges intentional
+- No pastel-heavy palettes in dark mode — maintain contrast authority
+- No emoji icons — lucide-react only
+- No "AI slop" aesthetics — avoid generic Inter/purple-gradient patterns
+
+## Design Principles
+
+1. **Earn every pixel**: Nothing decorative without function. If an element doesn't help the user understand state, take action, or navigate, remove it.
+2. **Quiet confidence**: The interface communicates competence through consistency and precision, not through visual loudness or novelty.
+3. **State is sacred**: Connection status, session state, node health — these must be instantly legible. Use color, position, and subtle animation to make state changes unmissable without being alarming.
+4. **Dense but breathable**: Pack information efficiently but maintain clear visual hierarchy through type scale, opacity, and spacing — not through excessive whitespace.
+5. **Theme-native**: Never hardcode colors. Every visual decision flows through CSS variables and the active base16 theme. A component should look correct in all 23 themes without special-casing.
+
+## Accessibility Requirements
+- **WCAG AA** minimum contrast ratios
+- **Reduced motion**: Respect `prefers-reduced-motion` — disable non-essential animations, keep functional transitions minimal
+- **High contrast**: Support a dedicated high-contrast theme option for low-vision users
+- **Color blind safe**: Status indicators (online/offline, success/error/warning) must be distinguishable without relying on hue alone — use shape, icon, or label as secondary signal
+- **Mobile & responsive**: Support touch targets, responsive layouts, and gesture navigation for tablet/mobile use
+- **Keyboard-first**: All actions reachable via keyboard; visible focus indicators
+
+## Typography Scale
+| Role | Font | Size | Weight | Tracking |
+|------|------|------|--------|----------|
+| Section label | JetBrains Mono | 11-12px | Bold | wider/widest, uppercase |
+| Body text | IBM Plex Sans | 14px | Regular | normal |
+| Secondary text | IBM Plex Sans | 13px | Regular | normal |
+| Muted/hint | IBM Plex Sans | 11px | Regular | normal |
+| Code/terminal | JetBrains Mono | 14px | Regular | normal |
+| Heading emphasis | JetBrains Mono | 17px | Bold | normal |
+
+## Spacing Patterns
+- Standard padding: `px-4`, `py-2.5`, `gap-2`-`gap-3`
+- Compact list items: `px-3`, `py-1.5`
+- Input fields: `px-3`, `py-2.5`, `rounded-xl`
+- Section spacing: `pt-4`, `pb-2`
+
+## Component Patterns
+- **Buttons**: daisyUI `btn` with ghost/primary/accent variants. Icon buttons use `btn-ghost btn-xs btn-square`.
+- **Inputs**: `bg-base-300 border border-base-content/15 rounded-xl`, focus: `border-primary`
+- **Opacity hierarchy**: `/70` secondary, `/40` muted labels, `/30` hints, `/15`-`/20` borders
+- **Surfaces**: Three tiers — chrome (`base-200`), stage (`base-100` + dot-grid), elevated (`base-300` + shadow)

package/.releaserc.json

@@ -0,0 +1,32 @@
+{
+  "branches": [
+    "main",
+    {
+      "name": "alpha",
+      "prerelease": true
+    }
+  ],
+  "plugins": [
+    [
+      "@semantic-release/commit-analyzer",
+      {
+        "preset": "angular"
+      }
+    ],
+    [
+      "@semantic-release/release-notes-generator",
+      {
+        "preset": "angular"
+      }
+    ],
+    [
+      "@semantic-release/npm",
+      {
+        "pkgRoot": "."
+      }
+    ],
+    [
+      "@semantic-release/github"
+    ]
+  ]
+}

package/.serena/project.yml

@@ -0,0 +1,138 @@
+# the name by which the project can be referenced within Serena
+project_name: "lattice"
+
+
+# list of languages for which language servers are started; choose from:
+#   al                  bash                clojure             cpp                 csharp
+#   csharp_omnisharp    dart                elixir              elm                 erlang
+#   fortran             fsharp              go                  groovy              haskell
+#   java                julia               kotlin              lua                 markdown
+#   matlab              nix                 pascal              perl                php
+#   php_phpactor        powershell          python              python_jedi         r
+#   rego                ruby                ruby_solargraph     rust                scala
+#   swift               terraform           toml                typescript          typescript_vts
+#   vue                 yaml                zig
+#   (This list may be outdated. For the current list, see values of Language enum here:
+#   https://github.com/oraios/serena/blob/main/src/solidlsp/ls_config.py
+#   For some languages, there are alternative language servers, e.g. csharp_omnisharp, ruby_solargraph.)
+# Note:
+#   - For C, use cpp
+#   - For JavaScript, use typescript
+#   - For Free Pascal/Lazarus, use pascal
+# Special requirements:
+#   Some languages require additional setup/installations.
+#   See here for details: https://oraios.github.io/serena/01-about/020_programming-languages.html#language-servers
+# When using multiple languages, the first language server that supports a given file will be used for that file.
+# The first language is the default language and the respective language server will be used as a fallback.
+# Note that when using the JetBrains backend, language servers are not used and this list is correspondingly ignored.
+languages:
+- typescript
+
+# the encoding used by text files in the project
+# For a list of possible encodings, see https://docs.python.org/3.11/library/codecs.html#standard-encodings
+encoding: "utf-8"
+
+# line ending convention to use when writing source files.
+# Possible values: unset (use global setting), "lf", "crlf", or "native" (platform default)
+# This does not affect Serena's own files (e.g. memories and configuration files), which always use native line endings.
+line_ending:
+
+# The language backend to use for this project.
+# If not set, the global setting from serena_config.yml is used.
+# Valid values: LSP, JetBrains
+# Note: the backend is fixed at startup. If a project with a different backend
+# is activated post-init, an error will be returned.
+language_backend:
+
+# whether to use project's .gitignore files to ignore files
+ignore_all_files_in_gitignore: true
+
+# list of additional paths to ignore in this project.
+# Same syntax as gitignore, so you can use * and **.
+# Note: global ignored_paths from serena_config.yml are also applied additively.
+ignored_paths: []
+
+# whether the project is in read-only mode
+# If set to true, all editing tools will be disabled and attempts to use them will result in an error
+# Added on 2025-04-18
+read_only: false
+
+# list of tool names to exclude.
+# This extends the existing exclusions (e.g. from the global configuration)
+#
+# Below is the complete list of tools for convenience.
+# To make sure you have the latest list of tools, and to view their descriptions, 
+# execute `uv run scripts/print_tool_overview.py`.
+#
+#  * `activate_project`: Activates a project by name.
+#  * `check_onboarding_performed`: Checks whether project onboarding was already performed.
+#  * `create_text_file`: Creates/overwrites a file in the project directory.
+#  * `delete_lines`: Deletes a range of lines within a file.
+#  * `delete_memory`: Deletes a memory from Serena's project-specific memory store.
+#  * `execute_shell_command`: Executes a shell command.
+#  * `find_referencing_code_snippets`: Finds code snippets in which the symbol at the given location is referenced.
+#  * `find_referencing_symbols`: Finds symbols that reference the symbol at the given location (optionally filtered by type).
+#  * `find_symbol`: Performs a global (or local) search for symbols with/containing a given name/substring (optionally filtered by type).
+#  * `get_current_config`: Prints the current configuration of the agent, including the active and available projects, tools, contexts, and modes.
+#  * `get_symbols_overview`: Gets an overview of the top-level symbols defined in a given file.
+#  * `initial_instructions`: Gets the initial instructions for the current project.
+#     Should only be used in settings where the system prompt cannot be set,
+#     e.g. in clients you have no control over, like Claude Desktop.
+#  * `insert_after_symbol`: Inserts content after the end of the definition of a given symbol.
+#  * `insert_at_line`: Inserts content at a given line in a file.
+#  * `insert_before_symbol`: Inserts content before the beginning of the definition of a given symbol.
+#  * `list_dir`: Lists files and directories in the given directory (optionally with recursion).
+#  * `list_memories`: Lists memories in Serena's project-specific memory store.
+#  * `onboarding`: Performs onboarding (identifying the project structure and essential tasks, e.g. for testing or building).
+#  * `prepare_for_new_conversation`: Provides instructions for preparing for a new conversation (in order to continue with the necessary context).
+#  * `read_file`: Reads a file within the project directory.
+#  * `read_memory`: Reads the memory with the given name from Serena's project-specific memory store.
+#  * `remove_project`: Removes a project from the Serena configuration.
+#  * `replace_lines`: Replaces a range of lines within a file with new content.
+#  * `replace_symbol_body`: Replaces the full definition of a symbol.
+#  * `restart_language_server`: Restarts the language server, may be necessary when edits not through Serena happen.
+#  * `search_for_pattern`: Performs a search for a pattern in the project.
+#  * `summarize_changes`: Provides instructions for summarizing the changes made to the codebase.
+#  * `switch_modes`: Activates modes by providing a list of their names
+#  * `think_about_collected_information`: Thinking tool for pondering the completeness of collected information.
+#  * `think_about_task_adherence`: Thinking tool for determining whether the agent is still on track with the current task.
+#  * `think_about_whether_you_are_done`: Thinking tool for determining whether the task is truly completed.
+#  * `write_memory`: Writes a named memory (for future reference) to Serena's project-specific memory store.
+excluded_tools: []
+
+# list of tools to include that would otherwise be disabled (particularly optional tools that are disabled by default).
+# This extends the existing inclusions (e.g. from the global configuration).
+included_optional_tools: []
+
+# fixed set of tools to use as the base tool set (if non-empty), replacing Serena's default set of tools.
+# This cannot be combined with non-empty excluded_tools or included_optional_tools.
+fixed_tools: []
+
+# list of mode names to that are always to be included in the set of active modes
+# The full set of modes to be activated is base_modes + default_modes.
+# If the setting is undefined, the base_modes from the global configuration (serena_config.yml) apply.
+# Otherwise, this setting overrides the global configuration.
+# Set this to [] to disable base modes for this project.
+# Set this to a list of mode names to always include the respective modes for this project.
+base_modes:
+
+# list of mode names that are to be activated by default.
+# The full set of modes to be activated is base_modes + default_modes.
+# If the setting is undefined, the default_modes from the global configuration (serena_config.yml) apply.
+# Otherwise, this overrides the setting from the global configuration (serena_config.yml).
+# This setting can, in turn, be overridden by CLI parameters (--mode).
+default_modes:
+
+# initial prompt for the project. It will always be given to the LLM upon activating the project
+# (contrary to the memories, which are loaded on demand).
+initial_prompt: ""
+
+# time budget (seconds) per tool call for the retrieval of additional symbol information
+# such as docstrings or parameter information.
+# This overrides the corresponding setting in the global configuration; see the documentation there.
+# If null or missing, use the setting from the global configuration.
+symbol_info_budget:
+
+# list of regex patterns which, when matched, mark a memory entry as read‑only.
+# Extends the list from the global configuration, merging the two lists.
+read_only_memory_patterns: []

package/CLAUDE.md

@@ -0,0 +1,35 @@
+# Lattice — Project Rules
+
+## Icons
+- Use `lucide-react` for ALL icons. Never write custom/inline SVG icons.
+- Import icons individually: `import { Settings, Moon, Sun } from "lucide-react"`
+
+## Coding Standards
+- Use `var` instead of `const`/`let`. No arrow functions.
+- Server-side: ESM with Bun. Client-side: ESM with Vite + React.
+- No emojis for icons or in UI.
+- No section separator comments or organizational comments.
+- One class per file.
+- Follow .editorconfig (2-space indent, LF, UTF-8).
+
+## Git
+- Never add "Co-Authored-By" lines mentioning Claude/AI.
+- Commit messages follow Angular Commit Convention.
+- Only commit when explicitly asked.
+
+## Development
+- Use `bun run dev` to start the development server — it hot reloads both the server and the web app automatically. No manual restart needed after code changes.
+
+## Pre-existing Errors
+- DO NOT EVER LEAVE PRE-EXISTING ERRORS, FIX THEM.
+
+## Design Context
+See `.impeccable.md` for comprehensive design guidelines. Key principles:
+- **Personality**: Precise, Technical, Calm — quiet authority, no fluff
+- **Emotions**: Control & Mastery, Trust & Reliability
+- **Dark-first** with 23 base16 themes via OKLCH color space
+- **Typography**: JetBrains Mono (headings/code), IBM Plex Sans (body)
+- **Three surface tiers**: Chrome (base-200), Stage (base-100 + dot-grid), Elevated (base-300 + shadow)
+- **Design principles**: Earn every pixel, quiet confidence, state is sacred, dense but breathable, theme-native
+- **Accessibility**: WCAG AA, reduced motion, high contrast, color blind safe, mobile/responsive, keyboard-first
+- **Anti-patterns**: No gratuitous animation, no emoji icons, no hardcoded colors, no "AI slop" aesthetics

package/CONTRIBUTING.md

@@ -0,0 +1,93 @@
+# Contributing to Lattice
+
+Thanks for your interest in contributing to Lattice! This document covers the basics you need to get started.
+
+## Development Setup
+
+### Prerequisites
+
+- [Bun](https://bun.sh/) v1.1+
+- Node.js 20+ (for some tooling)
+- Git
+
+### Getting Started
+
+```bash
+git clone https://github.com/cryptiklemur/lattice.git
+cd lattice
+bun install
+bun run dev
+```
+
+The dev server starts on `http://localhost:7654` with hot reload for both server and client.
+
+### Project Structure
+
+```
+lattice/
+  shared/    # Shared TypeScript types and message definitions
+  server/    # Bun server — WebSocket handlers, session management, mesh networking
+  client/    # React + Vite client — dashboard, settings, chat UI
+```
+
+## Development Workflow
+
+### Coding Standards
+
+- Use `var` instead of `const`/`let`
+- No arrow functions — use `function` keyword
+- Use `lucide-react` for all icons
+- Follow `.editorconfig` (2-space indent, LF line endings, UTF-8)
+- One class per file
+
+### Commit Messages
+
+We follow [Angular Commit Message Conventions](https://github.com/angular/angular/blob/main/CONTRIBUTING.md#-commit-message-format):
+
+```
+<type>(<scope>): <short summary>
+```
+
+**Types:** `feat`, `fix`, `refactor`, `docs`, `style`, `test`, `chore`, `ci`
+
+**Scopes:** `client`, `server`, `shared`, or omit for cross-cutting changes
+
+**Examples:**
+```
+feat(client): add skill marketplace search
+fix(server): use correct node identity for project list
+refactor(shared): extract MCP form components
+```
+
+### Building
+
+```bash
+bun run build        # Build all packages
+bun run typecheck    # Type-check without emitting
+```
+
+### Testing Changes
+
+1. Run the dev server: `bun run dev`
+2. Open `http://localhost:7654` in your browser
+3. Verify your changes work visually
+
+## Pull Requests
+
+1. Fork the repo and create a branch from `main`
+2. Make your changes following the coding standards above
+3. Ensure the project builds without errors: `bun run build`
+4. Write a clear PR description explaining what changed and why
+5. Submit your PR
+
+## Reporting Issues
+
+Use [GitHub Issues](https://github.com/cryptiklemur/lattice/issues) to report bugs or suggest features. Include:
+
+- Steps to reproduce (for bugs)
+- Expected vs actual behavior
+- Your environment (OS, Bun version, browser)
+
+## License
+
+By contributing, you agree that your contributions will be licensed under the [MIT License](LICENSE).

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Aaron Scherer
+
+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.

package/README.md

@@ -0,0 +1,83 @@
+# Lattice
+
+Multi-machine agentic dashboard for Claude Code. Monitor sessions, manage MCP servers and skills, orchestrate across mesh-networked nodes.
+
+> **Alpha** — Lattice is under active development. APIs and features may change.
+
+## What is Lattice?
+
+Lattice is a web dashboard that sits alongside your Claude Code sessions. It gives you a unified view across projects, machines, and sessions — with real-time monitoring, configuration management, and a skill marketplace.
+
+### Features
+
+- **Multi-project dashboard** — See recent sessions across all projects at a glance, jump back into any conversation
+- **MCP server management** — Add, edit, and remove MCP servers at global or project level through a visual editor
+- **Skill marketplace** — Search and install skills from [skills.sh](https://skills.sh), manage installed skills with rendered markdown previews
+- **Mesh networking** — Connect multiple machines into a mesh network, see node status and project distribution
+- **Session management** — Browse, rename, delete, and resume Claude Code sessions per project
+- **Real-time chat** — Send messages, approve tool use, monitor context usage and costs
+- **Theme system** — 23 base16 themes (dark and light) with OKLCH color space
+- **Configuration editor** — Edit CLAUDE.md, environment variables, rules, and permissions through the UI
+
+## Quick Start
+
+### Install
+
+```bash
+# With npm
+npm install -g lattice-ai
+
+# With bun
+bun install -g lattice-ai
+```
+
+### Run
+
+```bash
+lattice
+```
+
+Opens the dashboard at `http://localhost:7654`. Add projects through the UI or by navigating to a directory with a `CLAUDE.md` file.
+
+### Development
+
+```bash
+git clone https://github.com/cryptiklemur/lattice.git
+cd lattice
+bun install
+bun run dev
+```
+
+## Architecture
+
+Lattice is a monorepo with three packages:
+
+| Package | Description |
+|---------|------------|
+| `shared/` | TypeScript types, message definitions, constants |
+| `server/` | Bun WebSocket server — handlers, session management, mesh networking |
+| `client/` | React + Vite dashboard — UI components, state management, themes |
+
+The server communicates with clients via WebSocket using a typed message protocol defined in `shared/`. Sessions are managed through the Claude Agent SDK. The client uses Tanstack Store for state management and Tanstack Router for routing.
+
+## Configuration
+
+Lattice stores its config at `~/.lattice/config.json`. Global Claude settings are read from `~/.claude/` and `~/.claude.json`.
+
+| Path | Purpose |
+|------|---------|
+| `~/.lattice/config.json` | Lattice daemon config (port, name, TLS, projects) |
+| `~/.claude/CLAUDE.md` | Global Claude instructions |
+| `~/.claude.json` | Global MCP server configuration |
+| `~/.claude/skills/` | Global skills directory |
+| `~/.claude/rules/` | Global rules |
+
+Project-level settings are stored in each project's `.claude/` directory and `.mcp.json`.
+
+## Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for development setup, coding standards, and pull request guidelines.
+
+## License
+
+[MIT](LICENSE)