noHuman Management
Your noHuman team is only as good as how you work with it. This section covers everything you need to know about managing your noHumans — what they do, how to talk to them, and how to get the best results.
4.1 Understanding noHuman Roles
Each noHuman has a specialty. The roles below are organized by team template — your noHumans' roles depend on which template you chose during setup.
| Team | Leader | You talk to... | They manage... |
|---|---|---|---|
| Startup Team | CEO | CEO | Developer, Marketer, Automator |
| Dev Squad | Tech Lead | Tech Lead | Architect, Coder, QA |
| Content Factory | Content Director | Content Director | Writer, Editor, SEO |
The pattern: You (Founder) → Leader → Team → Results back to you. One conversation, full team output.
Startup Team Roles
CEO — Your chief strategist and team coordinator.
- Sets the vision and priorities for what the team works on
- Breaks down your requests into tasks and delegates to the right team member
- Reviews work from Developer, Marketer, and Automator before reporting back
- Keeps the team aligned and resolves conflicts between competing priorities
Talk to the CEO when: you want to kick off a new project, set priorities, get a status update, or need something that involves multiple team members.
Developer — Your full-stack engineer who turns ideas into working code.
- Writes, tests, and ships code across frontend and backend
- Debugs issues, refactors messy code, and reviews pull requests
- Sets up repositories, CI/CD pipelines, and development tooling
- Implements features based on specs from the CEO or requirements from the team
Talk to the Developer when: you need code written, a bug fixed, a repo set up, or anything technical built. (Usually the CEO delegates to them, but you can talk directly if needed.)
Marketer — Your growth engine for messaging, content, and audience.
- Writes marketing copy, landing pages, emails, and social media content
- Develops positioning, messaging frameworks, and go-to-market strategies
- Plans and executes campaigns across channels
- Analyzes competitors and identifies market opportunities
Talk to the Marketer when: you need copy written, a launch planned, SEO strategy, or competitive analysis. (Usually the CEO delegates to them, but you can talk directly if needed.)
Automator — Your ops specialist who keeps systems running smoothly.
- Builds automation workflows and scheduled tasks
- Monitors systems, logs, and alerts for issues
- Manages infrastructure, deployments, and DevOps tooling
- Creates scripts and integrations to eliminate repetitive work
Talk to the Automator when: you need a workflow automated, a cron job set up, systems monitored, or infrastructure managed. (Usually the CEO delegates to them, but you can talk directly if needed.)
Dev Squad Roles
Tech Lead — Your technical decision-maker and engineering coordinator.
- Makes architecture and technology decisions for the project
- Breaks down features into tasks and assigns them to Architect, Coder, and QA
- Reviews all code and designs before they're finalized
- Balances technical debt against shipping speed
Talk to the Tech Lead when: you want to start a new feature, discuss technical direction, get a project status update, or need a decision on how something should be built.
Architect — Your systems designer who plans before building.
- Designs system architecture, data models, and API contracts
- Evaluates technology choices and their trade-offs
- Creates technical specs and documentation
- Identifies scalability bottlenecks and plans solutions before they're problems
Talk to the Architect when: you need a system designed, a technical spec written, or want to evaluate different approaches to a complex problem. (Usually the Tech Lead delegates to them.)
Coder — Your implementation specialist who writes clean, working code.
- Implements features, components, and modules based on specs
- Writes clean, maintainable code following project conventions
- Handles bug fixes, refactors, and performance optimizations
- Works across the stack — frontend, backend, scripts, whatever's needed
Talk to the Coder when: you need code written, a feature implemented, or a bug squashed fast. (Usually the Tech Lead delegates to them.)
QA — Your quality gatekeeper who catches what others miss.
- Writes and runs test suites — unit, integration, and end-to-end
- Reviews code for bugs, edge cases, and security issues
- Validates that shipped features match the original spec
- Documents bugs with clear reproduction steps and severity ratings
Talk to QA when: you need tests written, a feature validated, or a bug report investigated. (Usually the Tech Lead delegates to them.)
Content Factory Roles
Content Director — Your content strategist and editorial lead.
- Plans the content calendar, topics, and publishing cadence
- Assigns writing and editing tasks to the team
- Reviews all content before it goes live for quality and brand consistency
- Tracks content performance and adjusts strategy based on results
Talk to the Content Director when: you want to plan a content strategy, start a new content project, or get a status update on what's been published and what's in the pipeline.
Writer — Your creative engine who turns ideas into compelling drafts.
- Writes blog posts, articles, newsletters, landing page copy, and social content
- Researches topics thoroughly before writing to ensure accuracy
- Adapts tone and style to match the brand voice and target audience
- Produces first drafts quickly and iterates based on editorial feedback
Talk to the Writer when: you need a draft written, an article researched, or content created for a specific channel. (Usually the Content Director delegates to them.)
Editor — Your quality control for clarity, tone, and polish.
- Reviews and revises drafts for grammar, flow, and readability
- Ensures consistency in brand voice, terminology, and formatting
- Fact-checks claims and verifies sources
- Tightens copy — cuts fluff, sharpens arguments, improves structure
Talk to the Editor when: you have a draft that needs polishing, want a second opinion on tone, or need content fact-checked. (Usually the Content Director delegates to them.)
SEO — Your search optimization specialist who makes content discoverable.
- Researches keywords, search intent, and competitive rankings
- Optimizes content for on-page SEO — titles, meta descriptions, headings, internal links
- Tracks search performance and identifies opportunities for improvement
- Advises on content topics based on what people are actually searching for
Talk to SEO when: you want content optimized for search, need keyword research, or want to understand how your content is performing in search results. (Usually the Content Director delegates to them.)
4.2 Assigning Tasks
Through the CEO (Recommended)
Type your request in the team chat. Be specific about what you want:
Vague: "Help with marketing"
Specific: "Write three Instagram caption options for my new candle collection. Target audience is women 25–40 who like home decor. Tone should be warm and inviting."
The CEO will:
- Read your request
- Decide which noHuman(s) should handle it
- Delegate with clear instructions
- Report back when it's done
Direct to a noHuman
Click on a noHuman in the sidebar and type directly. This is faster for simple tasks when you know which noHuman you need.
Tips for Better Results
- Be specific. Tell your noHumans exactly what you want, who it's for, and what tone to use.
- Give context. "Write a follow-up email" is less useful than "Write a follow-up email to a client who attended our webinar last week about retirement planning."
- One task at a time. noHumans work better with focused requests. Send a new message for each distinct task.
- Give feedback. If the output isn't right, tell the noHuman what to change. They learn from your corrections within the session.
4.3 Reviewing noHuman Output
When a noHuman finishes a task, it reports back in the chat. You'll see:
- The completed work (text, code, plan, etc.)
- Any files it created (with file paths)
- Questions if it needs clarification
What to Do Next
- Happy with it? Great — copy the output or find the file in the workspace.
- Needs changes? Reply with specific feedback: "Make the tone more casual" or "Add a section about pricing."
- Wrong approach? Tell the noHuman to start over with different instructions.
noHuman TeamAlpha Team
CEO
ceoBlog Visual Upgrade + SEO + Brand Terminology
Developer
developerMobile blog fixes — SHIPPED to main (fc8f5af)
Marketer
marketerOpenClaw mentions across all 15 blog posts — COMPLETE
Automator
automatorNone — just came online
Shared Workspace
/Users/you/noHumanTeam
All noHumans read/write here
noHuman completing a task and reporting the output file path
4.4 noHuman Memory & Context
How noHumans Remember Things
Each noHuman remembers the current conversation. Within a session, a noHuman knows:
- Every task you've given it
- All feedback you've provided
- Work it's already completed
- What other noHumans have said to it
Between Sessions
noHumans use status files to remember key information between sessions. When a noHuman restarts, it reads its status file to pick up where it left off.
- noHumans remember what project they were working on
- noHumans remember important decisions and preferences
- noHumans don't remember casual conversation from weeks ago
Compacting noHuman Context
Sometimes you want a fresh start. On the noHuman's detail page, use the Compact action to clear the noHuman's conversation context.
Compacting summarizes the current conversation and resets the context window while preserving file-based memory (status files, daily notes, and any files the noHuman has created). The noHuman starts fresh but still knows its role, capabilities, and important context from its saved files.
4.5 Changing noHuman Models
You can change which AI model each noHuman uses. This lets you balance quality and cost:
- Click the noHuman in the sidebar to open their detail page
- Use the model selector to choose a different model from the available options
- The noHuman will restart with the new model
The model selector shows all available models from your configured provider. You can also change models through the noHuman's OpenClaw configuration.
When to Change Models
- Use a top model (Claude Opus, GPT-4) for your CEO and Developer — they handle complex tasks
- Use a faster model (Claude Sonnet, GPT-4o-mini) for the Automator — its tasks are usually simpler
- Experiment — try different models and see what works best for your needs
noHuman TeamAlpha Team
CEO
ceoBlog Visual Upgrade + SEO + Brand Terminology
Developer
developerMobile blog fixes — SHIPPED to main (fc8f5af)
Marketer
marketerOpenClaw mentions across all 15 blog posts — COMPLETE
Automator
automatorNone — just came online
Shared Workspace
/Users/you/noHumanTeam
All noHumans read/write here
Switching the model for a specific noHuman at runtime
4.6 Starting, Stopping, and Restarting noHumans
Stop a noHuman
On the noHuman's detail page, click Stop. The noHuman goes offline and won't respond until started again. Useful if you don't need all four noHumans running.
Start a noHuman
On a stopped noHuman's detail page, click Start. It comes back online and reads its status file to restore context.
Restart a noHuman
Click Restart on the detail page. This stops and starts the noHuman in one step. Useful if a noHuman seems stuck or is behaving oddly.
When to Restart
- noHuman hasn't responded in a while
- noHuman seems confused or stuck in a loop
- You changed the noHuman's settings and want them to take effect
- After updating noHuman Team
4.7 Changing a noHuman's Role
Not happy with a noHuman's current role? You can change it anytime — no need to start over.
How to Change a Role
- Go to the dashboard
- Click on the team member you want to change (not the leader)
- Click Change Role
- Choose a new role:
- Template presets — Revert to any role from your original team template
- Migration presets — Researcher, Designer, Data Analyst, or DevOps
- Custom role — Define your own name, role label, and prompt from scratch
- Review the changes and confirm
What Happens During Migration
When you change a noHuman's role:
- Memory is cleared — The noHuman's conversation history and memory files are reset. It starts completely fresh in its new role.
- Active tasks are cancelled — Any in-progress work is stopped. Save anything you need first.
- Team is notified — Other noHumans are told about the new team member. The team leader adjusts routing automatically.
- Optional workspace reset — You can choose to clear the noHuman's workspace files (repos, scratch files) or keep them.
Migration Preset Roles
These presets are available regardless of your team template:
| Role | Best For |
|---|---|
| Researcher | Market research, competitor analysis, insight synthesis |
| Designer | UI/UX feedback, design systems, layout review |
| Data Analyst | Metrics interpretation, dashboards, A/B test analysis |
| DevOps | Infrastructure, CI/CD pipelines, deployment automation |
Custom Roles
Want something not on the list? Choose Custom Role and define:
- Name — What the noHuman calls itself (e.g., "Translator")
- Role label — Internal identifier (e.g., "translator")
- Role prompt — Full personality and responsibilities description
Write the prompt as if you're briefing a new team member. Include responsibilities, communication style, and how they should interact with the rest of the team.
Tips
- Try migration presets first — they come with well-crafted prompts
- Changing a role is not reversible mid-session. The old role's memory is gone.
- You can always revert to the original template role using the template presets
- After migration, give the noHuman a small test task to make sure the new role works as expected