repository·main·Indexed 12 days ago
https://github.com/dyad-sh/dyadA free, local, open-source AI application builder for Mac and Windows. Dyad allows developers to build applications on their own machines using their own AI API keys (BYOK), providing a private, vendor-neutral alternative to cloud-based AI coding tools. The ecosystem includes component tagging loaders for Next.js and Vite, as well as PostgreSQL schema utilities like pg-schema-classifier and ts-pg-schema-diff.
Dyad is a local, open-source AI application builder designed to run on your machine. It provides a development experience similar to Lovable, v0, or Bolt, but emphasizes privacy, speed, and user control.
Key characteristics include:
The development roadmap for Chat History Search includes the following planned enhancements:
referencedApps paths).A successful implementation of the Dynamic Models architecture must meet these criteria:
api.dyad.sh when available.language_model_constants.ts upon API failure or invalid data.Dyad provides a suite of six Git tools designed for local agents. These tools are categorized into read-only tools (available in ask and plan modes) and a state-changing tool (available only in writable agent mode).
Read-only tools:
git_status: View branch state and file statuses (staged, unstaged, untracked, conflicted).git_diff: View changes between the index, working tree, or HEAD.git_log: View commit history.git_show_commit: View commit metadata and patches.git_show_file: View historical file content.State-changing tool:
git_restore_file: Restores a single file from a specific revision into the working tree. This tool overwrites dirty or untracked content but does not change the Git index (staged changes remain staged).Dyad is transitioning from a desktop-only Electron application to a multi-platform ecosystem. The strategy involves maintaining the Desktop app as a free, local, open-source flagship, while introducing a Web version (browser-based, freemium model) and a Mobile/PWA version (for monitoring and lightweight interaction).
| Feature | Desktop | Web | Mobile/PWA |
|---|---|---|---|
| Primary Use Case | Full creation (chat, code, preview, deploy, git, local models) | Full creation (cloud-backed, minus local-only features) | Monitoring, reviewing, lightweight chat |
| Layout | Three-panel: sidebar + chat + preview | Three-panel: sidebar + chat + preview | Single-panel with bottom tab navigation |
| Code Editing | Monaco editor | Monaco editor | Read-only code viewer |
| Preview | Local dev server | Remote container | Full-screen with toggle |
| Sync Method | Local files | GitHub-based sync | GitHub-based sync |
To support web and mobile platforms, Dyad moves from a local Electron IPC model to a standalone Node.js server model.
The Model:
Key Implementation Details:
onChunk, onEnd) are transformed into Server-Sent Events (SSE).createClient() function in src/ipc/contracts/core.ts serves as the single point of abstraction to swap ipcRenderer.invoke() for fetch() depending on the platform.// IPC Pattern (Desktop)
ipcMain.handle("create-app", handler)
ipcRenderer.invoke("create-app", data)
// HTTP Pattern (Web)
POST /api/create-app
fetch("/api/create-app", { body: data })Dyad supports Convex as a reactive backend platform. Unlike traditional databases, Convex is treated as a 'backend'. The integration uses a CLI-driven approach via npx convex for deployment operations and reads convex/schema.ts directly for schema introspection.
Key Integration Details:
npx convex deploy within the app directory.convex/schema.ts file.concurrently to run both the Vite dev server and npx convex dev simultaneously.apps table, rather than in global settings.Important Note: Convex requires an active internet connection for development; offline development is not supported.
Dyad manages tabs and windows with specific lifecycle behaviors:
Cancel or Stop to terminate such work.TabInstanceId and belongs to a WindowSessionId.When installing packages with build scripts not in Dyad's curated allow-list (e.g., core-js), pnpm defaults to skipping these builds. Under pnpm 11's strictDepBuilds: true setting, a standard pnpm install will fail with ERR_PNPM_IGNORED_BUILDS (exit 1) if these builds are not explicitly handled.
To prevent broken builds in exported repositories (Vercel, Netlify, CI) or during Dyad Rebuild operations, Dyad implements an Auto-Deny mechanism:
.modules.yaml to identify packages that were implicitly ignored during the initial install.pkg: false decision in the pnpm-workspace.yaml file under the allowBuilds map. This entry is placed outside the Dyad-managed block and includes a Dyad marker.ERR_PNPM_IGNORED_BUILDS error and the pnpm warning, ensuring that subsequent pnpm install commands (without special Dyad flags) succeed while maintaining the security posture of skipping unapproved build scripts.Note on Rebuilds: A standard pnpm install on an "already up to date" environment exits 0 and does not re-evaluate build scripts. To force a previously skipped build to run, you must use pnpm rebuild <pkg>.
# Example of what Dyad records in pnpm-workspace.yaml
allowBuilds:
# dyad-managed-block-start
# ... existing allowed builds ...
# dyad-managed-block-end
# dyad-auto-deny-marker
core-js: falseDyad uses a namespace strategy where each translation file represents a specific feature area (a namespace). This allows for manageable file sizes and lazy-loading of translations for specific routes.
Common namespaces include:
common: Buttons, generic labels, navigation.settings: Settings page sections.chat: Chat UI elements.home: Home page and app lists.errors: Toast messages and error dialogs.hub: Marketplace/library.integrations: Connector-specific strings (GitHub, Supabase, etc.).The chat-stream implementation relies on the following settled assumptions (from G1a):
StreamState is the sole authority for streaming status.