DevIsland

Project: DevIsland

Tagline: Fleet Radar: a local-first control tower for parallel coding agents

Author's Claim: A macOS menu-bar and notch-overlay app that provides coordination signals for developers using multiple parallel coding agents working in separate Git worktrees.

What Changed: The project is a self-contained, local-first tool built for developers who use AI coding agents in parallel. It introduces a "Fleet Radar" UI to visualize active worktrees and agent sessions on a developer's Mac, with an emphasis on avoiding cloud data transmission.

Single Most Important Open Question: Does the author’s own description indicate any evidence of real-world usage or adoption by developers using parallel coding agents?

The description states that DevIsland is a macOS menu-bar and notch-overlay app for managing coding-agent activity. It includes a feature called Fleet Radar, which:

• Discovers active worktrees and live agent sessions on the developer’s Mac.
• Shows branch state, modified files, overlap warnings, and priority work in one Session Center view.
• Allows developers to jump directly from a Fleet card to the relevant terminal.
• Keeps repository metadata local—no source code or worktree data is sent to a cloud service.

Inference: The app appears to be a developer tool focused on improving coordination when using multiple parallel coding agents, particularly in a local-first environment. It is not described as a SaaS product or platform but rather a desktop application.

The author positions DevIsland as a local-first control tower for developers working with parallel coding agents, aiming to solve coordination challenges that arise from using multiple worktrees.

• The project claims to address the problem of "losing track of which branch owns a change, where files overlap, and which terminal needs attention."
• It emphasizes local-first design, stating that no data is sent to cloud services.
• The author also notes that the tool aims to provide early warnings (e.g., shared file paths) rather than definitive conflict signals.

Inference: The positioning is focused on developer workflow optimization, not a general-purpose AI or collaboration platform. It’s a niche tool for developers using AI agents in parallel worktrees, with an emphasis on privacy and local processing.

The description states that DevIsland is built for developers who use parallel coding agents working in separate Git worktrees.

• The app targets users of AI coding tools (e.g., GPT-based agents) who are managing multiple concurrent development tasks.
• It is designed to be used on a MacOS environment, specifically with menu-bar and notch-overlay UIs.
• The tool is not described as targeting teams or organizations, but individual developers.

Inference: The ICP is likely technical professionals working in AI-assisted development environments, particularly those using tools like GPT-based agents in parallel worktrees. It’s a very narrow use case.

The description does not mention any pricing model or business model.

• No information is provided about monetization, subscriptions, licensing, or sales channels.
• The project is described as a hackathon submission, not a commercial product.

Inference: There is no evidence of a business model or pricing structure. The tool appears to be an experimental or prototype-level solution.

The author states that:

• Fleet Radar is implemented in Swift and SwiftUI.
• It is part of DevIsland, a macOS app with menu-bar and notch-overlay UIs.
• The system models each worktree as a local session context.
• Overlap signals are derived from modified paths.
• Card actions connect to terminal focus.
• The demo uses three concurrent worktrees, two of which modify the same file.

Inference: The technical stack is standard for macOS development, and the tool is built with local-first principles. It appears to be a functional prototype or proof-of-concept, not a production-ready product.

The description does not provide any evidence of traction, adoption, or user feedback.

• DevIsland is described as a hackathon submission.
• No mention of users, customers, or real-world usage.
• The project has no revenue, headcount, or funding data.

Inference: There is no evidence of product-market fit or real-world usage. It is likely an early-stage prototype or experimental tool.

The description does not provide any information about competitors or market context.

• No mention of existing tools for managing parallel coding agents.
• No comparison to other developer productivity tools or AI-assisted development platforms.

Inference: The competitive landscape is unknown. It’s unclear whether similar tools exist, and the author does not reference them.

• No evidence of real-world usage or adoption — the tool is described as a hackathon submission.
• Limited scope — it only works on macOS and for developers using parallel worktrees.
• Unproven business model — no indication of monetization or scalability.
• Self-reported only — all claims are unverified, and there’s no third-party validation.

Inference: The project is experimental, with no demonstrated traction. It may not be ready for commercial use or investment.

1. What is the actual problem you're solving, and how many developers are currently facing it?
2. Have you tested this tool with real users in parallel coding agent workflows?
3. Is there a plan to expand beyond macOS or support other platforms?
4. How do you intend to monetize this tool if it remains local-first?
5. What is the long-term vision for DevIsland beyond the hackathon?