Skip to main content

Open Source

The people building Daintree.

Daintree exists because of the work below. Every merged PR on daintreehq/daintree, every commit on develop, and the people who shipped them. Thank you.

Daintree is built in Daintree. Every recent PR below was reviewed in the desktop app itself.

Contributors

Credit where it's due.

Everyone who's merged work into develop, with a short writeup of what they've been building.

Greg Priday

@gregpriday · Creator
Creator

Creator of Daintree. Built the desktop habitat from the first commit: the IPC bridge, the PtyManager, the panel grid, the review-first workflow, and the agent integration layer that sits underneath every supported CLI.

Recent focus: the fleet broadcast system, which picked up saved presets, a Pinned/Smart-Sets split, and per-target edit and skip in the broadcast popover. Crash-recovery and safe-mode now quarantine suspect panels behind a banner instead of dropping every pane on a repeat crash. The Worktrees overview gained bulk close and remove plus multi-select with keyboard navigation, settings tabs converged on a chrome-first loading pattern, GitHub stats and health polling picked up adaptive budget-aware rate-limit throttling, and the config and layout IPC namespaces moved onto defineIpcNamespace.

Works across every layer of the codebase: main process, renderer, terminal subsystem, pty-host, panel system, Review Hub, and the agent adapters. Writes the release notes, triages the issues, reviews the PRs, and keeps the brand voice consistent across the docs, blog, and marketing site.

First contribution November 2025 Merged PRs Last PR
Recent work

Jonathan Borduas

Founding collaboratorEarly contributorCodeActive

Focused on dev-preview reliability and agent configuration. The in-app browser Daintree spawns alongside a dev server is how agents see what they're actually building. It's the bridge between "code compiles" and "code works."

Recent work moved up the stack into agent setup and isolation: an agent flavor system with CCR discovery and custom flavor CRUD, a per-worktree dev server port registry that hands each worktree its own assignedUrl, and a per-worktree remote compute lifecycle so parallel sessions don't collide on shared cloud state. The --turbopack auto-injection for Next.js dev servers now gates on Next.js 15+ behind a settings toggle. Earlier work shipped an OAuth loopback flow so external auth redirects land back in the preview instead of a dead tab, plus an "Open in Browser" escape hatch when cross-origin navigations get blocked. Each fix makes the agent review loop a little tighter.

First contribution March 2026 Merged PRs Last PR
Recent work

Y. Chamare

ContributorEarly contributorDocsCode

Extended Daintree's built-in agent roster. Added Kiro CLI as a first-class agent, covering setup wizard integration, auth detection, and panel glue. Kiro users don't have to hand-roll a custom terminal recipe anymore.

Followed up with AWS SSO token support in the auth check, so Kiro users authenticating through an AWS identity center get detected correctly instead of bouncing through the setup flow on every launch. Also added Kiro to the README agent list and install section so newcomers evaluating the project can see the full agent lineup from the landing doc. Quiet, infrastructural work that makes agent onboarding invisible for a whole class of users.

First contribution April 2026 Merged PRs Last PR
Recent work

Andrew Misplon

ContributorEarly contributorCode

Fixed a regression in the CodeMirror editor theme where fontFamily was falling through to the browser default instead of the configured monospace font. Small patch, wide reach. The Review Hub, the notes panel, and every diff surface in Daintree reads through that theme, so one missing token was visible on every code view in the app.

First contribution April 2026 Merged PRs Last PR
Recent work

Devendra Mulewa

Founding collaboratorEarly contributorTestsCodeActive

Works on test-harness and CI reliability across platforms. Recent work has been stabilizing flaky end-to-end tests: gating refreshActiveWindow on the sidebar DOM being attached, guarding against null returns from getCurrentProject when switching projects, swapping in adaptive timeouts and the correct dock-item selector, and skipping Ctrl+Tab navigation tests on all Linux rather than just CI. Earlier work fixed Windows CI failures caused by path-separator and shell-quoting differences in the test harness, so the Windows leg of the matrix runs clean alongside macOS and Linux. The kind of cross-platform infrastructure work that goes invisible once it's right and loud when it isn't.

First contribution April 2026 Merged PRs Last PR
Recent work

Growth

From the first commit to now.

Every commit on develop, bucketed by week. Markers show where each contributor first merged.

Total commits

The work

Recently merged.

Merged PRs in reverse-chronological order, grouped by week. Click any row to open it on GitHub.

Recently shipped
First contributions

Contributing

If you want it in Daintree, build it.

There's no triage queue, no good-first-issue board, no contributor program. Daintree is open source and most pull requests come from people fixing or adding the thing they personally needed. The workflow below is the whole workflow.

AI-assisted PRs are welcome. Daintree is built to review them. Slop isn't, so read the code before you push it.

01

Load Daintree in your agent

Clone daintreehq/daintree and point your favorite coding agent at it — Claude Code, Codex, Gemini, OpenCode, whatever you run. The repo is a normal Electron + TypeScript codebase, so there's nothing exotic to learn first; your agent can read its way around in a few minutes, then spin up a worktree. The contributing guide has the local setup steps.

02

Build it and test it

Make the change you want. Run Daintree locally and visually test it — click through the actual UI, because Electron bugs hide from unit tests. Add unit or integration tests for the logic that matters. Even single-line fixes count: every one chips away at rough edges and helps build a habitat for AI agents that everyone can rely on.

03

Open a PR against develop

Fork, branch, and send a pull request targeting develop. Conventional-commit titles (feat:, fix:, perf:) render with color tags above, and once it merges your row lands in the first-contributions log alongside everyone else's. Set a profile picture first if you want your contribution to show up on this page.