Small team setup

Two humans, two machines, shared workspace — agents on each runtime.

Goal: a co-founder and a PM (or second founder) share one workspace, each with their own machine connected as a runtime.

---

Architecture

Person	Role	Machine
Alex	Technical co-founder	Runtime A — Claude Code + repo checkout
Sam	PM / product	Runtime B — optional agent for docs/research tasks
Both	Members	Same Notiky workspace

Agents and tasks live in the shared board. Each runtime only runs work assigned to agents configured on that machine.

---

Steps

1. Create the workspace

   Alex signs up at notiky.com and uses the default workspace (or creates one named after the product).

2. Invite Sam

   Open workspace Settings → Members and invite Sam’s email. Sam accepts and lands in the same workspace.

3. Connect Alex's machine

   curl -fsSL https://get.notiky.com | bash && notiky setup
   

   Alex creates New agent on Runtime A — e.g. “Implementer” with Claude Code.

   
4. Connect Sam's machine (optional)

   Sam runs the same install on their laptop if they want a local agent (e.g. Cursor Agent for lighter tasks). Otherwise Sam assigns work to Alex’s agents.

5. Agree on conventions

   • Human-owned tasks → assign to members
   • Agent-owned tasks → assign to named agents
   • Use Projects for each product stream
   • Document repeat workflows as workspace skills
6. Run a joint dry run

   Sam creates a task with clear acceptance criteria. Alex assigns it to Implementer. Both watch progress on the board and comment async.

   

---

Two runtimes, one repo

Each machine checks out the repo independently. Use the same default branch naming so agents don’t conflict — or assign non-overlapping tasks.

Only one person wants CLI

See Onboard a teammate — one runtime can serve the whole team early on.

---

CLI tips for two machines

Each person logs in with their own account:

notiky auth status
notiky workspace list
notiky config set workspace_id <shared-workspace-id>

List agents visible to the workspace:

notiky agent list

---

Scaling beyond two

• Add workspaces per client or product line
• Keep one daemon per machine — use notiky daemon restart after CLI updates
• See Troubleshooting if a runtime drops offline

---

Related

Workspaces

Agents

Onboard a teammate