Connect Projects with Project Ecosystems
This guide is currently available in English.
A Project Ecosystem is a permanent connection between related projects in Kaiju Hub AI. It tells the app and its AI agents that separate desktop, web, and mobile codebases belong to one product. Each project keeps its own files and framework, while shared objectives, member responsibilities, paths, and contracts give AI the context it needs to coordinate changes across the whole product.
Start a new Project Ecosystem
From Project Hub, click New Project and choose Ecosystem. Enter a workspace name and choose its parent folder. Project Ecosystems are a Pro workflow and require a supported local CLI builder such as Claude Code, Codex, Gemini CLI, or Grok CLI.
Describe the product and choose its apps
Write one shared product objective, then add two to four apps from Desktop, Mobile, and Web. Give every app a unique name, framework, responsibility, and app-specific description. For a classified-ads product, for example, the web app, mobile app, and desktop app can all create and browse the same listings while each keeps its own platform-specific interface.
Connect one shared backend
Enable Supabase when the member apps should use the same authentication, database, storage, or realtime data. Select a Supabase organization and project, create one during setup, or use manual project values. Kaiju Hub AI writes the shared configuration into the ecosystem so every generated member can be built against the same backend.
Link projects you already have
On the Project Hub dashboard, open Edit Project for any member and select the Ecosystem tab. Select 2–50 existing projects, describe each member's responsibility, and wait for the edit to save automatically. The current project stays selected. These connections describe a shared product; dashboard groups simply organize your project list. Linking existing projects does not move their folders into a newly generated workspace.
Join an existing ecosystem or edit it from mobile
For an unlinked project, select a member of an existing ecosystem to join that ecosystem with all its members. Projects in another ecosystem are locked when you are already editing a different ecosystem. On mobile, touch and hold a project, choose Ecosystem connections, select members and edit Project descriptions, then tap Save. Desktop membership edits save automatically; mobile edits require Save.
Reach the whole ecosystem from one favorite
While viewing any member, add it to the five project favorites in the desktop header. Kaiju Hub AI shows the project icon automatically when one is available and uses the favorite number as a fallback. Hover the shortcut to see its linked desktop, web, mobile, and service members, then choose any member to jump straight to it. One favorite can be the entry point to an entire product, leaving the other header slots free for other projects or ecosystems.
Let AI coordinate changes across members
When you start an AI task from any ecosystem member, Kaiju Hub AI automatically includes the shared objective and the titles, descriptions, roles, types, IDs, and local paths of sibling projects. If a change in one app requires a database, contract, API, or UI update in another, the agent can inspect and update the affected members together. State the product-level outcome you want, and review the coordinated changes before shipping.
Review generation results and recover failed members
When creating a new ecosystem, check each member's result before moving on. If one member fails, the ecosystem workspace and successful projects are kept; review the failed member cards and the reported error before retrying work. A Supabase CLI linking warning also needs attention even when project creation succeeds. Validate shared workflows with the required member apps running together.