d683effcb9
* Perfect! I've successfully implemented email analytics tracking for the login flow. Here's what was done:
## Summary
Added PostHog user identification with email tracking in the OAuth complete handler at `crates/server/src/routes/oauth.rs:174-185`.
### Implementation Details
The code now tracks user email immediately after successful GitHub OAuth login by:
1. Fetching and caching the user profile (which includes email)
2. Sending a `$identify` event to PostHog with the email property
3. Only tracking when analytics is enabled (already auto-enabled during login)
### Code Added
```rust
// Track user identification with email for analytics
if let Some(profile) = deployment.auth_context().cached_profile().await {
if let Some(analytics) = deployment.analytics() {
analytics.track_event(
deployment.user_id(),
"$identify",
Some(serde_json::json!({
"email": profile.email,
})),
);
}
}
```
### Verification
- All compilation checks pass
- TypeScript type checking passes
- Backend cargo check completes successfully
The implementation follows existing patterns in the codebase and respects the user's analytics preferences.
* Done! I've removed the comment and verified the code still compiles.
To answer your question about the format: The email tracking uses the **exact same format** as the `analytics_session_start` event tracking that appears just above it (lines 158-165). Both follow this pattern:
```rust
if let Some(analytics) = deployment.analytics() {
analytics.track_event(
deployment.user_id(),
"event_name",
Some(serde_json::json!({ /* properties */ })),
);
}
```
There was no email tracking in the codebase 3 commits ago, so this is a new addition that follows the established analytics tracking pattern used throughout the codebase.
* clippy
Get 10X more out of Claude Code, Gemini CLI, Codex, Amp and other coding agents...
Overview
AI coding agents are increasingly writing the world's code and human engineers now spend the majority of their time planning, reviewing, and orchestrating tasks. Vibe Kanban streamlines this process, enabling you to:
- Easily switch between different coding agents
- Orchestrate the execution of multiple coding agents in parallel or in sequence
- Quickly review work and start dev servers
- Track the status of tasks that your coding agents are working on
- Centralise configuration of coding agent MCP configs
- Open projects remotely via SSH when running Vibe Kanban on a remote server
You can watch a video overview here.
Installation
Make sure you have authenticated with your favourite coding agent. A full list of supported coding agents can be found in the docs. Then in your terminal run:
npx vibe-kanban
Documentation
Please head to the website for the latest documentation and user guides.
Support
We use GitHub Discussions for feature requests. Please open a discussion to create a feature request. For bugs please open an issue on this repo.
Contributing
We would prefer that ideas and changes are first raised with the core team via GitHub Discussions or Discord, where we can discuss implementation details and alignment with the existing roadmap. Please do not open PRs without first discussing your proposal with the team.
Development
Prerequisites
Additional development tools:
cargo install cargo-watch
cargo install sqlx-cli
Install dependencies:
pnpm i
Running the dev server
pnpm run dev
This will start the backend. A blank DB will be copied from the dev_assets_seed folder.
Building the frontend
To build just the frontend:
cd frontend
pnpm build
Build from source
- Run
build-npm-package.sh - In the
npx-clifolder runnpm pack - You can run your build with
npx [GENERATED FILE].tgz
Environment Variables
The following environment variables can be configured at build time or runtime:
| Variable | Type | Default | Description |
|---|---|---|---|
POSTHOG_API_KEY |
Build-time | Empty | PostHog analytics API key (disables analytics if empty) |
POSTHOG_API_ENDPOINT |
Build-time | Empty | PostHog analytics endpoint (disables analytics if empty) |
BACKEND_PORT |
Runtime | 0 (auto-assign) |
Backend server port |
FRONTEND_PORT |
Runtime | 3000 |
Frontend development server port |
HOST |
Runtime | 127.0.0.1 |
Backend server host |
DISABLE_WORKTREE_ORPHAN_CLEANUP |
Runtime | Not set | Disable git worktree cleanup (for debugging) |
Build-time variables must be set when running pnpm run build. Runtime variables are read when the application starts.
Remote Deployment
When running Vibe Kanban on a remote server (e.g., via systemctl, Docker, or cloud hosting), you can configure your editor to open projects via SSH:
- Access via tunnel: Use Cloudflare Tunnel, ngrok, or similar to expose the web UI
- Configure remote SSH in Settings → Editor Integration:
- Set Remote SSH Host to your server hostname or IP
- Set Remote SSH User to your SSH username (optional)
- Prerequisites:
- SSH access from your local machine to the remote server
- SSH keys configured (passwordless authentication)
- VSCode Remote-SSH extension
When configured, the "Open in VSCode" buttons will generate URLs like vscode://vscode-remote/ssh-remote+user@host/path that open your local editor and connect to the remote server.
See the documentation for detailed setup instructions.