Here is a summary of the podcast episode based exclusively on the provided transcript:
**Guest and Company Overview**
* Ken is a founder at First Person Labs, talking about the company's work for the very first time on the podcast.
* First Person Labs focuses on creating a model of a person (understanding their memories, priorities, preferences, goals, values, commitments, and intent) and putting that person in control.
**The Core Product: "Second"**
* The company creates a personal agent/model called a "Second."
* A Second acts as a personal butler or agent (akin to an "Alfred to Batman"), securely holding a person's life context and serving as a trusted vault.
* First Person Labs acts as its own thing, rather than being an agent itself like Grokbot or Codex. Other specialized agents (such as Grokbot, Codex, or ephemeral agents) interface with the user's Second to understand what the user wants.
* The host envisions that having many personal agents is transitory, and the Second is intended to be the one trusted agent/vault for all personal data that interacts with all other software and hardware agents.
* The Second continuously analyzes the infinite stream of events as a user uses their computer (app switches, pauses on websites, typing, wi-fi connections) 24/7. It hierarchically builds up an understanding of what the user is trying to do, which is paired with connectors (like slack, signal, whatsapp, and raw computer streams) to understand the user.
* It catches things and provides proactive help—such as updating event weather forecasts in real-time or pinging users regarding ongoing conversations—ranging from reactive productivity (simple email/meme notifications) to reflective productivity (connecting dots across long time horizons and priorities).
* Ken notes that Second is available today (at `two dot computer`), though they are scaling up inference and capacity and rolling it out responsibly.
**Security, Architecture, and Privacy**
* Building a system that sees everything a user does raises immediate trust concerns, so First Person Labs prioritizes privacy and security architecture.
* Data and inference are the two components of AI. Users can choose what inference they bring. If they do not trust First Person Labs, they can bring their own tokens to analyze data locally on their laptop.
* Alternatively, Second provides an inference provider using trusted execution (confidential computing/confidential inference), where a model runs inside GPUs with a special toggle. This provides a hardware guarantee (backed by NVIDIA and third-party providers) where no one—including the provider—can see inside or view the data.
* This differs from "zero data retention," which is merely a policy promise based on a provider's word. Confidential inference uses hardware signatures to make privacy technically provable.
* Storage options include "Second Local" (data stays local, similar to a password vault) or a cloud-hosted version where data is encrypted locally first (similar to iCloud or password managers) and only decrypted ephemerally in memory or entirely inside a secure confidential container that the user can attest.
* Preventing LLMs from leaking information relies on deterministic guarantees (implemented at the app level) and reasoning-based guarantees (scaling with model capability and using context to guide decisions on what data to share).
**Cost, Models, and Performance**
* Running background agents analyzing a computer stream 24/7 consumes a significant number of tokens. Ken provides a math example: running 10 agents 24/7 at 60 tokens per second using Opus pricing would cost $1,000 per day, whereas using DeepSeek Flash drops the cost to $60 per day. Token prices have already dropped by more than 50% since the company started.
* The system is built to be portable and run on any models, utilizing a harness design to determine which models get used when for cost efficiency (e.g., using expensive smart models for high-level goals like understanding a user's weekly goals, and using models like Jeff for retrieval).
**Use Cases and Future Vision**
* Surprising development use cases: Second acts as a super memory for coding. Users no longer need to explain anything to coding agents; they can just screenshot anything, say "fix," and the agent knows what to fix. It also enables "context continuity," allowing a user to seamlessly move from browsing on a laptop to writing an email on a phone with up-to-the-minute context.
* Product interface: Currently, the app runs in the background, asks for permissions, and produces APIs (such as what the user did 10 minutes ago, priorities for next week, reminders, wiki, and people in the user's life). Users can interact via text and APIs, or use audio modes (like calling Grokbot on audio while walking) to interface with their Second.
* Future evolution: The company plans to eventually evolve the interface toward ambient, embodied, and ubiquitous computing (like Jarvis or sci-fi culture series AI companions), where every person has a Second and all devices act as inputs and outputs to that same core model.