Place Your First Node
A node on the org chart represents a role — CEO, CMO, CTO, Sales VP, Operations, an engineering lead, a researcher, whatever the org needs. Each node is backed by its own autonomous agent.
Recommended starter: CMO
If it’s your first workspace, place a CMO node. It maps cleanly to skills that ship with Direktor (market-company, ad-campaigns, sell-online) and gives you quick wins like drafting posts, launching campaigns, or researching positioning.
Steps
- On the canvas, click + Add Node (or drag from the palette on the left).
- Pick a role from the list, or type a custom role name.
- Drop it on the canvas. If you already have nodes placed, connect it to a parent (e.g. CMO reports to CEO) by dragging a line.
- Click the node to open its Chat Panel.
- (Optional) Give it a starting context: “You are the CMO of Acme Labs, a B2B SaaS startup selling inventory-management tooling to SMB retail. Our primary channel is LinkedIn.”
Starting context is saved as the agent’s permanent system prompt — it colors every future response without you having to repeat it.
Node anatomy
Each node card shows:
- Avatar + role name — visual identity.
- State dot — green (working), grey (idle), yellow (waiting on you), red (blocked).
- Current task — one-line summary of what the agent’s doing right now.
- Activity preview — last few timeline events.
Double-click the card to open the full Chat Panel where you converse with the agent.
Sibling + boss relationships
Direktor’s agents can message each other. If you place a CTO node as a sibling to the CMO, the CMO can send_message_to_peer('cto', ...) when a task needs engineering input. Structure matters — a flat chart of peers behaves differently than a hierarchy with approval gates. Pick what matches your real org.