Inframe

Next.js app plus a token-gated TUI client (frame) for remote tester access.

Local app development

npm run dev

TUI (local)

npm run frame

TUI (remote, token-gated)

The TUI can connect to a deployed app and require a shared tester token.

Set these env vars in your local .env.local before launching frame:

FRAME_API_BASE_URL=https://your-deployment.vercel.app
FRAME_ACCESS_TOKEN=shared-tester-token
FRAME_REQUIRE_ACCESS_TOKEN=true

Optional path overrides:

FRAME_CHAT_PATH=/api/cli/chat
FRAME_VERIFY_PATH=/api/cli/verify

Then run:

npm run frame

Server env required on deployment

In Vercel project env (Production/Preview as needed):

INFRAME_API_KEY=...
FRAME_TEST_TOKEN=shared-tester-token

FRAME_TEST_TOKEN is what you give testers as FRAME_ACCESS_TOKEN.

Global install for testers

Testers can run the TUI globally from this repo once published or from git:

npm i -g <package-or-repo>
frame

If pnpm is not on PATH in PowerShell, use npx pnpm ... for repo maintenance commands.

Deployment model recommendation

• Use a dedicated Vercel project for the TUI backend (tui-ink-agent-runtime).
• Keep your main app (frame-ai) separate unless you intentionally want shared env/risk.
• Separate projects are cleaner for tester tokens, rollback, and access control.