This is a Next.js project bootstrapped with create-next-app.

Model Provider Config

The chat backend supports both OpenAI and Anthropic models.

Set these in .env.local:

# optional: force provider ("openai" | "anthropic")
AI_PROVIDER=openai

# optional: provider-agnostic model override (e.g. gpt-4.1-mini or claude-3-7-sonnet-latest)
AI_MODEL=

# OpenAI
OPENAI_API_KEY=
OPENAI_MODEL=gpt-4.1-mini
OPENAI_REASONING_SUMMARY=auto
OPENAI_REASONING_EFFORT=medium

# Anthropic
ANTHROPIC_API_KEY=
ANTHROPIC_MODEL=claude-3-7-sonnet-latest

Routing behavior:

• AI_PROVIDER=anthropic uses Anthropic.
• AI_PROVIDER=openai uses OpenAI.
• Without AI_PROVIDER, claude-* models route to Anthropic; everything else routes to OpenAI.

Split Deployment: Vercel Frontend + Render Chat

You can run chat execution on Render while keeping the Next.js frontend on Vercel.

Frontend (Vercel) env

Set these on Vercel:

NEXT_PUBLIC_CHAT_API_BASE_URL=https://chat.rowsncolumns.ai
NEXT_PUBLIC_CHAT_API_PATH=/chat

When NEXT_PUBLIC_CHAT_API_BASE_URL is set, the browser calls Render chat directly with a bearer token from Neon auth. The token used is the Neon session token (getSession().session.token), and Render validates it via Neon /get-session. Client payload includes only threadId, docId, and message.

Chat service (Render)

Start command:

yarn chat:render

Render env vars:

PORT=10000
CHAT_RENDER_PATH=/chat
CHAT_SERVER_TIMEOUT_MS=1800000
CHAT_ALLOWED_ORIGINS=https://rowsncolumns.ai,https://www.rowsncolumns.ai,https://<your-vercel-domain>
CHAT_MODEL=gpt-5.4
CHAT_PROVIDER=openai
CHAT_REASONING_ENABLED=false
# Optional fixed server-side instructions (never sent by browser)
CHAT_SYSTEM_INSTRUCTIONS=

# Required auth backend URL (same value used by Next.js auth server)
NEON_AUTH_BASE_URL=

# Reuse existing app runtime envs:
DATABASE_URL=
SHAREDB_URL=
OPENAI_API_KEY=
ANTHROPIC_API_KEY=
LANGCHAIN_API_KEY=
LANGCHAIN_TRACING_V2=
LANGCHAIN_PROJECT=

Notes:

• CHAT_ALLOWED_ORIGINS is enforced via CORS.
• Keep DATABASE_URL and SHAREDB_URL pointing to the same production backends used by the frontend app.
• The legacy /api/chat route on Vercel can remain as fallback.

Credits + Admin Refill

Users receive daily credits with a non-accumulating reset to 30.

Run credits migration:

yarn db:migrate:credits

Optional admin allowlists (comma-separated) for manual refill access in Settings:

RNC_ADMIN_USER_IDS=
RNC_ADMIN_EMAILS=

ShareDB On Postgres (Neon)

ShareDB server storage uses PostgreSQL.

Set in .env.local:

# Recommended: Neon Postgres URL
SHAREDB_DATABASE_URL=

# Optional fallback used when SHAREDB_DATABASE_URL is missing
DATABASE_URL=

# ShareDB websocket server port
SHAREDB_PORT=8080

# Optional: set to false for local non-SSL Postgres
SHAREDB_REQUIRE_SSL=true

Run ShareDB table migration:

yarn db:migrate:sharedb

Document Ownership Mapping

Track document ownership (doc_id -> user_id) in Neon:

yarn db:migrate:documents
yarn db:migrate:document-shares

Auth Cookie Compatibility (Excel Taskpane)

Excel taskpane runs inside a third-party iframe, so auth cookies must preserve upstream SameSite=None; Secure attributes (and optionally Partitioned) for OAuth/session continuity.

This app applies compatibility at app boundaries (not in node_modules):

• Utility: lib/auth/cookie-compat.ts
• API boundary: app/api/auth/[...path]/route.ts
• Middleware boundary: proxy.ts

Compatibility rules:

• Default (web Safari): normalize Neon auth cookies for Safari compatibility
  • remove Partitioned
  • rewrite SameSite=None to SameSite=Lax
• Taskpane iframe flows: preserve upstream Set-Cookie attributes unchanged
  • enabled via cookieCompat=preserve on callback URLs

Notes:

• /auth/callback remains simple (handles explicit OAuth error params; otherwise redirects to redirectTo)
• OAuth verifier exchange remains middleware-driven
• No polling/retry logic and no SDK monkey patching

Quick validation:

# local
curl -i -X POST 'http://localhost:3000/api/auth/sign-in/social' \
  -H 'content-type: application/json' \
  --data '{"provider":"google","callbackURL":"/auth/callback?redirectTo=%2Fdoc","disableRedirect":true}'

# production
curl -i -X POST 'https://rowsncolumns.ai/api/auth/sign-in/social' \
  -H 'content-type: application/json' \
  -H 'origin: https://rowsncolumns.ai' \
  --data '{"provider":"google","callbackURL":"/auth/callback?redirectTo=%2Fdoc","disableRedirect":true}'

Expected Set-Cookie for Neon auth cookies:

• Web Safari flow: contains SameSite=Lax, does not contain Partitioned
• Taskpane flow (cookieCompat=preserve): preserves upstream attributes exactly

Getting Started

First, run the development server:

npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev

Open https://localhost:3000 with your browser to see the result. OAuth sign-in (especially Safari) requires secure cookies, so dev now starts with HTTPS by default. Use https://localhost:3000.

If you need plain HTTP for debugging, run:

yarn dev:http

You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.

This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.

Learn More

To learn more about Next.js, take a look at the following resources:

• Next.js Documentation - learn about Next.js features and API.
• Learn Next.js - an interactive Next.js tutorial.

You can check out the Next.js GitHub repository - your feedback and contributions are welcome!

Deploy on Vercel

The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.

Check out our Next.js deployment documentation for more details.