Ray 3.0

Product Introduction

1. Definition: Ray 3.0 is a cross-platform desktop debugging tool (macOS/Windows/Linux) designed for developers working with AI agents, PHP, Laravel, JavaScript, and other languages. It captures and organizes debug output (strings, arrays, objects, queries, etc.) in a dedicated visual interface.
2. Core Value Proposition: Ray eliminates context-switching by moving debug data out of terminals/browsers into a structured, interactive viewer. It centralizes debugging workflows, enhances readability of AI-generated output (like HTML components or Mermaid diagrams), and supports real-time collaboration via SSH.

Main Features

1. Multi-Language Debugging:

   • How it works: Ray intercepts ray() calls (or equivalent in JS/PHP) and streams data to its desktop app. Uses lightweight clients (e.g., spatie/ray package for PHP) to send payloads via TCP.
   • Technologies: TCP/IP communication, platform-native rendering (Electron for cross-platform UI), and custom parsers for data types (SQL queries, stack traces).

2. AI Output Visualization:

   • How it works: Integrates with AI agents to render dynamic content (e.g., Mermaid/ERD diagrams, HTML prototypes) in Ray’s viewer. Uses a built-in MCP server to grant AI access to local tools/windows.
   • Technologies: Mermaid.js for diagram rendering, headless browser components for HTML previews.

3. Execution Control Tools:

   • How it works: Pauses PHP/Laravel code execution to measure timing between calls or inspect state. Auto-captures queries/jobs/exceptions without manual dd() breaks.
   • Technologies: PHP extension hooks, Xdebug integration alternatives.

4. Remote SSH Debugging:

   • How it works: Streams debug data from remote servers via SSH tunnels. Messages appear in Ray’s local interface with origin tags (e.g., server: production).
   • Technologies: OpenSSH tunneling, encrypted message queuing.

Problems Solved

1. Pain Point: Fragmented debugging workflows force developers to juggle terminals, browsers, and IDE consoles, slowing iteration. Ray consolidates outputs into one searchable, filterable interface.
2. Target Audience:
   • AI/ML engineers debugging agent-generated content.
   • Full-stack developers (PHP/Laravel, JavaScript, WordPress).
   • Teams collaborating on remote servers or complex microservices.
3. Use Cases:
   • Debugging AI-generated HTML/Mermaid diagrams without terminal limitations.
   • Comparing archived messages to diagnose intermittent bugs.
   • Monitoring production issues via SSH without local log replication.

Unique Advantages

1. Differentiation: Unlike browser DevTools or terminal dump tools (e.g., xdebug), Ray offers IDE-like navigation (click-to-jump to files), theme customization, and AI-specific rendering. Competitors lack Mermaid/HTML previews or SSH streaming.
2. Key Innovation: The MCP server bridges AI tools and local environments, enabling real-time interaction with AI output. Combined with pause/measure execution, this reduces manual instrumentation by 70% (per user testimonials).

Frequently Asked Questions (FAQ)

1. Does Ray 3.0 support JavaScript frameworks like React or Vue?
   Yes, Ray’s JavaScript client works with React, Vue, Node.js, and vanilla JS. Send data via ray(object) and view structured outputs in the desktop app.

2. Can I use Ray for debugging production environments?
   Ray supports SSH-based remote debugging, allowing safe output streaming from production servers. Avoid overloading with ray()->limit() to cap message volume.

3. How does Ray 3.0 handle licensing for teams?
   Licenses (annual/lifetime) are managed via Spatie. Each seat covers one user across unlimited devices. VAT is added at checkout, and pre-3.0 licenses remain valid.

4. Is Ray compatible with Windows/Linux for PHP development?
   Ray provides native apps for Windows (x86), Linux (AppImage), and macOS (ARM/Intel). PHP debugging requires the spatie/ray Composer package.

5. What happens to my debug data when Ray is closed?
   Sessions auto-archive locally. Use the "Archive" feature to save messages indefinitely for later comparison or audits.