Inlaya

Inlaya is a Next.js app for importing a GitHub repository, browsing its issues, and working on those issues inside a live E2B sandbox with AI-assisted edit flows.

What It Does

• Connects a user account to GitHub
• Imports a repository into the app as a project
• Lists GitHub issues for that project
• Starts one shared sandbox per project
• Lets users inspect files, run commands, view diffs, and prepare AI-assisted edits
• Persists issue chat history in Postgres through Prisma

Main Flow

1. Sign in with Clerk.
2. Connect GitHub.
3. Import a repository on /projects/new.
4. Open /projects/[id] to browse issues and manage the sandbox.
5. Open /projects/[id]/issues/[issueNumber] to work on a specific issue.
6. Reuse the same project sandbox for file operations, commands, diffs, and AI edit preparation.

Stack

• Next.js App Router
• React
• Clerk
• Prisma + PostgreSQL
• GitHub App / GitHub OAuth
• E2B sandboxes
• OpenRouter for AI edit generation and model selection

Project Structure

• src/app App Router pages, layouts, and API routes
• src/components UI components for project, issue, and sandbox workflows
• src/server Server-side modules for GitHub, sandbox, chat, AI, and database access
• prisma/schema.prisma Prisma data model and relations
• docs/architecture.md Higher-level frontend, API, and sandbox architecture
• docs/database.md Human-readable explanation of the Prisma models

Prerequisites

• Node.js
• pnpm
• PostgreSQL database
• Clerk project credentials
• GitHub App credentials
• E2B API key
• OpenRouter API key (OPENROUTER_API_KEY)

Environment Variables

The app validates its environment in src/env.js.

Server-side variables:

• APP_URL — public application origin, such as http://localhost:3000 locally or https://inlaya.raghavgaba.me in production
• DATABASE_URL
• CLERK_SECRET_KEY
• GITHUB_APP_ID
• GITHUB_APP_PRIVATE_KEY
• GITHUB_APP_CALLBACK_URL
• GITHUB_APP_CLIENT_ID
• GITHUB_APP_CLIENT_SECRET
• GITHUB_APP_INSTALL_URL
• OPENROUTER_API_KEY
• OPENROUTER_MODEL
• OTEL_SERVICE_NAME — service name shown in Jaeger; defaults to inlaya-agent
• OTEL_TRACES_EXPORTER — "otlp" (default), "console", or "none"
• OTEL_EXPORTER_OTLP_TRACES_ENDPOINT — complete OTLP/HTTP trace endpoint; defaults to http://localhost:4318/v1/traces
• OTEL_EXPORTER_OTLP_HEADERS — optional OTLP authentication headers supplied by a hosted tracing provider; keep this value secret
• E2B_API_KEY
• E2B_SANDBOX_TEMPLATE

Client-side variables:

• NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY
• NEXT_PUBLIC_CLERK_SIGN_IN_URL
• NEXT_PUBLIC_CLERK_SIGN_UP_URL
• NEXT_PUBLIC_CLERK_AFTER_SIGN_IN_URL

Development

Install dependencies:

pnpm install

Run the app locally:

pnpm dev

Adding an OpenRouter agent model

Before adding a model to AGENT_MODELS:

1. Check its supported_parameters in OpenRouter's public /api/v1/models metadata.
2. Confirm whether it supports both tools and structured_outputs.
3. Set supportsStrictToolArguments explicitly in the model configuration.
4. Run pnpm test -- src/lib/__tests__/agent-models.test.ts src/server/ai/providers/__tests__/tool-strictness.test.ts.

Unknown models default to non-strict tool arguments. Local Zod validation remains required even when OpenRouter strict tool arguments are enabled.

Agent tracing with Jaeger

Start the local Jaeger service:

docker compose up -d jaeger

Run the app with pnpm dev, then complete an agent request. Open http://localhost:16686, select the inlaya-agent service, choose Find Traces, and open the sandbox_agent.run trace.

The local Jaeger service accepts OTLP/HTTP traces on port 4318 and stores them in memory, so its traces are cleared when the container is removed.

To return temporarily to terminal output instead of Jaeger, set:

OTEL_TRACES_EXPORTER=console

Useful commands:

• pnpm build Production build. This is the most reliable verification command in this repo.
• pnpm typecheck Run TypeScript without emitting files.
• pnpm db:migrate Create and apply Prisma development migrations.
• pnpm db:generate Regenerate Prisma client types.
• pnpm db:push Push schema changes without creating a migration.
• pnpm db:studio Open Prisma Studio.

Database

The database schema lives in prisma/schema.prisma.

For a human-readable walkthrough of the models and why they exist, see docs/database.md.

Architecture

For the overall app structure, API layout, and sandbox lifecycle, see docs/architecture.md.

Tool Contracts

Canonical developer-facing tool contracts live in docs/tools.md.

• docs/tools.md Canonical contracts for sandbox tools, including glob_files and search_code.

Troubleshooting

• pnpm build is more trustworthy than pnpm typecheck when .next/types is stale.
• Some TypeScript errors in this repo disappear after a successful build regenerates Next artifacts.
• Sandbox state is now persisted per project in Prisma, but the live connected E2B session still lives in memory while the server process is alive.

Contributing

If you change the Prisma schema, run:

pnpm db:migrate

Before shipping changes, prefer verifying with:

pnpm build
pnpm typecheck