8000 GitHub - anantjain-xyz/wallie: Linear clone with coding agents. Built in early 2025. Predecessor to anantjain-xyz/wallie-dev. · GitHub
[go: up one dir, main page]

Skip to content
This repository was archived by the owner on Oct 10, 2026. It is now read-only.
anantjain-xyzPublic archive

About

Linear clone with coding agents. Built in early 2025. Predecessor to anantjain-xyz/wallie-dev.

Resources

Security policy

Stars

0 stars

Watchers

1 watching

Forks

Repository files navigation

Wallie

Issue tracking and project management with GitHub and coding agent integrations, built with React, TypeScript, Hono, Clerk, and Supabase.

Status

This project is no longer maintained and is preserved as a reference. No support, security updates, or ongoing development are planned. Fork it if you want to continue development.

Review the known security limitations before running or deploying it. The locked dependencies have known vulnerabilities, and the legacy upload flow requires changes to keep storage credentials on the server.

Setup

Use pnpm 10.15.0 (pinned in package.json). Local Supabase also requires the Supabase CLI and Docker.

pnpm install

Create a .env file based on the .env.example file and set the environment variables:

cp .env.example .env

You can get the Clerk API keys from the Clerk dashboard.

Run

# Start the API server (port 3003 by default)
pnpm api-server

# Optionally start cron worker
pnpm cron-server

Start supabase

supabase start

If testing webhooks from GitHub to your local machine, expose port 3003 and update your GitHub App settings to use the exposed URL for the webhook and callback:

tailscale funnel 3003

Now start the dev server for the frontend app:

pnpm dev

When you're done, stop Supabase:

supabase stop

If you write migrations, you can apply them by resetting the Supabase db:

supabase db reset

Supabase Clients & Env Vars

Wallie uses two separate Supabase clients with different env vars, one for the frontend and one for server-side Hono services:

  • Frontend client

    • File: src/supabase.ts
    • Env: VITE_SUPABASE_URL, VITE_SUPABASE_ANON_KEY
    • Behavior: uses the anon key and fetch-time token provider to forward a Clerk JWT for RLS. No service role key is ever exposed to the browser.
  • Server client

    • File: servers/supabase.ts
    • Env: SUPABASE_URL, SUPABASE_SERVICE_ROLE_KEY (required; no anon fallback)
    • Behavior: uses the service role key for privileged operations needed by webhooks and background jobs (e.g., GitHub/Stripe handlers, cron tasks).

Add these variables to your .env (see .env.example). The frontend VITE_* vars are only used in the browser app, while the server SUPABASE_* vars are only loaded by Node processes.

GitHub App Integration

Wallie supports GitHub App integration for creating pull requests directly from issues.

Create a GitHub App

  1. Go to https://github.com/settings/apps/new to create a new GitHub App.
  2. Configure:
    • Name: "Wallie" (or your preferred name)
    • Homepage URL: your application's URL
    • Callback URL: ${GITHUB_CALLBACK_URL} (from your .env)
    • Setup URL: https://your-app-domain.com/settings/github (optional convenience)
    • Webhook URL: https://your-api-server-domain.com/webhook/github
    • Webhook Secret: a secure random string
  3. Permissions:
    • Repository permissions:
      • Contents: Read & write
      • Pull requests: Read & write
      • Metadata: Read-only
    • Organization permissions (optional):
      • Members: Read-only
  4. Generate and download the private key for your GitHub App.
  5. Note your GitHub App ID, App slug/name, and Client credentials.

Environment Variables

Add the following to your .env:

# Frontend URL for post-install redirects
FRONTEND_URL=http://localhost:5173

# GitHub App Configuration
GITHUB_APP_NAME=your_app_slug_name   # e.g., wallie
GITHUB_CALLBACK_URL=http://localhost:3003/callback
GITHUB_APP_ID=your_github_app_id
GITHUB_APP_PRIVATE_KEY="-----BEGIN RSA PRIVATE KEY-----\n...your multi-line private key...\n-----END RSA PRIVATE KEY-----"
GITHUB_APP_WEBHOOK_SECRET=your_github_app_webhook_secret

Notes:

  • GITHUB_APP_NAME is required for generating the install URL (/prepare-install).
  • The API server reads FRONTEND_URL, GITHUB_CALLBACK_URL, GITHUB_APP_ID, GITHUB_APP_PRIVATE_KEY, and GITHUB_APP_WEBHOOK_SECRET.

User Flow

  1. In the app Settings, click Connect GitHub (which calls /prepare-install).
  2. Complete the GitHub App installation flow; GitHub redirects to ${GITHUB_CALLBACK_URL} handled by the API server.
  3. Repositories for the installation are synced and available for selection when creating issues.
  4. When creating an issue with a selected repository, Wallie can create PRs using the installation token.

Troubleshooting

  • Installation fails: verify GITHUB_CALLBACK_URL and server reachability.
  • Repository list empty: use Refresh Repositories in Settings.
  • PR creation fails: confirm app permissions and valid installation token.
  • UUID extension errors in DB: latest migrations generate UUIDs in app code; ensure you applied current migrations.
  • Timestamp column type errors: use NOW() in SQL for timestamps when writing 5F1B raw SQL.

Checks

pnpm stylecheck
pnpm typecheck
pnpm exec vitest run
pnpm build

The unit suite excludes the live GitHub webhook smoke test. To run that test against your local API server, configure your own GitHub App webhook secret and run pnpm test:webhook.

License and credits

Wallie's original contributions are licensed under the MIT License. Inherited code and bundled fonts retain their original licenses; see third-party notices.

Wallie began as ElectricSQL's Linearlite example, built on Tuan Nguyen's Linear UI clone.

About

Linear clone with coding agents. Built in early 2025. Predecessor to anantjain-xyz/wallie-dev.

Resources

Security policy

Stars

0 stars

Watchers

1 watching

Forks

Contributors

Languages

0