co-mono/packages/proxy
Mario Zechner 030788140a WIP: Remove global state from pi-ai OAuth/API key handling
- Remove setApiKey, resolveApiKey, and global apiKeys Map from stream.ts
- Rename getApiKey to getApiKeyFromEnv (only checks env vars)
- Remove OAuth storage layer (storage.ts deleted)
- OAuth login/refresh functions now return credentials instead of saving
- getOAuthApiKey/refreshOAuthToken now take credentials as params
- Add test/oauth.ts helper for ai package tests
- Simplify root npm run check (single biome + tsgo pass)
- Remove redundant check scripts from most packages
- Add web-ui and coding-agent examples to biome/tsgo includes

coding-agent still has compile errors - needs refactoring for new API
2025-12-25 01:01:03 +01:00
..
src Proxy package 2025-10-05 19:02:15 +02:00
package.json WIP: Remove global state from pi-ai OAuth/API key handling 2025-12-25 01:01:03 +01:00
README.md Proxy package 2025-10-05 19:02:15 +02:00
tsconfig.json Proxy package 2025-10-05 19:02:15 +02:00

@mariozechner/pi-proxy

CORS and authentication proxy for pi-ai. Enables browser clients to access OAuth-protected endpoints.

Usage

CORS Proxy

Zero-config CORS proxy for development:

# Run directly with tsx
npx tsx packages/proxy/src/cors-proxy.ts 3001

# Or use npm script
npm run dev -w @mariozechner/pi-proxy

# Or install globally and use CLI
npm install -g @mariozechner/pi-proxy
pi-proxy 3001

The proxy will forward requests to any URL:

// Instead of:
fetch('https://api.anthropic.com/v1/messages', { ... })

// Use:
fetch('http://localhost:3001?url=https://api.anthropic.com/v1/messages', { ... })

OAuth Integration

For Anthropic OAuth tokens, configure your client to use the proxy:

import Anthropic from '@anthropic-ai/sdk';

const client = new Anthropic({
  apiKey: 'oauth_token_here',
  baseURL: 'http://localhost:3001?url=https://api.anthropic.com'
});

Future Proxy Types

  • BunnyCDN Edge Function: Deploy as edge function
  • Managed Proxy: Self-hosted with provider key management and credential auth
  • Cloudflare Worker: Deploy as CF worker

Architecture

The proxy:

  1. Accepts requests with ?url=<target> query parameter
  2. Forwards all headers (except host, origin)
  3. Forwards request body for non-GET/HEAD requests
  4. Returns response with CORS headers enabled
  5. Strips CORS headers from upstream response

Development

npm install
npm run build
npm run check