Bring Your API Keys and Pay for What You Use.
My detailed post in Twitter about the process of development:
https://x.com/besidka_ai/status/1946685763183133001
Project board is available here.
- You are welcome to visit the production site www.besidka.com.
- Please choose any option of authentication such as Google sign in, GitHub sign in or more common way of the Email + Password flow.
- When you are authorized, please put your API keys there: www.besidka.com/profile/keys.
- You are welcome to start a new chat: https://www.besidka.com/chats/new
- PINK — Dark and light themes, both unapologetically pink
- BYOK — Bring Your Own API Key — Use your OpenAI or Google AI Studio keys and only pay for what you use. No subscriptions, no markup
- Multiple AI Models — Switch between GPT-4o, Gemini and other LLMs in one place
- Web Search — Ground AI answers with real-time web context
- Reasoning Mode — Step-by-step thinking for complex questions
- File Attachments & File Manager — Send images and PDFs, reuse files across chats
- Chat Branching — Fork a conversation mid-thread to explore a different direction
- Projects — Organize chats with shared instructions and memory
- Resumable Streams — Refresh the page and pick up right where you left off
- Chat History — Search, pin and rename past conversations
- Syntax Highlighting — Clean, readable code blocks out of the box
- No Install Required — Works in any browser, sign in and go
- Better Auth — Email/password, Google or GitHub sign-in
- Symptom: Google or GitHub social sign-in is unavailable, or Google shows
403: disallowed_useragent. - Cause: The app is opened in an embedded/in-app browser (for example Threads, Instagram, Facebook, TikTok), and OAuth providers may block these user agents.
- Resolution: Open the same page in your system browser (Chrome/Safari/Firefox) and try again with social sign-in.
- Config sanity check: Ensure your Google OAuth app has this redirect URI:
https://<your-domain>/api/auth/callback/google
Pay your attention that the project is designed to run on Cloudflare Workers. It requires additional steps to run it via Cloudflare Workers preview or deploy to the production environment.
The steps below are for local development only for the quick start and check.
Clone the repository.
git clone git@github.com:besidka/besidka.gitGo to the project directory. Install the dependencies.
cd besidka
pnpm installCopy ENV related files.
cp .dev.vars.example .dev.varsGenerate environment types for the project.
pnpm run cf-typegenPrepare drizzle migrations.
# Expected output is .drizzle/migrations/*.sql
pnpm run db:generateApply the migrations to the D1 database.
# Expected output is .wrangler/state/v3/d1/*.sqlite
pnpx wrangler d1 migrations apply DBPrepare and apply the cookie-consent database migrations. This is a separate
D1 database (CONSENT_DB) used to store consent receipts. See
docs/cookie-consent.md for details.
# Expected output is .drizzle/migrations-consent/*.sql
pnpm run db:consents:generate
pnpm run db:consents:migrateStart the development server.
pnpm run devor to start Cloudflare Workers preview server
pnpm run preview- Open http://localhost:3000 in your browser.
- Sign up http://localhost:3000/signup. Please use the Email + Password flow because you don't have prepared API keys for Google and GitHub OAuth yet. In development mode you don't need to wait for email confirmation. You have to be automatically redirected to the home page as a customer already.
- Put your own API keys here: http://localhost:3000/profile/keys
- You are welcome to start a new chat: http://localhost:3000/chats/new
- Snyk is a tool for finding and fixing vulnerabilities in your code.
# Total issues: 0
snyk code test
| Light theme | |
|---|---|
|
|
| Dark theme | |
|
|



