Chayya — The Shadow of Your Best Work

What the company appears to be: Chayya is a self-reported browser automation tool designed for individuals who perform repeated tasks in web browsers. The author describes it as a "human-in-control workflow companion" that records workflows using Playwright, generates clear step-by-step explanations and SOPs, and allows users to review and trust automated routines.

What changed: The project was submitted to the OpenAI 2026 hackathon by a single founder (Ranveer Singh), indicating an early-stage development effort. It is described as a local-first React/Vite application with an Express backend and optional Electron desktop shell, built using Playwright for recording/replaying browser actions.

Single most important open question: Is there evidence of real-world usage or adoption beyond the author's own development work?

The description states that Chayya is a browser automation tool. It records workflows using Playwright, turns them into reviewable artifacts, and allows for safe replay with clear steps and evidence.

• The product uses Playwright for recording and replaying browser actions.
• It generates SOPs and Rule Books from captured workflows.
• It preserves the original actions while offering an optimized version.
• It includes audit trail functionality to show proof of each run.
• It is built as a local-first React/Vite application with an Express backend, optionally wrapped in an Electron desktop shell for macOS and Windows.

The author also mentions that it supports human-in-the-loop automation, where the user must inspect what happened before allowing background replay.

Not evidenced: The actual functionality beyond self-reporting, including whether workflows are actually reusable or trusted by users.

The description claims Chayya is a tool for turning tasks done once into trusted routines, with clear steps and evidence. It emphasizes:

• A human-in-control approach.
• Trust through visible replay proof and audit history.
• Reusability without black boxes.
• Transparent optimization that preserves original actions.

It positions itself as a solution for people who do repetitive browser tasks (e.g., research, lesson prep, back-office processes) but want to avoid automation that removes visibility or control.

The claim evolution shows a shift from general-purpose automation to trust-based, reviewable, and human-centered automation.

Not evidenced: Whether this positioning has been validated by users or market feedback.

The author states that Chayya is for people who perform repeated browser tasks such as:

• Researching topics
• Preparing lessons
• Checking information
• Following back-office processes

It is described as useful for students, teachers, and business users who need to trust automated workflows.

Not evidenced: Specific customer segments, personas, or adoption data. No mention of existing customers or user groups beyond the author’s own use case.

The description does not provide any information about:

• Revenue model
• Pricing structure
• Monetization strategy
• Customer acquisition plan

Not evidenced: Any commercial details beyond the product concept.

The project is built using:

• Frontend: React/Vite
• Backend: Express.js
• Automation engine: Playwright
• Desktop support: Optional Electron shell for macOS and Windows
• AI integration: GPT-5.6 via OpenAI Codex (used for engineering acceleration)
• Security features: Redaction of sensitive values
• Workflow logic: Separation between original capture and optimized version

The author notes that workflows must pass in a visible browser before background replay is allowed, suggesting a conservative safety design.

Not evidenced: Deployment architecture, scalability, or performance metrics.

There is no evidence of:

• Revenue
• Customers
• Usage data
• Product-market fit
• User feedback or adoption beyond the author’s own development

The project was submitted to a hackathon and is described as a single-person effort. It has not been independently verified or tested in real-world conditions.

Not evidenced: Any traction indicators, including user engagement, retention, or growth.

No mention of competitors or market positioning beyond the author’s own description. The project does not reference existing tools like RPA platforms, browser automation tools, or workflow automation systems.

Not evidenced: Competitive landscape, differentiation, or competitive advantages.

• Single-founder development: No team or external validation.
• Unproven market demand: No evidence of real-world usage or customer feedback.
• Limited scope: Built for browser tasks only; no indication of mobile or VR support beyond future plans.
• Self-reported AI integration: The use of GPT-5.6 is described as a development aid, not a core product feature.
• No commercialization strategy: No pricing, monetization, or go-to-market plan.

Inference: The lack of traction and external validation raises questions about whether the tool will gain adoption beyond its creator’s own use case.

1. What specific browser tasks are you seeing users perform repeatedly that would benefit from this tool?
2. How do you plan to validate that users trust the automated workflows?
3. Have you tested Chayya with actual users beyond yourself?
4. What is your path to monetization or scaling beyond a hackathon project?
5. Are there any known limitations in how well Playwright handles live websites, and how are those mitigated?
6. How do you intend to support mobile or VR workflows in the future?