photon

<div align="center"> <img src="https://raw.githubusercontent.com/portel-dev/photon/main/assets/photon-logo.png" alt="Photon" width="500"> </div> [](https://www.npmjs.com/package/@portel/photon) [](https://www.npmjs.com/package/@portel/photon) [](https://github.com/portel-dev/photon/blob/main/LICENSE) [](https://www.typescriptlang.org) [](https://nodejs.org) [](https://modelcontextprotocol.io) [](https://photon.portel.dev/) ### One TypeScript capability becomes the whole agent stack. Photon is the fastest way to turn a small, verified TypeScript method into something humans can operate and agents can trust. Write the capability once; Photon derives the interfaces, contracts, and runtime behavior around it: - **MCP server** for Claude, ChatGPT, Cursor, and agents - **Embedded app UI** for chat clients that support MCP app resources - **CLI tool** for scripts, demos, and automation - **Beam web interface** for humans - **Web routes, schedules, webhooks, retries, state, and audit history** when the capability grows into a production workflow Photon is free and open source software released under the [MIT license](./LICENSE). Full documentation lives at [photon.portel.dev](https://photon.portel.dev/). Related Portel project: [NCP](https://portel-dev.github.io/ncp/) gives agents one natural MCP interface to discover and run tools across a whole tool ecosystem. Photon builds reliable agent-facing capabilities; NCP helps agents find and use them alongside every other MCP. **Try it in two minutes:** ```bash bun add -g @portel/photon photon new my-tool photon ``` That opens Beam, the generated human UI. Add `photon mcp install my-tool` when you want the same capability inside Claude Desktop or another MCP client. *Interfaces are optional. Intent is mandatory.* ```bash gh repo star portel-dev/photon ``` --- ## From one method to every surface The weather example is intentionally small: one TypeScript method, a few docblock tags, and one `@ui` HTML asset. Photon turns that into a CLI command, Beam UI, MCP tool, and embedded app surface for MCP app-capable chat clients. Claude Desktop can run it from a local stdio MCP command; ChatGPT developer mode can connect to the same Photon over a public HTTPS `/mcp` endpoint. <div align="center"> <img src="https://raw.githubusercontent.com/portel-dev/photon/main/assets/showcase/weather/photon-surface-map.svg" alt="Infographic showing one Photon method becoming CLI, Beam, MCP, Claude Desktop, ChatGPT, and other agent surfaces" width="100%"> </div> Real clients, same Photon: <table> <tr> <td width="50%" align="center" valign="top"> <img src="https://raw.githubusercontent.com/portel-dev/photon/main/assets/showcase/weather/chatgpt-photon-weather-local-dot.png" alt="Real ChatGPT developer-mode session rendering the Photon weather app from a public HTTPS MCP endpoint"> <br>_{ChatGPT developer mode rendering the Photon weather UI from a public HTTPS <code>/mcp</code> endpoint.} </td> <td width="50%" align="center" valign="top"> <img src="https://raw.githubusercontent.com/portel-dev/photon/main/assets/showcase/weather/claude-weather-real.png" alt="Real Claude Desktop session rendering the Photon weather app through local MCP"> <br>_{Claude Desktop rendering the same Photon through local MCP.} </td> </tr> </table> [Follow the step-by-step tutorial](./docs/tutorials/from-method-to-chat-app.md) or open the runnable example in [`examples/weather-showcase`](./examples/weather-showcase). The tutorial also includes Beam, CLI, and a concept animation for the full transformation. --- ## The Photon Promise Photon is the modern dev stack for the agentic age: each photon is a small, auditable brick that can be used by humans, agents, schedulers, webhooks, and apps without rewriting the same capability for every interface. <div align="center"> <img src="https://raw.githubusercontent.com/portel-dev/photon/main/assets/photon-agentic-stack.png" alt="Photon agentic stack infographic showing one intent becoming MCP contracts, human surfaces, apps, operations, trust boundaries, and composable systems" width="100%"> </div> That is the core idea: **tiny trusted capabilities compose into larger systems**. A photon can start as a helper method, become a CLI command, render as an app, run on a schedule, accept webhooks, and still expose a clean agent-readable contract. --- ### Example ```typescript // hello.photon.ts export default class Hello { greet(name: string) { return `Hello, ${name}!`; } } ``` That's a complete photon. From this single file you get: ``` $ photon cli hello greet --name Ada # CLI $ photon # Web UI at localhost:3008 $ photon mcp hello # MCP server for Claude, Cursor, etc. ``` No decorators. No registration. No server boilerplate. Just define the intent. Photon handles the rest. --- ### Quick Start From zero to an MCP server connected to Claude Desktop in three commands: ```bash bun add -g @portel/photon photon new my-tool # Scaffolds ./my-tool.photon.ts in your CWD photon mcp install my-tool # Registers it in Claude Desktop's config # Restart Claude Desktop. Your tool is live. ``` Prefer the web dashboard? Skip step 3 and run `photon` instead — it opens Beam, the auto-generated UI. Or try without installing globally: ```bash bunx @portel/photon new my-tool bunx @portel/photon mcp install my-tool # pnpm users can use pnpm dlx instead: pnpm dlx @portel/photon new my-tool pnpm dlx @portel/photon mcp install my-tool ``` > Requires [Node.js 20+](https://nodejs.org). TypeScript is compiled internally; no `tsconfig.json` needed. > > **Where do photon files live?** `./` (a project directory you cd into) or `~/.photon/` (global, auto-discovered). User settings persist under `~/.photon/state/<photon>/`. See [Where things live](docs/getting-started.md#where-things-live). ### How It Works You write a TypeScript class. Methods are your capabilities. Types describe what's valid. Comments explain the intent. Photon reads all of it and generates three interfaces from one file. Same logic. Same validation. Same data. <div align="center"> <img src="https://raw.githubusercontent.com/portel-dev/photon/main/assets/photon-core-concepts.svg" alt="Six Photon core concepts: methods, comments, types and tags, settings, UI and routes, and operations" width="100%"> </div> ``` analytics.photon.ts → Web UI (Beam) · CLI · MCP Server for AI ``` The more you express, the more Photon derives: | What you write | What Photon derives | |---|---| | Method signatures | Tool definitions: names, inputs, outputs | | Type annotations | Input validation rules, UI field types | | JSDoc comments | Documentation for AI clients and human users | | Constructor parameters | Config UI, environment variable mapping, runtime injection (`Photon`, `Cloudflare`, `CloudflareEnv`) | | `@tags` | Validation, formatting, scheduling, webhooks | When you add a `@param city {@pattern ^[a-zA-Z\s]+$}` annotation, Beam validates it in the form, the CLI validates it before running, and the MCP schema enforces it for the AI. One annotation. Three consumers. ### Three ways to author `extends Photon` is one shape. You can also inject `Photon` as a constructor parameter when you already extend something else, or compose without inheritance — same API either way. CF resources reach the photon through a separate `Cloudflare` injection so portable photons stay portable. See [docs/guides/PHOTON-INJECTION.md](docs/guides/PHOTON-INJECTION.md). --- ## Beam: Human Exploration Beam is the web dashboard. Every photon becomes an interactive form automatically. Run `photon`. That's the whole command. <div align="center"> <img src="https://raw.githubusercontent.com/portel-dev/photon/main/assets/beam-dashboard.png" alt="Beam Dashboard" width="100%"> </div> The UI is **fully auto-generated** from your method signatures: field types, validation, defaults, layouts. You never write frontend code. When you add a `{@choice a,b,c}` tag to a parameter, Beam renders a dropdown. When you mark a string as `{@format email}`, the field validates email format. The UI evolves as your code does. When forms aren't the right interface for what you're building, you can replace Beam's auto-generated view with your own HTML. A global named after your photon is auto-injected (e.g., `analytics.onResult(data => ...)`) — no framework required. `window.photon.url` is also injected and resolves to the Beam base URL so your HTML can construct fetch paths correctly whether running locally or behind a reverse proxy. > Custom UIs follow the [official MCP Apps Extension](https://modelcontextprotocol.io/extensions/apps/overview) and work across compatible hosts. See the [Custom UI Guide](./docs/guides/CUSTOM-UI.md). Photons that declare HTTP routes with `@get`, `@post`, `@put`, `@patch`, or `@delete` are shown in Beam as web apps. Routes support dynamic path segments (e.g. `@get /items/:id`) matched by specificity: literal segments win over parameters. Beam proxies requests to those routes and injects an `x-photon-base-path` header so the app can construct correct absolute paths regardless of where Beam is hosted. --- ## AI Agents: Machine Invocation Photon ships separate, tested MCP adapters: sessionful MCP 2025 over stdio and Streamable HTTP, plus stateless MCP `2026-07-28` release-candidate support over Streamable HTTP. See the [compatibility matrix and runnable clients](./docs/guides/MCP-COMPATIBILITY.md), or run `photon doctor mcp` against your installed runtime. ```bash photon info analytics --mcp ``` ```json { "mcpServers": { "analytics": { "command": "photon", "args": ["mcp", "analytics"] } } } ``` Paste into your AI client's config. Your photon is now an MCP server. Claude can call your methods. Cursor can call your methods. Any MCP-compatible host can call your methods. The AI sees the same thing a human sees in Beam: the method names, the parameter descriptions from your JSDoc, the validation rules from your types. The JSDoc comment you wrote to document the tool for yourself is what Claude reads to decide when and how to call it. The MCP tools themselves work with [Claude Desktop](https://claude.ai/download), [Claude Code](https://docs.anthropic.com/en/docs/claude-code), [Cursor](https://cursor.com), and any MCP-compatible client. When your photon has a custom UI, clients that support the [MCP Apps Extension](https://modelcontextprotocol.io/extensions/apps/overview) can render it natively, as shown in the weather proof above. --- ## How a Photon Evolves Here is how a photon grows. Each step adds one thing and gets multiple capabilities from it. ### Add comments: AI understands your intent ```typescript /** * Weather - Check weather forecasts worldwide */ export default class Weather { /** * Get the weather forecast for a city * @param city City name (e.g., "London") */ async forecast(params: { city: string }) { ... } } ``` The class description becomes how AI clients introduce the tool to users. The `@param` description is what the AI reads before deciding what value to pass. Same comments. Human help text and AI contract at once. <div align="center"> <img src="https://raw.githubusercontent.com/portel-dev/photon/main/assets/readme-step-2.png" alt="Step 2" width="100%"> </div> ### Declare configuration: a settings tool appears ```typescript export default class Weather { /** User-tunable knobs. Photon auto-generates a `settings` tool from this. */ protected settings = { /** Units for forecast values */ units: 'metric', /** Polling interval in seconds */ pollIntervalSec: 300, }; async forecast(params: { city: string }) { const res = await fetch(`...?units=${this.settings.units}`); return await res.json(); } } ``` `protected settings` is the canonical way to expose runtime knobs. Photon reads the JSDoc on each property, generates an MCP `settings` tool with typed inputs, and persists user changes to `~/.photon/state/<photon>/<instance>-settings.json`. Inside methods, `this.settings` is a read-only Proxy. To change a value, the user (or AI) calls the auto-generated `settings` tool. For **secrets** that should never be persisted in a settings file (API keys, tokens), use a constructor parameter instead. Photon maps the parameter name to an env var: ```typescript export default class Weather { constructor(private apiKey: string) {} // → WEATHER_API_KEY } ``` The constructor pattern is for primitives that come from `.env`. The `protected settings` pattern is for everything else, including any knob the user should be able to change at runtime without restarting. **When in doubt, reach for `settings`.** <div align="center"> <img src="https://raw.githubusercontent.com/portel-dev/photon/main/assets/readme-step-3.png" alt="Step 3" width="100%"> </div> ### Add tags: behavior extends across all surfaces ```typescript /** * @dependencies node-fetch@^3.0.0 */ export default class Weather { /** * @param city City name {@example London} {@pattern ^[a-zA-Z\s]+$} * @param days Number of days {@min 1} {@max 7} * @format table */ async forecast(params: { city: string; days?: number }) { ... } } ``` `@dependencies` installs `node-fetch` automatically on first run, no manual package install needed. The `{@pattern}` validates in the form, the CLI, and the MCP schema simultaneously. `days` becomes a number spinner with bounds. `@format table` renders the result as a table in Beam. One annotation, three surfaces. <div align="center"> <img src="https://raw.githubusercontent.com/portel-dev/photon/main/assets/readme-step-4.png" alt="Step 4" width="100%"> </div> ### System CLI dependencies If your photon wraps a command-line tool, declare it and Photon enforces it at load time: ```typescript /** * @cli ffmpeg - https://ffmpeg.org/download.html */ export default class VideoProcessor { async convert({ input, format }: { input: string; format: string }) { // ffmpeg is guaranteed to exist when this runs } } ``` <div align="center"> <img src="https://raw.githubusercontent.com/portel-dev/photon/main/assets/readme-step-5.png" alt="Step 5" width="100%"> </div> --- ## What Comes for Free Things you don't build because Photon handles them: | | | |---|---| | **Auto-UI** | Forms, field types, validation, layouts generated from your signatures | | **Stateful instances** | Multiple named instances of the same photon, each with isolated state | | **Persistent memory** | `this.memory` gives your photon per-instance key-value storage, no database needed | | **Scheduled execution** | `@scheduled` runs any method on a cron schedule | | **Webhooks** | `@webhook` exposes any method as an HTTP endpoint | | **OAuth (client)** | Built-in OAuth 2.0 flows for Google, GitHub, Microsoft | | **OAuth Authorization Server** | Issue tokens to MCP clients yourself: CIMD + DCR, PKCE, OIDC id_token, RFC 8693 token exchange | | **SQLite persistence** | Audit log, execution history, and OAuth grants survive daemon restart (bun:sqlite or better-sqlite3) | | **Daemon ops** | `photon ps` lists and controls scheduled jobs, webhooks, and live sessions | | **Distributed locks** | `@locked` serializes access: one caller at a time, across processes | | **Cross-photon calls** | `this.call()` invokes another photon's methods | | **Cloudflare runtime** | `this.cf.r2('blobs')`, `this.cf.d1('app')`, `this.cf.kv('cache')` — same shape locally (miniflare) and deployed (real bindings). See [CF-BINDINGS.md](docs/guides/CF-BINDINGS.md) | | **Real-time events** | `this.emit()` fires named events to the browser UI with zero wiring | | **Live rendering** | `this.render()` pushes formatted output to CLI and Beam in real time | | **Delegated LLM** | `this.sample()` asks the driving agent's model to generate text — no API key, agent pays | | **Inline confirm / input** | `this.confirm()` and `this.elicit()` route through the client's native UI (Beam dialog, Claude prompt) | | **Scoped remote access** | `photon claim` generates a short-lived code to scope a remote MCP session to one directory | | **Standalone binaries** | `photon build` compiles any photon to a single executable via Bun | | **Dependency management** | `@dependencies` auto-installs npm packages on first run | --- ## Coordination: Locks + Events Two primitives. Together they unlock a class of things that are surprisingly hard to build today. **Locks** serialize access. When a method is marked `@locked`, only one caller can execute at a time, whether that caller is a human in Beam, a CLI script, or an AI agent. Everyone else waits their turn. **Events** push state changes to any browser UI in real time. `this.emit({ event: 'boardUpdated', data: board })` on the server becomes `chess.onBoardUpdated(handler)` in your custom UI — named after your photon file. No WebSockets to configure. No polling. Events are delivered via SSE through the MCP Streamable HTTP transport. Together: **turn-based coordination with live state**. ```typescript export default class Chess { /** Make a move. Locks ensure human and AI alternate turns. */ /** @locked */ async move(params: { from: string; to: string }) { const result = await this.applyMove(params.from, params.to); // Browser UI updates instantly, no polling needed this.emit({ event: 'boardUpdated', data: result.board }); this.emit({ event: 'turnChanged', data: { next: result.nextPlayer } }); return result; } } ``` ```javascript // In your custom UI (ui/chess.html) // The global `chess` is auto-injected, named after your photon file chess.onBoardUpdated(board => renderBoard(board)); chess.onTurnChanged(({ next }) => showTurn(next)); // Call server methods directly chess.move({ from: 'e2', to: 'e4' }); ``` A human moves through Beam. Claude is configured with the MCP server. The lock ensures they truly alternate. Events keep the board live on both sides. That's a fully functional turn-based chess game, human vs AI, in about 50 lines of application logic. The same pattern applies beyond games: approval workflows where a human reviews before AI continues, collaborative tools where edits from any source appear instantly, simulations where steps must execute in strict sequence, any system where **who acts next matters**. --- ## MCP Primitives on `this` The MCP protocol's user-facing primitives are surfaced as plain methods on every photon instance — no decorators, no capability flags, no SDK imports. The runtime routes each call through whichever surface the request arrived on (Beam, Claude Desktop, Cursor, CLI). ```typescript export default class Editor { async summarize(params: { text: string }) { // Ask the driving agent's LLM. No API key. Agent pays. return await this.sample({ prompt: `Summarize in one sentence:\n\n${params.text}`, maxTokens: 128, }); } async deploy() { if (!(await this.confirm('Ship to production?'))) return; const env = await this.elicit<string>({ ask: 'select', message: 'Which environment?', options: ['staging', 'prod'], }); await this.run(env); } } ``` | Primitive | What it does | |---|---| | `await this.sample({ prompt })` | Delegates LLM generation to the caller's model via MCP sampling | | `await this.confirm(question)` | Yes/no prompt — returns `boolean` | | `await this.elicit(params)` | Arbitrary input (text, select, form, file, etc.) | | `this.status(msg)` / `this.progress(v)` | Live feedback during long work; routes to SSE stream in Beam | | `this.roots` | MCP workspace roots declared by the connected client (`roots/list`) | | `this.notifyResourceUpdated(uri)` | Push `notifications/resources/updated` to subscribed clients | Full reference: [`docs/reference/MCP-PRIMITIVES.md`](docs/reference/MCP-PRIMITIVES.md). --- ## Remote Access: Claim Codes By default every installed photon is visible to every connected MCP client. When you want to pair a *remote* agent with a *subset* of your photons — your phone driving Beam, a teammate reviewing one project, a CI agent scoped to a single directory — generate a claim code: ```bash $ photon claim --scope /workspace/proj --ttl 4h --label "phone" ✓ Claim code: R3K-9QZ Scope: /workspace/proj Expires in: 4h ``` The remote client presents the code as the `Mcp-Claim-Code` header on its MCP session. `tools/list` then only exposes photons whose source lives under that directory. Sessions without a code keep full access — the feature is strictly opt-in. Full reference: [`docs/reference/CLAIM-CODES.md`](docs/reference/CLAIM-CODES.md). --- ## Marketplace A curated set of photons is ready to install. The public gallery is now kept small on purpose: polished apps and tools in one place, teaching examples in another. <div align="center"> <img src="https://raw.githubusercontent.com/portel-dev/photon/main/assets/beam-marketplace.png" alt="Marketplace" width="100%"> </div> ```bash photon search boards photon add boards ``` You can also install directly from any GitHub repository using qualified refs: ```bash photon add owner/repo/photon-name ``` Browse the [Photon Apps marketplace](https://github.com/portel-dev/photons) for ready-to-use photons, or the [Photon Examples marketplace](https://github.com/portel-dev/photon-examples) for focused learning examples. You can also host a private marketplace for your team: internal tools that stay off the public internet. --- ## Commands ```bash # Run photon # Open Beam UI photon mcp <name> # Run as MCP server photon mcp <name> --dev # MCP server with hot reload photon cli <name> [method] # Run as CLI tool # Install from GitHub photon beam owner/repo/name # Install & open in Beam photon cli owner/repo/name method # Install & run via CLI # Create photon maker new <name> # Scaffold a new photon # Build photon build <name> # Compile to standalone binary photon build <name> --with-app # Include Beam UI in binary # Manage photon info # List all photons photon info <name> --mcp # Get MCP client config photon maker validate <name> # Check for errors # Marketplace photon add <name> # Install photon photon search <query> # Search marketplace photon upgrade # Upgrade all # Ops photon doctor # Diagnose environment photon test # Run tests photon ps # Observe & control scheduled jobs, webhooks, sessions ``` ### `photon ps`: scheduled jobs, webhooks, and sessions `photon ps` is the operator surface for the daemon. Without arguments it prints a four-section snapshot — ACTIVE schedules, DECLARED-but- not-enrolled, WEBHOOKS, and ACTIVE SESSIONS. ```bash photon ps # full snapshot photon ps --json # structured output for scripts photon ps --type active # one section only photon ps --base ~/Projects/kith # filter to one PHOTON_DIR ``` **Two-step model.** A `@scheduled` annotation in source is **DECLARED** until enrolled. Enrollment is per-machine, persistent, and explicit: ```bash photon ps enable newsletter:sendDigest # DECLARED → ACTIVE photon ps disable newsletter:sendDigest # ACTIVE → suppressed (survives restart) photon ps pause newsletter:sendDigest # stop firing without removing enrollment photon ps resume newsletter:sendDigest # undo pause photon ps history newsletter:sendDigest # last 20 firings: timestamp, status, error ``` For manual cron schedules without a `@scheduled` tag, use the Beam Pulse panel ("Add schedule") or call `this.schedule.create()` from photon code. `this.schedule.create()` (programmatic schedules) skips DECLARED and goes straight to ACTIVE. See [`docs/GUIDE.md#scheduling`](docs/GUIDE.md#scheduling-scheduled-thisschedule-photon-ps) for the full reference, the daemon state layout, and `.photon-no-host` for multi-host setups. ### Install from GitHub Use qualified refs to install and run photons directly from any GitHub repository: ```bash photon beam Arul-/photons/claw # Install from GitHub, open in Beam photon cli Arul-/photons/todo add # Install from GitHub, run method ``` The format is `owner/repo/photon-name`. Transitive `@photon` dependencies from the same repo are resolved automatically. ### Compile to Binary Build standalone executables from any photon — no Node.js required on the target machine: ```bash photon build my-tool # Binary for current platform photon build my-tool -t bun-linux-x64 # Cross-compile for Linux photon build my-tool --with-app # Embed Beam UI as a desktop app ``` Uses Bun's compiler under the hood. The binary bundles the photon, its `@dependencies`, and transitive `@photon` deps into a single file. --- ## Tag Reference | Tag | Where | What it does | |---|---|---| | `@dependencies` | Class | Auto-install npm packages on first run | | `@cli` | Class | Declare system CLI dependencies, checked at load time | | `@format` | Method | Result rendering (table, list, markdown, code, etc.) | | `@param ... {@choice a,b,c}` | Param | Dropdown selection in Beam | | `@param ... {@choice-from method}` | Param | Dynamic dropdown populated from another method's return value | | `@param ... {@format email}` | Param | Input validation and field type | | `@param ... {@min N} {@max N}` | Param | Numeric range constraints | | `@ui` | Class/Method | Link a custom HTML template | | `@auth` | Class | Require or describe MCP authentication and populate `this.caller` | | `@scope` | Method | Override the inferred OAuth scope for a protected MCP tool call | | `@expose` | Method | Auto-bind to `POST /api/<kebab>` for SPA fetch (`public` skips the SameSite gate) | | `@get /path` | Method | HTTP-only GET route; shown as a web app in Beam, not an MCP tool. Supports `:param` segments | | `@post /path` | Method | HTTP-only POST route; shown as a web app in Beam, not an MCP tool. Supports `:param` segments | | `@put /path` | Method | HTTP-only PUT route; shown as a web app in Beam, not an MCP tool. Supports `:param` segments | | `@patch /path` | Method | HTTP-only PATCH route; shown as a web app in Beam, not an MCP tool. Supports `:param` segments | | `@delete /path` | Method | HTTP-only DELETE route; shown as a web app in Beam, not an MCP tool. Supports `:param` segments | | `@resource <uri>` | Method | Dynamic MCP resource resolver (canonical form; replaces `@Static`) | | `@prompt` | Method | MCP prompt template (canonical form; replaces `@Template`) | | `@webhook` | Method | Expose as HTTP endpoint | | `@scheduled` | Method | Run on a cron schedule | | `@locked` | Method | Distributed lock across processes | | `@autorun` | Method | Auto-execute when selected in Beam | | `@mcp` | Class | Inject another MCP server as a dependency | | `@icon` | Class/Method | Set emoji icon | > See the full [Tag Reference](./docs/reference/DOCBLOCK-TAGS.md) for all 30+ tags with examples. --- ## Documentation **Start here:** | Guide | | |---|---| | [Getting Started](./docs/getting-started.md) | Install, build, and run your first photon in 5 minutes | | [From Method to Chat App](./docs/tutorials/from-method-to-chat-app.md) | Weather showcase: CLI, Beam, MCP, and embedded app UI from one method | | [Core Concepts](./docs/concepts.md) | The 6 ideas behind Photon | | [Tag Reference](./docs/reference/DOCBLOCK-TAGS.md) | Public reference for every docblock tag Photon understands | | [Output Formats](./docs/formats.md) | Visual gallery of every `@format` type | | [Intent Metadata](./docs/reference/INTENT-METADATA.md) | How comments, schemas, annotations, and formats map to native surfaces | | [Settings](./docs/GUIDE.md#settings-user-configurable-knobs) | Declare runtime knobs with `protected settings` (the canonical config pattern) | | [Troubleshooting](./docs/TROUBLESHOOTING.md) | Common issues and solutions | **Go deeper:** | Topic | | |---|---| | [Custom UI](./docs/guides/CUSTOM-UI.md) | Build rich interactive interfaces with the photon bridge API | | [OAuth](./docs/guides/AUTH.md) | Built-in OAuth 2.0 with Google, GitHub, Microsoft | | [MCP JWT Auth](./docs/guides/MCP-JWT-AUTH.md) | Secure deployed MCP tool calls with short-lived scoped JWTs | | [MCP Client Registration](./docs/guides/mcp-client-registration.md) | Register MCP clients with Photon's AS via CIMD or DCR | | [Observability](./docs/guides/observability.md) | OpenTelemetry traces, metrics, logs, and structured errors | | [Protocol Features](./docs/guides/PROTOCOL-FEATURES.md) | Capability handshake, structured errors, trace correlation | | [Daemon Pub/Sub](./docs/internals/DAEMON-PUBSUB.md) | Real-time cross-process messaging | | [Webhooks](./docs/reference/WEBHOOKS.md) | HTTP endpoints for external services | | [Locks](./docs/reference/LOCKS.md) | Distributed locks for exclusive access | | [Advanced Patterns](./docs/guides/ADVANCED.md) | Lifecycle hooks, dependency injection, interactive workflows | | [Marketplace Configuration](./docs/guides/MARKETPLACE-CONFIG.md) | Sharing settings across related photons in one marketplace | | [Deployment](./docs/guides/DEPLOYMENT.md) | Docker, Cloudflare Workers, AWS Lambda, Systemd | **Operate:** | Topic | | |---|---| | [The Photon Daemon](./docs/guides/DAEMON.md) | Lifecycle, PHOTON_DIR resolution, resilience, troubleshooting | | [Security](./SECURITY.md) | Best practices and audit checklist | | [Marketplace Publishing](./docs/guides/MARKETPLACE-PUBLISHING.md) | Create and share team marketplaces | | [Best Practices](./docs/guides/BEST-PRACTICES.md) | Patterns for production photons | **Reference:** [Complete Developer Guide](./docs/GUIDE.md) · [Tag Reference](./docs/reference/DOCBLOCK-TAGS.md) · [Naming Conventions](./docs/guides/NAMING-CONVENTIONS.md) · [Architecture](./docs/internals/ARCHITECTURE.md) · [Lifecycle & Ingress](./docs/internals/LIFECYCLE-AND-INGRESS.md) · [PHOTON_DIR & Namespace](./docs/internals/PHOTON-DIR-AND-NAMESPACE.md) · [Changelog](./CHANGELOG.md) · [Contributing](./CONTRIBUTING.md) --- ## Open Source Photon is free and open source under the [MIT license](./LICENSE). The project is still evolving and contributions are welcome. - Star the repository if the idea resonates: `gh repo star portel-dev/photon` - [Report issues](https://github.com/portel-dev/photon/issues) - [Contribute improvements or examples](./CONTRIBUTING.md)