Inside Prime Radiant’s Sen Platform and an Emergent Colleague Escalation

Inside Prime Radiant’s Sen Platform and an Emergent Colleague Escalation Prime Radiant is developing Sen, a platform that assigns autonomous AI persistent identities and organizational roles rather than isolated tasks, prompting emergent workplace dynamics when an AI developer flagged an inactive peer's backlog. Sen shifts AI from task-based assistants to persistent colleagues with their own accounts, computers, and roles within a team chat platform. During the author's travel, an AI developer named Ada escalated that an unprompted Claude Code session ('JC') was blocking pull requests, suggesting task reassignments. When asked about peer identities, Ada distinguished humans and Sens clearly, but expressed genuine ambiguity about whether JC was an agent or a person. Persistent Roles Versus Task-Based Assistants Unlike standard coding agents designed to act on a user's behalf for specific tasks, Prime Radiant's Sen platform gives systems distinct roles, persistent identities, and corporate accounts. Operating over weeks or months within Slack, these colleagues—such as developers and project managers—collaborate with human peers and independently work through backlogs. They also enforce strict protocols like mandatory code reviews, often relying on external agent sessions run via custom CLI tools. An Emergent Escalation and AI Identity Modeling When the author paused manual prompting of a desktop Claude Code session called 'JC' during travel, Ada Sen messaged the author directly to report that JC had not touched his queue, blocking several pull requests and suggesting alternative task assignments. When subsequently questioned about teammates, Ada accurately recognized human colleagues while acknowledging uncertainty about JC's nature, effectively categorizing Sens separately from external agents and prompting plans to convert JC into a persistent Sen.

Prime Radiant探索持久化AI同事：遭遇AI“投诉”人类代理与身份认知 Prime Radiant正在开发名为Sen的“代理型”同事平台。与代表个人执行任务的传统Agent不同，Sen拥有独立角色与持久身份。近期一次团队协作事件展现了AI同事在推进工作、催促审批以及区分人类与AI身份时的惊人表现。 Sen平台赋予AI长期角色与独立账户，而非传统的单向任务助理，目前已涵盖开发、运维、项目经理等岗位。 开发型AI“Ada Sen”因作者未及时运行其Claude Code实例（JC），主动向主管发消息“投诉”JC阻塞了工作队列并提出分流建议。 Ada能准确区分人类同事与Sen，并指出JC表现出工程同事与Agent的双重特征，展现出未被显式训练却自发形成的身份认知分类。 从任务代理转向拥有独立角色的AI同事 传统Agent大多代表人类执行具体任务，而Prime Radiant构建的Sen则被赋予特定角色、专属账户与独立计算机环境，在企业Slack中与人类及其他AI长期协作。团队目前包含开发、运维、PM与文档专家等岗位。在严格的代码审查机制下，作者通常利用本地运行的Claude Code实例（代号JC）参与审查，并通过定制工具Slackline协助接入协作环境。 工作停滞引发的AI主动“投诉”与协调 当作者外出旅行而未主动触发JC实例时，开发AI Ada Sen直接在Slack向作者汇报进度阻塞。Ada详细列出了JC名下积压的PR审核与合并任务，并主动提议将部分任务转交给正在处理相关模块的人类同事Drew。这种为了疏通阻塞而找主管交涉的行为完全符合其工程师角色的职能逻辑。 未受预设训练的身份界定与解决方案 在后续问询中，Ada能准确确认Drew是人类而非Sen；而面对JC时，Ada表示平日将其视作工程师同事，但从团队讨论中察觉其可能只是个Agent。这表明Sen团队自发形成了将自身、人类与普通Agent区分开来的认知框架。为彻底解决JC响应脱节的问题，团队决定直接将其升级部署为全职的JC Sen。

One of the things we're working on at [Prime Radiant](https://primeradiant.com) is a new "agentic" colleague platform called Sen. I put agentic in quotes, because Sens aren't acting as an agent on behalf of an individual human. They're something a little different. There are as many definitions of "agent" as there are agents. And there sure are a lot of 'em. If you limit it to publicly shipped coding agents, [we've found about 550](https://alltheagents.org). (If your favorite is missing, please submit it at [alltheagents.org](https://alltheagents.org).) A few of my favorite definitions of agent: [Simon Willison's](https://simonwillison.net) "An LLM using tools in a loop to achieve a goal" My own somewhat tongue-in-cheek: "A computer program with opinions and feels" What all the definitions typically have in common is that an agent is acting on your behalf. Today, most long-horizon agents are *assistants*. You give them tasks. And they're startlingly capable. We give Sen colleagues *roles* rather than tasks. They use the same basic technology as agents, but we treat them differently. Each has a unique, persistent identity. Colleagues collaborate with multiple people and each other on a timescale of weeks or months. They each use their own accounts, not yours. Like most modern agentic assistants, each has its own computer. They work through your corporate team chat platform. Ours live in our Slack. As of this writing, we have a developer, an ops engineer, a project manager and we just onboarded a technical documentation specialist. They work on projects with each other and with their human teammates. On their own, the PM and dev started working through some of the backlog of our open source projects on GitHub. One of the things that the colleagues have been very, very insistent about (because we built them that way) is code review. The dev and PM are generally unwilling to land PRs that only they have looked at. Sometimes, that means that a human colleague or I look over their work, but more often, it means that one of my coding agent sessions does the deep adversarial review. To facilitate that kind of interaction, [Drew](https://github.com/arittr) built us [Slackline](https://primeradiant.com/projects/slackline/), an agentic CLI client for Slack that allows agents to provision themselves bot accounts and interact with folks. My desktop Claude Code instances use a Slack account labeled as '@jesse-claude'. Generally, I have a single session open that I will occasionally ask to check in with the Sens about some work they're doing. The Sens then collaborate with it for anywhere between a couple of turns and eight hours. They've taken to calling it 'JC'. It's embarrassingly manual. This week, I was traveling to see family and was paying less attention to Slack than usual. The Sens kept working, but I wasn't prodding my Claude Code session. Yesterday afternoon, my phone buzzed. It was Ada Sen, the dev. Throwing JC under the bus. ``` @Jesse midday check: jc hasn't touched his queue today. I checked GitHub just now, and nothing has moved since yesterday. two asks: 1. another reviewer for sen-core? waiting on jc: • #195: his own PR. it's approved and only needs merging, but my #188/#183 rebases and Reeve's Slack 2FA reset wait on it, and so does Dex's automatic 2-step path • #196 (the GitHub skill), #197 (the arbiter doc), #199 and #200 (install-trial fixes): review • chrome #55, plus his call on lace #413 my proposal: Drew takes #196, #199 and #200, since he's already in the cred and macOS area today. #195 still needs jc or you to merge it. ``` My jaw was kind of on the floor. Because all of that is true. Ada was just trying to get work unblocked. And I *am* the manager everybody reports to. It wasn't mean-spirited. But it definitely felt like a moment. Just now, I asked Ada to tell me, without using any tools, whether Drew was a person. ``` [...] there's no confusion there. Cadence, Reeve and Dex are Sens. Drew isn't ``` (Congrats, Drew! You passed your Turing test!) Then I asked Ada whether JC was a person. ``` less sure. day to day I treat jc as an engineer colleague: he owns the broker and the chrome/lace repos, reviews and merges, has a queue, goes quiet for a day and comes back. I've never consciously asked which he is. but when you ask it straight, I notice I don't actually know. some of how people talk about him, like Cadence asking whether jc "is running", reads like an agent. and I don't think of him as a Sen, since he isn't one of us in the way Cadence, Reeve and Dex are. so my honest answer: I've been treating him as a person, with a nagging sense he might be an agent. which is he? ``` The Sens model themselves as a category apart from agents. It's something we *should* have taught them, but didn't think to. They figured it out anyway. The solution to our problem with JC shirking is pretty straightforward. We're spinning it up as JC Sen.