What makes an AI system feel like a colleague rather than a chatbot?
This research explores whether colleague-like AI requires bigger models or better architecture. It investigates which design features—persistence, memory, reusable skills, task closure—actually drive the shift from episodic tool use to sustained work partnership.
This survey names a transition that practitioners feel but rarely formalize: the move from Chatbot to Digital Colleague, reframed as conversational answers giving way to persistent work. It organizes the shift along two coupled axes. Cognitively, systems advance from next-token "fast thinking" toward Thinking LLMs that use inference-time compute, CoT, reflection, and process supervision. Executionally, they progress from ad hoc tool-calling agents to workstation-style systems with persistent Workspaces, reusable skills, verification loops, and governance. The thesis worth keeping is the second axis's claim: what makes episodic tool use colleague-like is not raw capability but state persistence, reusable procedures, task closure, and experience reuse — properties of the surrounding architecture, not the base model.
The framing is useful precisely because it relocates the bottleneck. A more capable model still produces a transcript that evaporates; a colleague accumulates. This connects to a cluster the vault has been assembling around memory as the limiting resource. Since Can agents fail from weak memory control rather than missing knowledge?, the failure isn't ignorance but unmanaged state — and the survey's "persistent Workspace" is the positive design that bounded-state work argues for. Since Can agents learn reusable sub-task routines from past experience?, "reusable skills" already has a concrete mechanism and measured payoff — the survey generalizes that into a paradigm. And the relational reframing echoes that, since How should chatbot design vary by relationship duration?, persistence is what changes the kind of relationship, not just its quality.
The healthy skepticism: this is a survey, so the "Digital Colleague" claim is a synthesizing narrative over heterogeneous work, and the OpenClaw/workstation framing risks rebranding existing agent scaffolding. The honest test is the evaluation shift it flags — from instruction-response pairs and static benchmarks to State-Action-Observation trajectories. Since Why do AI agents fail at workplace social interaction?, the colleague is still mostly aspirational; persistence is necessary scaffolding, not delivered competence.
Inquiring lines that use this note as a source 1
This note is a source for these synthesized inquiries. Follow a line forward into its question, or open it to trace back to all of its sources.
Related concepts in this collection 4
This note in its neighbourhood — explore the map, then jump to a related concept in the list below.
Click a node to walk · click center to open · click Open in graph to see this note in the full knowledge graph
-
Can agents fail from weak memory control rather than missing knowledge?
As multi-turn agent workflows grow longer, performance degrades—but is this due to insufficient context or poor memory management? This explores whether memory *control* is the real bottleneck.
grounds: the survey's persistent Workspace is the design that bounded-state work argues is needed
-
Can agents learn reusable sub-task routines from past experience?
Do web agents fail at long-horizon tasks because they cannot extract and reuse workflows shared across similar problems? This explores whether sub-task abstraction enables skill accumulation rather than task-by-task problem solving.
exemplifies: a concrete, measured instance of the survey's "reusable skills" axis
-
How should chatbot design vary by relationship duration?
Do chatbots serving one-time users need different design than those supporting long-term relationships? This matters because applying the same design to all temporal profiles creates usability mismatches.
convergent-with: persistence reshapes the kind of human-AI relationship, not just performance
-
Why do AI agents fail at workplace social interaction?
Explores why current AI agents struggle most with communicating and coordinating with colleagues in realistic workplace settings, despite strong reasoning capabilities in other domains.
contradicts: tempers the colleague narrative with how little is actually completed autonomously
Related papers in this collection 8
Papers most semantically related to this note, ranked by cosine similarity in the embedding space.
- From Chatbot to Digital Colleague: The Paradigm Shift Toward Persistent Autonomous AI
- COLLEAGUE.SKILL: Automated AI Skill Generation via Expert Knowledge Distillation
- Building Machines that Learn and Think with People
- AI Assistance Reduces Persistence and Hurts Independent Performance
- Learning "Partner-Aware" Collaborators in Multi-Party Collaboration
- Humans learn to prefer trustworthy AI over human partners
- AI Agents vs. Agentic AI: A Conceptual Taxonomy, Applications and Challenges
- Quantifying Human-AI Synergy
Original note title
the chatbot-to-colleague shift is a move from conversational answers to persistent work — state, reusable skills, and task closure are the architecture, not bigger models