我们是如何定义 OpenClaw for Teams 新产品形态的｜对谈 Kuse&Junior 联创兼 CTO 宇豪

Summary

This 42章经 episode interviews Yuhao / 宇豪 about Kuse, its shift from design and marketing agents into an AI workspace, and the new Junior product form for teams. The episode’s main contribution is that a team version of Open Claw or Open Cloud should not merely share a personal assistant across coworkers: it needs [[OpenClawForTeams|enterprise-oriented AI employees]] with identity, memory, permissions, security, evaluation, and pricing designed around real organizational labor.

Key Claims

• Kuse moved from early email-marketing and design-agent experiments toward a folder-based AI workspace after finding that users who uploaded files and asked agents to organize or reformat material retained better.
• Fixed subscription pricing proved dangerous for agent products because complex tasks can force many rounds of model calls while users do not see the subsidized inference cost; Kuse shifted toward usage-based pricing even though that reset user and paid-customer numbers.
• Agent startups need Agent Evaluation Benchmarks early because model changes, runtime changes, multi-turn state, tool actions, and “should not act” cases cannot be judged only from impressive demos.
• Kuse’s own organization had about fifteen full-time employees and three to four long-running internal agents, with monthly token spending above $20,000; hiring requests were challenged by asking why the work could not be handled by an agent.
• Azura shows the internal-software threat to SaaS: once a sales agent has customer and sales context, it can build a simple CRM that tracks upsell opportunities without a conventional product-design cycle.
• Junior is positioned as an AI employee rather than a personal assistant: it has responsibilities, projects, work accounts, email, phone number, and a persistent place in company workflows.
• The team version requires Enterprise Agent Memory: a Junior should remember company, project, and organizational relationships rather than only serving one owner’s preferences.
• Security is treated as a product gate, not an afterthought. Kuse gave Junior high internal authority for testing, hired white-hat attackers, and tested phishing, prompt injection, employee-device loss, malicious skills, and inappropriate disclosure.
• Proposed Junior pricing is closer to salary than SaaS: the team discussed per-agent monthly pricing such as $2,000 or $5,000, plus excess token credits.
• Multi-agent work creates new operating problems: role boundaries blur, sessions can queue or grow unstable, multiple humans may talk to one agent at once, and separate AI employees may need separate work machines.
• Internet infrastructure still assumes human users in many places; bot detection, payments, phone numbers, account registration, and platform risk controls can block otherwise capable agents.
• The episode’s social claim is that AI is moving from the software market toward the labor market, which makes cost, safety, auditability, permission semantics, and workflow fit central to enterprise adoption.

Key Quotes

“AI employee” — the product category Yuhao uses to separate Junior from a personal assistant.

“salary-based” — the pricing direction discussed for Junior.

“build evaluation benchmark” — Yuhao’s advice to agent founders.

Connections

• Kuse — company whose workspace growth, pricing changes, and internal agent practice ground the source.
• Yuhao / 宇豪 — Kuse and Junior co-founder/CTO explaining the product and organization lessons.
• Junior, [[KuseRing|Ring]], Azura, and [[KuseTom|Tom]] — AI-employee product and named internal agent cases.
• Open Claw, Open Cloud, and OpenClaw For Teams — reference wave and team-product reinterpretation.
• Digital Employees, AI Organization Design, and Outcome-Based AI Pricing — labor-market, organization, and salary-like pricing implications.
• Agent Evaluation Benchmarks, Agent Permission Boundaries, Enterprise Agent Governance, and Agent Identity And Authentication — reliability, safety, and attribution requirements for enterprise agents.
• Enterprise Agent Memory, Persistent Agent Memory, Agent Harness, Agentic Workflow, and AI Skills — context, tooling, runtime, and procedural-memory layers behind useful agents.
• AI Inference Cost Structure, Multi-Agent Collaboration, Agent Native Software, and Agentic Economy — cost, collaboration, software-design, and infrastructure implications.

Contradictions

• No direct contradiction found. The source reinforces existing OpenClaw/OpenCloud, digital-employee, token-cost, and permission-boundary themes while sharpening a scope distinction: personal agents can center one user’s memory, but team agents need company-first memory, auditable authority, and organizational security.