The next paradigm shift (according to Karpathy)

Tech/AI Concept + Product Features Highlighted

• “Claude Tag” as an org-level agent primitive (Slack-first)

  • Claude can be added to Slack as a team member (not just a one-off command).
  • Teams can grant Claude access to selected channels and specific tools/data/codebases.
  • Users can tag Claude in-channel to delegate tasks while focusing on their own work.

• Channel-based context management + learning

  • Claude builds context from the channels it’s in, so users don’t have to re-explain everything repeatedly.
  • Memory/learning is scoped to the channel, not global company-wide, aligning with how teams structure knowledge.
  • Claude can potentially learn from other channels/data sources if permissions allow, but it doesn’t pull from private channels.

• “Multiplayer” workflow inside Slack

  • One Claude instance per channel, shared by everyone there.
  • Multiple people can interact with the same Claude and continue from where the last person left off, making it feel like collaboration rather than a single-user chat.

• Asynchronous and autonomous task behavior

  • Claude can work asynchronously: users delegate and return later.
  • It can also schedule and pursue tasks over hours/days.

• Optional “ambient” proactive updates

  • When enabled, Claude can proactively flag relevant information from connected tools/channels and follow up on unresolved threads—helpful because Slack can be chaotic.

• Comparison to other agent setups (Hermes/OpenClaw/OpenClaude)

  • The speaker describes earlier agent tooling patterns where different agents/containers are manually created to isolate context per task/channel (e.g., multiple “isolates”/deployments).
  • They like Claude Tag because it provides similar “separation via context boundaries” at the platform level (channel as the boundary), reducing the need for extensive customization.

• Scheduling/use-case example

  • A daily automation that scans a subreddit and generates a shareable page for social posting.
  • Separating this into its own “thread/context” helps prevent interference with other tasks.

Critical Review / Analysis Points

• Feature hype vs limitations

  • The speaker is enthusiastic about the UX and org-level design, but less happy that:
    • It may be tied to Anthropic’s model (“the Claude part”) rather than being model-agnostic.
    • There’s no easy way to switch models for Claude Tag, unlike custom agent setups where models can be swapped for speed/cost/quality tradeoffs.

• Vendor / lock-in concern

  • They argue it’s better to support multi-vendor / multi-model approaches for higher quality and efficiency.
  • They describe a strategy where agents delegate work to other agents/models (e.g., for SDK/API design or UI tasks), which they say isn’t available with Claude Tag as-is.

• Non-product sponsor product mention: code review UX

  • They review CodeRabbit, which improves code review by restructuring large PR diffs into readable logical “layers” with summaries, hover details, comment indicators, and a side minimap.
  • The framing is that this is about making output readable, not changing the underlying concept of code review.

Main Speakers / Sources

• Andrej Karpathy

  • Named/referenced extensively; the key “future paradigm” framing is attributed to him.

• The video’s host/reviewer

  • The speaker who praises/criticizes Anthropic/Claude Tag and compares it to their Hermes/OpenClaude setups.

• Anthropic

  • Source of Claude Tag product claims (e.g., adoption metrics).