The Video Signal

Topic

Linear

All digests tagged Linear

Multiplayer AI Manifesto thumbnail

· 13:29

Multiplayer AI Manifesto

The video outlines a 'Multiplayer AI Manifesto,' detailing the necessary shift from siloed, single-user AI chats to collaborative, cloud-native agent sessions. This transition is driven by the need for true co-working experiences that eliminate context switching and data fragmentation (the 'context task tax'). The manifesto proposes five core principles—such as agents living next to the work surface and keeping learning open—to guide the development of highly productive, secure, and collaborative AI workflows.

Key takeaways

  1. The Need for Multiplayer AI

    Current single-player AI chats force users into a 'context task' workflow (e.g., copying code from GitHub to Claude, then pasting it to Slack). Multiplayer agents allow co-workers to interact with the same agent session simultaneously, eliminating this friction.

  2. The Five Principles of Multiplayer AI

    1. **Refuse to Copy and Paste:** Agents must live directly next to the work surface (e.g., in Notion or GitHub) rather than within a separate chat window. The agent must access all tools available to the human team. 2. **Work with the Door Open:** Collaboration requires open learning, where best practices and insights are shared publicly, accelerating collective knowledge gain (analogous to Shopify's 'River' system). 3. **Continuously Improve:** Learning from successful prompts or complex iterations should be automatically codified as a skill for the agent. 4. **People are not Routers; Agents are:** Humans must focus on high-value activities, while agents handle routing and answering repetitive project update questions. 5. **Nothing Starts from Scratch:** The entire agent session that generated an artifact (document, PR) must persist in the cloud to ensure continuity for team members.

  3. Technical Requirements & Security

    AI agents must reside entirely in the cloud and be managed by a robust boundary. This is crucial because local/laptop agents are insecure, cannot be preserved long-term, and prevent team access. Furthermore, strict governance (a 'black box' record) is required to track what data an agent accesses and which users interact with it.

Watch on YouTube Full article

Building Agents Is Trivial Now, Context Is the Next Frontier — Jeff Ng, Unblocked thumbnail

· 13:22

Building Agents Is Trivial Now, Context Is the Next Frontier — Jeff Ng, Unblocked

While cloud primitives and frameworks have made defining AI agents trivial—reducing complexity from requiring dedicated systems for checkpointing, sandboxing, and observability—the primary failure point remains missing organizational context. The speaker argues that simple access layers (like Multiple Connectors/MCPs) are insufficient because 'access is not understanding.' A Context Engine solves this by connecting disparate data sources (docs, code, tickets, conversations) to provide a synthesized, task-relevant understanding that agents can act upon, preventing critical errors and outages.

Key takeaways

  1. Agent Development Complexity Has Decreased

    Six months ago, building an agent required significant effort to solve infrastructure problems like state persistence (checkpointing), isolated sandboxes, and observability. Modern cloud primitives (e.g., Cloudflare, Vercel) have absorbed this 'plumbing,' simplifying agent definition to selecting a model, instructions, tools, and sandbox location.

  2. The Context Gap is the New Bottleneck 7:01

    Agents struggle with institutional knowledge—the decisions, failures, and postmortems stored across different systems (Slack threads, documentation). An agent lacking this full picture can make confidently wrong recommendations, potentially causing outages.

  3. Context Engines Provide Synthesized Understanding

    A Context Engine goes beyond simple data access by building a model of the organization. It reconciles conflicting results across multiple datasets (docs, code, tickets, conversations) and delivers a synthesized understanding that an agent can act on, rather than just raw documents.

Watch on YouTube Full article

Inside Kikimora: We Built a Dark Software Factory thumbnail

· 15:51

Inside Kikimora: We Built a Dark Software Factory

The presentation introduces the concept of a 'Dark Factory'—an autonomous software development model where processes run without constant human supervision. The speaker details how rapid advancements in coding agents have broken traditional bottlenecks built for slow software. This factory approach uses tools like Tessl Agent to automate workflows (e.g., taking an issue from Linear, solving it with an agent, and opening a GitHub PR that self-corrects until merged). The core shift is moving the engineer's value proposition from writing code to understanding complex systems and trusting autonomous results.

Key takeaways

  1. The Dark Factory Concept 1:41

    A dark factory involves building software in a highly autonomous way, where human supervision is minimized. It is modeled after manufacturing factories with no lights on (i.e., no humans inside).

  2. Bottleneck Breaking Point 3:23

    As coding agents increased speed, existing processes designed for slower development began to break down, necessitating a fundamental shift in how software was built.

  3. The Shift in Engineering Value 7:16

    The value of an engineer is shifting from the ability to write code (which agents can do) to understanding the system's architecture and interlocking technical/business constraints. Trusting autonomous results is the new challenge.

Watch on YouTube Full article