concept Updated 2026-07-07 Tags: Ai, Context, Organizations

Organizational Context

Organizational context is the shared work state that Moxt tries to make available to agents in “AGI 来了?我用了一周,头皮发麻“|对谈张昊然:Moxt 联合创始人. It includes documents, meeting recordings, data definitions, PRDs, project plans, code changes, comments, ownership, progress, and communication history that normally remain fragmented across tools.

The concept extends Context Engineering from personal or project context into team infrastructure. In OS-Level Context and Intent Context sources, the key question is how an agent perceives a user’s current activity; in Moxt, the key question is how a workspace preserves the organization’s current state so that AI Coworkers can draft, analyze, remind, critique, and coordinate without repeated manual briefing.

Zhang Haoran’s “more context” claim is that many apparent intelligence failures are actually context-shape failures. If documents, tables, data, meetings, and work progress are stored in AI-readable formats inside an AI-Native Workspace, existing models and agent structures can do more useful work.

Key Claims

  • Organizational context is not only stored knowledge; it includes current team state, responsibilities, project movement, and recent decisions.
  • AI coworkers need access to this context before they can behave like collaborators rather than generic chat assistants.
  • Context quality can improve data analysis because the agent can reason about definitions, metrics, and business questions before generating charts or conclusions.
  • Shared context can reduce some status meetings, but it also raises privacy, permission, and monitoring boundaries.
  • Organizational context can become a switching cost if agents learn the team’s work traces, preferences, and routines over time.

Connections