Early Access

Help Us Build This

Get Early Access

We'll send you updates as we add features and improve LogicStamp

LogicStamp is live, and we're looking for early users to help us improve

LogicStamp is currently built and maintained primarily by Amit Levi, with early contributions from the community. I'd love more collaborators - your feedback and ideas directly shape what we build next.

🗺️ Roadmap

Here's what we're building next. Your feedback will help us prioritize what matters most.

Recent Achievements

View full changelog

v0.7.1 (Current) - 2026-03-05

Strict watch session tracking: added session-level statistics for errors, warnings, and resolved violations. Status block shows cumulative session metrics and active violations.
Simplified strict watch usage: --strict-watch now automatically enables watch mode. Use stamp context --strict-watch instead of requiring both flags.
Verbose output flag: added --verbose flag for detailed bundle output. Default CLI output now prioritizes summary messages, with detailed file output moved to verbose mode.
Normalized path display: consistent relative path formatting across all CLI commands for improved readability.
Performance improvements: reduced terminal noise by updating strict watch output only when violations change.
Internal refactoring: watch mode modules reorganized into dedicated watchMode/ folder for better structure and maintainability.

v0.7.0 (March 2026)

⚠️ Breaking: stamp context style now defaults to--style-mode lean for smaller bundles. Use--style-mode full for full metadata.
Watch mode improvements: faster incremental rebuilds and cached style metadata.
Extraction improvements: refactored prop extraction and expanded AST edge-case handling.
Schema fixes: lean/full style modes now properly validated.
Security awareness: CLI warns when security reports are missing.
Testing & reliability: expanded coverage across watch mode, extraction, and dependency scenarios.
Docs refresh: LogicStamp positioned as the Context Compiler for TypeScript.

v0.6.0 (February 2026)

Runtime schema validation: contracts now validated with AJV.
Fail-closed loading: invalid or malformed contracts are rejected.
Security hardening: path traversal protection and improved error handling.
Dependency updates: improved TypeScript 5.x support and patched vulnerabilities.
⚠️ Node.js ≥ 20 required

v0.5.x (January - February 2026)

Context bundle generation: deterministic JSON bundles describing components, props, hooks, and dependencies.
Dependency graph extraction: automatic analysis of component relationships across React and TypeScript projects.
Token optimization modes: multiple output modes designed to reduce LLM token usage while preserving structure.
Style metadata extraction: optional analysis of Tailwind, CSS modules, and styling frameworks.
Validation and CLI tooling: commands for validating generated context and inspecting bundle structure.
Workflow automation: foundation for CI usage and automated AI workflows with structured context bundles.

v0.4.x (January 2026)

Watch mode with incremental rebuilds.
Backend framework support (Express, NestJS).
Vue 3 TypeScript support.
Style metadata extraction across major UI frameworks.
MCP server integration.

Earlier Releases

MCP Server Integration - Available now! Get started
Style metadata extraction (Tailwind, SCSS, Material UI, ShadCN, Radix UI, Framer Motion, Chakra UI, Ant Design)
Dynamic Tailwind class parsing (Phase 1) - Enhanced Tailwind CSS extractor to resolve dynamic class expressions
Vue.js TypeScript/TSX support - Comprehensive Vue 3 Composition API support
Security scanning and secret sanitization
TOON output format

High Priority Bug Fixes

✓

Emit Detection Accuracy

✅ Fixed in v0.3.7 - Emit detection now correctly distinguishes between internal handlers and component public API emits. Only handlers that are part of the component's Props interface/type are included in the emits object.

✅ Fixed in v0.3.7

Dynamic Class Parsing (Phase 2)

Resolve advanced variable-based classes within template literals. Phase 1 complete (v0.3.9) - handles const/let variables, object properties, and conditional expressions (~70-80% of patterns). Phase 2 will handle object lookups with variables, cross-file references, and function calls returning class strings (~15-20% of edge cases). Estimated effort: 8+ hours.

🟡 Phase 1 Complete, Phase 2 Planned

Framework Expansion

✓

Backend Framework Support

✅ Complete in v0.4.0 - Comprehensive support for Node.js backend frameworks (Express.js, NestJS). Extracts API routes, HTTP methods, route parameters, request/response types, and framework-specific metadata. Introduces new node:api contract kind.

✅ Complete (v0.4.0)

JavaScript & JSX Support

Add support for JavaScript (.js) and JSX (.jsx) files in addition to TypeScript. Extend AST parser to handle JavaScript syntax, support JSDoc type annotations for type inference, and handle JavaScript-specific patterns (CommonJS, ES modules).

🔴 Not StartedHigh Priority

✓

Watch Mode

✅ Complete (v0.4.1) - Automatic context regeneration when source files change. Incremental rebuilds only regenerate affected bundles. Change detection shows what changed (props, hooks, state, events, components, functions). Debouncing (500ms) batches rapid changes. Status files for tooling integration. Strict watch mode available for breaking change detection.

✅ Complete (v0.4.1)

Complete Vue.js Support

Add full support for Vue Single File Components (.vue files). Parse template, script, and style blocks. Extract template syntax (directives, bindings, slots), script setup and composition API usage, and scoped styles/CSS modules. Support both Options API and Composition API.

🟡 Partially CompleteHigh Priority

MCP Server Enhancements

Semantic Component Search

Add semantic search across component bundles. Search by component descriptions, prop names, functionality, or metadata rather than requiring exact file/component names.

🔴 Not StartedHigh Priority

Git Baseline for Compare

Add git-based baseline support for context comparison, enabling meaningful drift detection against known reference points. Supports --baseline git:HEAD, git:main, or any git ref. Uses git worktree for clean isolation. Enables CI integration and --fail-on-breaking flag for contract drift detection.

🔴 Not StartedHigh Priority

Configuration File Support

Support mcp-config.json to set default values for profile, mode, paths, and other settings. Reduces parameter repetition and enables project-specific defaults.

🔴 Not StartedMedium Priority

Progress/Status Reporting

Add progress reporting for long-running operations like refresh_snapshot and compare_modes. Use MCP progress notifications to provide real-time updates.

🔴 Not StartedMedium Priority

Medium Priority Improvements

✓

CSS-in-JS Support Completeness

✅ Complete in v0.5.1 - All major CSS-in-JS libraries now supported: styled-components, Emotion, Material UI, ShadCN/UI, Radix UI, Framer Motion, Styled JSX, Chakra UI, and Ant Design.

✅ Complete (v0.5.1)

Enhanced Third-Party Component Info (Phase 2)

Phase 1 complete (v0.3.8) - Package names and versions now included. Phase 2 will extract prop types from TypeScript declaration files (.d.ts) in node_modules, handle different package structures and re-exports, and support generic types and type aliases.

🟡 Phase 1 Complete, Phase 2 Pending

TypeScript Type Extraction

Currently supports basic types, literal unions, and function types. Missing: generics (e.g., ListProps<T>), complex unions/intersections, and generic type parameters.

🟡 Partially Complete

Project-Level Insights

Add cross-folder relationships and project-wide statistics to context_main.json. Planned: cross-folder dependency analysis, project-wide component counts, aggregate style metadata statistics, and architecture pattern detection.

🔴 Not Started

Future Enhancements

Comparison & Drift Detection

•

Git Baseline for Compare - Add git-based baseline support using --baseline git:<ref> syntax. Enables CI/CD integration and --fail-on-breaking flag for contract drift detection. Uses git worktree for clean isolation.

Schema & Architecture

•

Conditional Schema by Language - Planned for v0.8.x - Make the UIFContract schema conditional based on the kind field. Use TypeScript discriminated unions and JSON Schema conditional validation to ensure language-specific fields are only present when relevant. Prerequisite for Python/Java support in v0.9.x.

Performance & Optimization

✓

Incremental bundle caching - Complete (v0.4.1) - Only regenerates changed bundles in watch mode

•

Output size optimization - Further reduce token counts while maintaining accuracy

•

Style metadata verbosity reduction - Reduce style extraction verbosity for nested components (depth >= 1) when using depth=2. Default behavior reduces Tailwind classes, component library lists, and removes SCSS/CSS details for nested components while preserving full extraction for entry components. Estimated ~30-40% reduction in style metadata tokens.

Framework Expansion

•

Svelte Support - Parse .svelte files. Extract props, reactive statements, stores, template syntax, bindings, scoped styles, and SvelteKit routing/layouts.

•

Python Support - Planned for v0.9.x - Parse Python AST, extract function signatures, classes, modules, type hints, and docstrings. Support FastAPI, Django, Flask. Generate Python-specific contracts with python:function or python:class kind. Prerequisites: Conditional schema (v0.8.x) and JS/JSX support.

•

Java Support - Planned for v0.9.x - Parse Java source files, extract class definitions, methods, interfaces, annotations, and Javadoc. Support Spring Boot and other popular frameworks. Generate Java-specific contracts with java:class kind. Prerequisites: Conditional schema (v0.8.x) and JS/JSX support.

Configuration & Extensibility

•

Custom profile configuration and overrides - User-defined profiles beyond preset options

•

Additional output formats - More format options for different AI workflow patterns

Developer Experience

•

Integration examples - Examples for popular AI assistants (Cursor, Claude Desktop, GitHub Copilot Chat)

•

Advanced debugging tools - Better diagnostics and troubleshooting capabilities

This roadmap is actively maintained. This is a solo project, so priorities will shift based on what I learn from early users.

For the complete roadmap with detailed implementation plans, see Context ROADMAP.md and MCP ROADMAP.md. For known limitations with code evidence, see Known Limitations.

Looking for contributors! If you're interested in helping build LogicStamp, check out the contributing guide or reach out directly.

Repositories: CLI • MCP Server

Who Should Join?

We're looking for developers who use AI assistants and want to help us make this better

Developers Using AI Assistants

If you're already using Cursor, Copilot, or Claude regularly, you probably know the pain of managing context. Help us make it better.

Teams with React/TypeScript Codebases

LogicStamp works best with React and TypeScript right now. If that's your stack, we'd love to see how it works for your team.

Open Source Maintainers

If you maintain an open source project, we think LogicStamp could help contributors understand your codebase faster. We'd love to test this theory.

People Who Like Trying New Tools

If you enjoy being an early adopter and don't mind the occasional rough edge, we'd love your feedback. We're responsive and actually listen.

Contributors Welcome

This is a solo project, and I'm actively looking for contributors! Whether it's bug fixes, new features, or documentation improvements, your contributions are welcome. Check out the contributing guide to get started.

Developers with Large Codebases

If you're working on a large codebase where context management is a real challenge, LogicStamp could help. We're especially interested in feedback from projects with complex architectures or many components.

Want to Help Us Build This?

We're just getting started. Your feedback will help us figure out what to build next.

Get Involved Read the Docs Contribute

Open source CLI • Free to use • Built with your feedback • Looking for contributors