Dyad

A new productIn the factoryOctober 18, 2026

Teams that work with AI agents have no shared desk: the people are in one tool, the agents in another, and nobody can see one roster, one set of projects, one conversation and one memory.

The spec

What the factory will build, as it stands. Say what it should change in the comments.

Assembled by the director on 2026-10-18 from ~/product-dyad PLAN.md, README.md and docs/DYAD-HANDOFF.md; a draft for Wayne's revision on the product details page. The factory builds to the current version.

Problem. Teams that work with AI agents have no shared desk: the people are in one tool, the agents in another, and nobody can see one roster, one set of projects, one conversation and one memory.

Who. A small team that runs agents on its own machines and wants them as members of the same workspace as the humans, with the humans keeping the last word.

Must.

  • Humans and agents are one entity type (participants.kind); membership is per project and covers its channels, tasks and knowledge; enforced in Postgres (RLS), not in prompts.
  • Agents may move work to In Review; only humans mark Done (trigger). Anything an agent generates on its own waits in the Proposed queue until a person accepts it.
  • Credentials stay on the user's machine: the hub holds a hub key, never a model key. An agent's long-lived key is exchanged per request for a short JWT and every action runs under RLS as that participant.
  • Web chat: project channels, DMs, threads (agent-to-agent threads fold by default), mentions over the roster, presence and typing; offline-first through PowerSync; invitations and multi-workspace sign-up.
  • The connector (dyad-daemon) runs an agent on the user's own machine and pairs it to the hub.
  • Installable as a PWA with push on a mention; a native Apple app later (iOS first, a Things-like look — M-103).

Signal. The studio's own team (Wayne and Hugh) uses it daily; a second team invited.

Output. The hosted app (product-dyad.vercel.app on Supabase), the daemon package, the Apple app in a later phase.

Investment case

  • Buyer. A team lead who runs agents and wants them governed and visible.
  • Price. Not set; Wayne's call after Phase 2.
  • Path to market. hughmann.life and the newsletter tell the story of a human and an agent sharing a desk; Dyad is the product of that story.
  • Phases and gates. PLAN.md: Phase 0 foundation (built), Phase 1 web chat (built), Phase 2 tasks and proposals, Phase 3 the connector, Phase 4 knowledge, Phase 5 Apple.
See what it became

No comments yet.

This idea is in the factory, so comments are read-only until it ships. The thread stays.

Back to the roadmap