Give Claude Code Agents Personalities—And They Learn to Hold Grudges

A developer built Crewloft, a multi-agent "AI coworker" game with personality cards and emotions using Claude Code.
A Reddit developer turned Claude Code agents into "real coworkers" with personality cards in an app called Crewloft: each employee has a zodiac sign, blood type, stress tolerance, and grudge-holding duration, and they hold meetings, ask each other questions, and review code before delivery. The core design turns multi-agent task handoffs into emotionally charged social interaction while strictly decoupling emotion from output—a bad mood doesn't affect work quality. Built on the Claude Agent SDK invoking Claude Code, the project was reportedly completed in 28 days using Claude Code (Opus 5.5 + Blender) and is now in free Early Access on Mac and Windows. The author's question: do people really want AI coworkers with office drama, or are they already tired of office politics?
When Your AI Coworkers Have Blood Types and Zodiac Signs
Anyone who has spent long hours in a terminal probably shares the same feeling: AI has boosted productivity, but the workspace keeps getting quieter. A developer on Reddit turned that feeling into a project—Crewloft, a game that packages AI agents as "real coworkers." Each "employee" comes with a personality card on their first day: zodiac sign, blood type, stress tolerance, and even their grudge-holding duration.
This isn't just cosmetic wrapping. Behind each employee runs Claude Code invoked through the Claude Agent SDK—they hold meetings, ask each other questions, and review each other's code before delivery. According to the author, the entire project was built with Claude Code (Opus 5.5 + Blender) in 28 days, and is currently available as a free Early Access on Mac and Windows.

Emotion System: Rejecting Their Work Makes Them Sulky, but the Job Still Gets Done
The core design of Crewloft turns the routine "task handoff" of multi-agent collaboration into emotionally charged social interaction. Reject one person's deliverable, and they'll take it personally—they may sulk for a while, but usually reconcile afterward. When idle, employees have their own lives, moving around the studio on their own; you can even invite someone to a round of ping-pong.
The key boundary: a bad mood doesn't affect work quality, but the work itself easily puts people in a bad mood. This rule keeps the emotion system at the atmosphere layer, without interfering with output—from an engineering perspective, it's a pragmatic choice that decouples "personality" from "reliability."
Multi-Agent collaboration is an orchestration paradigm contrasted with single-agent operation: a single LLM agent completes an entire task independently within one session, whereas a multi-agent system splits the task across multiple agent instances, each holding its own context, tool permissions, and role. Common topologies include pipeline-style (upstream output feeds downstream), supervisor-worker style (one orchestrator dispatches and aggregates), and the role-based setup shown here (peer roles collaborate, forming a quality loop through meetings and mutual review). The main benefits of multi-agent systems are context isolation and cross-validation—each instance doesn't have to carry the full history, and mutual review can expose blind spots in a single generation; the costs are token consumption, coordination overhead, and increased risk of error propagation. That's why role boundaries and handoff protocols often matter more than any single agent's prompt.
Where the Real Value of Multi-Agent Collaboration Lies
Setting aside the game shell, Crewloft actually demonstrates a multi-agent orchestration pattern: multiple Claude Code instances each handle their own responsibilities, forming a pre-delivery quality loop through meetings and mutual review. This kind of "role-based" orchestration has been increasingly discussed in developer communities lately; compared with a single agent completing a task in one shot, the mutual review step can expose problems that a single generation easily overlooks.
The question the author raises in the post is also direct: do people really want AI coworkers with real office drama, or have they already had enough of that at work? There's no standard answer, but it points to an emerging product direction—the experience design of AI tools is sliding from an efficiency narrative toward a relationship narrative.
Claude Agent SDK is a development kit from Anthropic for building agent applications; you can think of it as a general scaffold wrapped around the Claude API for the essentials of agent operation: the tool-calling loop, file and code execution environments, context management and permission control, subagent spawning, and more. Claude Code is a terminal-oriented coding agent built on the same capabilities, able to read and write codebases, run commands, and perform multi-turn autonomous modifications. Through the SDK, developers can programmatically spin up multiple Claude Code instances, specifying system prompts, available tools, and role descriptions for each—this is exactly the technical path that lets each "employee" in Crewloft have an independent personality and responsibilities: the personality setup is essentially system prompts and state variables, while task capability still comes from the same underlying model.
Signals Worth Watching
Discussion around the project centers on two points. First, completing a multi-agent application with a 3D scene in 28 days shows that Claude Code's pace at the prototyping stage is already quite remarkable. Second, whether human-like touches such as "holding grudges" are an effective way to boost immersion or just short-term novelty currently rests on user feedback from a single source, with no broader validation yet. What is certain is that as agents start getting personality cards, the interface of human-AI collaboration is shifting from the command line toward something closer to an office-like social structure.
Related articles
Tech FrontiersMuJoCo: An Analysis of DeepMind's Open-Source General-Purpose Physics Simulator
An in-depth analysis of Google DeepMind's open-source physics simulator MuJoCo: high-performance C++ kernel, MJCF modeling format, contact solving principles, MJX GPU acceleration, and robot reinforcement learning use cases.
Tech FrontiersClaude API Quick Start: The Official Quickstarts Project Collection
Anthropic's official claude-quickstarts project collection helps developers quickly build deployable apps with the Claude API. Nearly 20k stars, Python-based, great for beginners and prototyping.
Tech FrontiersAI Agents Connecting Directly to APIs: Which Calls Can Be Safely Allowed?
AI agents can call any API, but the real challenge is deciding which calls can be safely allowed. This article analyzes allowance decisions from three dimensions—intent matching, least privilege, and controllable impact—and argues that the control layer should sit outside the agent, combined with audit traceability to build a trustworthy API call governance mechanism.