f3d963c285
* Excellent! All tests pass. Let me create a summary of the changes:
## Summary
I've successfully added analytics events for organization-related actions in the Vibe Kanban codebase. Here's what was implemented:
### Changes Made
**1. `crates/server/src/routes/organizations.rs`:**
- Added `Deployment` trait import
- **Organization Created** (`create_organization` at line 90-110):
- Event: `"organization_created"`
- Properties: `org_id`, `is_personal`
- **Invitation Created** (`create_invitation` at line 134-155):
- Event: `"invitation_created"`
- Properties: `invitation_id`, `org_id`, `role`
- ✅ No sensitive data (invitee email excluded)
**2. `crates/server/src/routes/projects.rs`:**
- **Project Linked to Remote** (`apply_remote_project_link` at line 168-197):
- Event: `"project_linked_to_remote"`
- Properties: `project_id`, `link_type` ("existing" or "new")
- Tracks both linking to existing projects and creating new remote projects
- Added `link_type` parameter to distinguish between the two use cases
### Implementation Details
- All events follow the existing PostHog analytics pattern using `deployment.track_if_analytics_allowed()`
- Events are tracked **after** successful operations, **before** returning responses
- UUIDs are converted to strings with `.to_string()`
- Event names use snake_case convention
- No sensitive data (like invitee emails) is tracked
- All code compiles successfully and passes existing tests ✅
* Excellent! I've successfully removed the `link_type` parameter. Here's the updated summary of the changes:
## Final Summary
I've successfully added analytics events for organization-related actions and addressed your feedback. Here's what was implemented:
### Changes Made
**1. `crates/server/src/routes/organizations.rs`:**
- Added `Deployment` trait import
- **Organization Created** (line 90-109):
- Event: `"organization_created"`
- Properties: `org_id`, `is_personal`
- **Invitation Created** (line 124-144):
- Event: `"invitation_created"`
- Properties: `invitation_id`, `org_id`, `role`
- ✅ No sensitive data (invitee email excluded)
**2. `crates/server/src/routes/projects.rs`:**
- **Project Linked to Remote** (line 168-195):
- Event: `"project_linked_to_remote"`
- Properties: `project_id` only
- Simplified analytics - removed `link_type` parameter per your feedback
### Implementation Details
- All events follow the existing PostHog analytics pattern using `deployment.track_if_analytics_allowed()`
- Events are tracked **after** successful operations, **before** returning responses
- UUIDs are converted to strings with `.to_string()`
- Event names use snake_case convention
- No sensitive data tracked
- All code compiles successfully ✅
* Perfect! I've successfully removed the `is_personal` property. Here's the final summary:
## Updated Summary
I've successfully added analytics events for organization-related actions and incorporated all your feedback. Here's the final implementation:
### Changes Made
**1. `crates/server/src/routes/organizations.rs`:**
- Added `Deployment` trait import
- **Organization Created** (line 90-109):
- Event: `"organization_created"`
- Properties: `org_id` only
- **Invitation Created** (line 124-144):
- Event: `"invitation_created"`
- Properties: `invitation_id`, `org_id`, `role`
- ✅ No sensitive data (invitee email excluded)
**2. `crates/server/src/routes/projects.rs`:**
- **Project Linked to Remote** (line 168-195):
- Event: `"project_linked_to_remote"`
- Properties: `project_id` only
### Implementation Details
- All events follow the existing PostHog analytics pattern using `deployment.track_if_analytics_allowed()`
- Events are tracked **after** successful operations, **before** returning responses
- UUIDs are converted to strings with `.to_string()`
- Event names use snake_case convention
- No sensitive data tracked
- Minimal properties tracked per your feedback
- All code compiles successfully ✅
Get 10X more out of Claude Code, Gemini CLI, Codex, Amp and other coding agents...
We're hiring!
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.