LynxPrompt — Summary

LynxPrompt is a self-hostable, federated platform for managing AI IDE configuration files — AGENTS.md, CLAUDE.md, .cursor/rules/, slash commands, and 30+ other formats — deployed via Docker Compose with a Next.js web UI, PostgreSQL database, and a CLI (lynxp). The platform functions as an internal marketplace where teams create "blueprints" (configuration templates), share them within an organization, and export them to any supported AI tool format with one click. An interactive wizard (web + CLI) auto-detects tech stack from GitHub/GitLab URLs, supports template variables and monorepo hierarchies, and handles SAML/OIDC/LDAP for enterprise SSO. Optional AI-assisted blueprint editing via the Anthropic API (opt-in, requires user's own API key) is the only cloud-bound feature. The VS Code extension, npm-distributed CLI (lynxp), GitHub Action, n8n node, Helm chart, and MCP server form a broad distribution ecosystem — making LynxPrompt the most "enterprise-ready" distribution mechanism among all ten batch frameworks. Unlike seed frameworks that define agent behavior, LynxPrompt's value is the institutional knowledge management layer: standardizing which CLAUDE.md files exist across teams, versioning them, and distributing them at scale.

LynxPrompt — Overview

Origin

Created by Sergio Fernández Rubio (GeiserX on GitHub). Licensed under GPL-3.0. Website: lynxprompt.com. Hosted instance available for those who prefer not to self-host.

Philosophy

LynxPrompt is a config management platform — it treats AI tool configuration files (CLAUDE.md, AGENTS.md, .cursorrules) as first-class organizational assets that need versioning, sharing, and standardization the same way code does.

From the README:

"Instead of manually writing configuration files for every project and every AI tool, use LynxPrompt to: Generate configs through an interactive wizard / Share blueprints through a private or federated marketplace / Standardize AI behavior across projects with reusable templates / Export to any supported format with one click."

"LynxPrompt is free and open-source. Self-host it for personal use, or deploy it within your organization to enforce coding standards, share institutional knowledge, and ensure consistent AI assistant behavior across your engineering teams."

Key Design Principles

1. Self-hostable first — Docker Compose as the deployment primitive, not SaaS
2. 30+ format support — write once, export to any AI tool
3. Federated marketplace — teams can share blueprints within or across organizations
4. All-or-nothing auth — SAML, OIDC, LDAP, OAuth, passkeys, magic link — full enterprise auth stack
5. Optional AI — AI-assisted editing is opt-in and uses the user's own Anthropic key; the platform works fully without it

Scope

LynxPrompt is the only framework in this batch that explicitly targets enterprise teams — multi-user, SSO-enabled, team-scoped blueprint sharing, self-hosted infrastructure. All other frameworks are single-developer tools.

Ecosystem Components

• lynxprompt-mcp — MCP server for browsing blueprints from AI assistants
• lynxprompt-vscode — VS Code extension
• homebrew-lynxprompt — Homebrew tap
• n8n-nodes-lynxprompt — n8n community node for workflow automation
• lynxprompt-action — GitHub Action for CI/CD integration
• Helm chart — Kubernetes deployment
• AUR package — Arch Linux
• Snap package — Ubuntu/Snap
• Chocolatey package — Windows

LynxPrompt — Architecture

Distribution

• Type: Self-hosted web app + CLI tool + VS Code extension + MCP server
• CLI Binary: lynxp (also lynxprompt) from cli/dist/index.js
• CLI Version analyzed: 2.1.0
• Web App Version: 2.1.0
• License: GPL-3.0
• Runtime required: Docker (for server), Node.js (for CLI)

Install Methods

# Server (Docker Compose)
curl -O https://raw.githubusercontent.com/GeiserX/LynxPrompt/main/docker-compose.selfhost.yml
docker compose -f docker-compose.selfhost.yml up -d
# → http://localhost:3000

# CLI
npm install -g lynxprompt
# Point to self-hosted instance (optional):
lynxp config set-url https://lynxprompt.your-company.com

# Homebrew
brew install GeiserX/lynxprompt/lynxprompt

# Chocolatey (Windows)
choco install lynxprompt

# AUR
# (Arch Linux)
# Snap
snap install lynxprompt

# Helm (Kubernetes)
helm repo add lynxprompt https://geiserx.github.io/LynxPrompt
helm install lynxprompt lynxprompt/lynxprompt

Tech Stack

Directory Tree

LynxPrompt/
├── src/
│   ├── app/               # Next.js App Router pages
│   ├── components/        # React UI components
│   ├── lib/               # Auth, DB, utilities
│   ├── types/             # TypeScript types
│   └── proxy.ts           # API proxy
├── cli/
│   ├── src/
│   │   ├── index.ts       # CLI entry point
│   │   ├── config.ts      # CLI config
│   │   ├── api.ts         # API client
│   │   └── commands/      # CLI command implementations
│   │       ├── analyze.ts, check.ts, config.ts, convert.ts
│   │       ├── diff.ts, hierarchies.ts, import.ts, link.ts
│   │       ├── list.ts, login.ts, logout.ts, merge.ts
│   │       ├── pull.ts, push.ts, search.ts, status.ts
│   │       ├── whoami.ts, wizard.ts
│   └── package.json       # bin: {lynxprompt, lynxp}
├── prisma/                # DB schema + migrations
├── charts/lynxprompt/     # Helm chart
├── docker/                # Docker configs
├── action/                # GitHub Action
├── packages/              # Internal packages (MCP server, etc.)
└── docker-compose.selfhost.yml

Configuration Environment Variables

Key: NEXTAUTH_SECRET, APP_URL, ENABLE_GITHUB_OAUTH, ENABLE_EMAIL_AUTH, ENABLE_PASSKEYS, ENABLE_SSO, ENABLE_AI, AI_MODEL, ANTHROPIC_API_KEY, ENABLE_STRIPE, SUPERADMIN_EMAIL, ENABLE_USER_REGISTRATION

LynxPrompt — Components

CLI Commands (18 subcommands)

Web Platform Features

Supported AI Tool Formats (30+)

Cursor, Claude Code, GitHub Copilot, Windsurf, Zed, Aider, Gemini CLI, Cline, Roo Code, Amazon Q, JetBrains Junie, and more.

Ecosystem Integrations

LynxPrompt — Uniqueness

differs_from_seeds

LynxPrompt is closest to agent-os (both are "write files that agents read" frameworks) and claude-conductor (both are markdown scaffold tools), but LynxPrompt operates at a fundamentally different scale: it is a multi-user, enterprise-ready platform with a full database, authentication stack (SAML/OIDC/LDAP), federated marketplace, and a 18-subcommand CLI — where agent-os and claude-conductor are single-developer directory bundles. Unlike all seeds, LynxPrompt treats AI config files as organizational artifacts requiring version control, team sharing, and compliance management. The closest seed parallel is spec-kit (which also has a CLI and aims for consistency), but spec-kit governs agent behavior in sessions while LynxPrompt governs config file distribution across machines and teams. LynxPrompt has no behavioral enforcement mechanism — it doesn't care what the agent does with the CLAUDE.md, only that teams have a consistent, governed way to create and distribute it.

Positioning

• Primary differentiator: The only framework in the batch (and likely in the broader catalog) that provides enterprise-grade governance for AI configuration files — SSO, federated marketplace, multi-user team management, version control.
• Secondary differentiator: Format-agnostic distribution: write once, export to 30+ AI tool formats. This is similar to a "design token" system for AI configs.
• Target user: Engineering teams at organizations with multiple developers, multiple AI tools, and a need for standardized AI coding assistant behavior across projects.

Observable Failure Modes

1. Infrastructure overhead: Docker Compose + PostgreSQL is heavy for solo developers; codesight or agent-os serve the same config generation need with zero infrastructure.
2. GPL-3.0 license: Enterprise adoption may be blocked by GPL-3.0 copyleft; other tools in the batch are MIT or Apache-2.0.
3. Platform dependency: Teams become dependent on the self-hosted LynxPrompt server for config distribution — if the server goes down, lynxp pull fails.
4. No behavioral enforcement: LynxPrompt distributes configs but cannot enforce that agents follow them — a Claude Code session can still ignore the distributed CLAUDE.md.
5. Feature surface complexity: Stripe marketplace, blog, forum, n8n integration, Helm chart, Chocolatey — extensive feature surface for a config distribution tool; may create maintenance burden.