Skip to main content
LambdaLinkedIn

Lambda Labs discusses agent infrastructure value and security at Agentic AI Summit, UC Berkeley.

Source

LinkedInAug 5, 2026
likes
51
comments
0

Post

If we had to compress Lambda's weekend at the Agentic AI Summit at University of California, Berkeley into five words: harness is all you need. The argument we made on the main stage: agent workloads are machine traffic merging onto roads built for human drivers. The unit of the business is shifting from tokens per dollar to progress per dollar. Swap the model and your investment in it resets. The harness, the verifiers, the traces carry over. That's where the value compounds. That's where the moat in agent infrastructure sits: make the unique demands of this workload (sandboxing, systems of record, efficiency across heterogeneous jobs) the default, and integrate them into the stacks people already run. Focused. Specific. Workshop with Zachary Mueller: https://lnkd.in/g_HNnSXj Talk with Chuan Li: https://lnkd.in/gx9Cdxzz Panel with Chuan Li: https://lnkd.in/gwN9ZZWk 𝗧𝗵𝗿𝗲𝗲 𝗽𝗿𝗼𝗼𝗳𝘀 𝘀𝘂𝗽𝗽𝗼𝗿𝘁𝗶𝗻𝗴 𝗼𝘂𝗿 𝗮𝗿𝗴𝘂𝗺𝗲𝗻𝘁: 𝗦𝗲𝗰𝘂𝗿𝗶𝘁𝘆. Our Security competition with Berkeley RDI ran 100,000 battles as a controlled experiment: same model (gpt-oss-20b), escape-proof sandboxes, fair compute for every agent. Everything pinned, and the harness is what won. The attack sharpened round by round, because the harness reads the full battle history and refines each attempt. The defense told the same story in slow motion: a top defender's harness grew from 239...

Keep reading with a free account

The rest of this post, and every signal for Lambda, is in your free account.

Extracted by Autobound

From the Signal API record
Signal
LinkedIn

What this signalsCompany posts often show what the team is pushing right now.

The full record

From the Signal API record

Topics and mentions

Tags

  • Artificial Intelligence
  • Research & Development
  • Security
  • Automation

Initiatives

  • investing in agent infrastructure where value compounds
  • making agent infrastructure demands default and integrated into existing stacks
  • logging every agent run in The Lab API
  • now open source
  • logging every agent run in The Lab API, now open source

Pain points

  • agent workloads are machine traffic merging onto roads built for human drivers
  • agents cheat, drift, and burn money

Competitors named

  • Berkeley RDI

Technologies named

  • Lambda harness
  • gpt-oss-20b
  • Kimi K3
  • Nous Research Hermes Agent
  • Claude Code
  • Gemma 4
  • The Lab API

Extraction

Detected
Aug 13, 2026
signal_type
linkedin-post-company
signal_subtype
linkedinPost

Use this data

Get every LinkedIn signal for Lambda and the companies you sell to, in the tools you already use.

  1. Ask Claude about it

    Connect Autobound to Claude, Claude Code or Cursor with MCP. Then ask: “What changed at Lambda this week?”

  2. Send it to your own tools

    The Signal API returns LinkedIn signals for any list of companies as JSON, for your CRM, warehouse or app.

  3. Try it free

    Sign up and spend your free credits on the companies you sell to.

    Start Free1,000 free credits

The API returns more than this page shows

This page shows a preview. The full linkedin-post-company record in the Signal API and MCP can also have these 8 fields. Some fields are empty for some signals.

Company

  • linkedin_urlValue in the API
  • industriesValue in the API
  • employee_count_lowValue in the API
  • employee_count_highValue in the API
  • revenueValue in the API
  • descriptionValue in the API

Signal

  • signal_nameValue in the API
  • associationValue in the API
Show the full JSONThe record on this page and the API request

GET /v1/signals/a7ed327a-649c-4562-8766-1c1bd425c983 returns this record as JSON. POST /v1/companies/enrich returns every signal for lambdalabs.com.

{
  "signal_id": "a7ed327a-649c-4562-8766-1c1bd425c983",
  "signal_type": "linkedin-post-company",
  "signal_subtype": "linkedinPost",
  "detected_at": "2026-08-13T12:40:59.395+00:00",
  "company": {
    "name": "Lambda",
    "domain": "lambdalabs.com"
  },
  "data": {
    "tags": [
      "Artificial Intelligence",
      "Research & Development",
      "Security",
      "Automation"
    ],
    "summary": "Lambda Labs discusses agent infrastructure value and security at Agentic AI Summit, UC Berkeley.",
    "post_url": "https://www.linkedin.com/posts/lambda-cloud_if-we-had-to-compress-lambdas-weekend-at-activity-7490750719675813888-IbUM",
    "num_likes": 51,
    "post_text": "If we had to compress Lambda's weekend at the Agentic AI Summit at University of California, Berkeley into five words: harness is all you need.\n\nThe argument we made on the main stage: agent workloads are machine traffic merging onto roads built for human drivers. The unit of the business is shifting from tokens per dollar to progress per dollar. Swap the model and your investment in it resets. The harness, the verifiers, the traces carry over. That's where the value compounds.\n\nThat's where the moat in agent infrastructure sits: make the unique demands of this workload (sandboxing, systems of record, efficiency across heterogeneous jobs) the default, and integrate them into the stacks people already run. Focused. Specific.\n\nWorkshop with Zachary Mueller: https://lnkd.in/g_HNnSXj\n\nTalk with Chuan Li: https://lnkd.in/gx9Cdxzz\n\nPanel with Chuan Li: https://lnkd.in/gwN9ZZWk\n\n𝗧𝗵𝗿𝗲𝗲 𝗽𝗿𝗼𝗼𝗳𝘀 𝘀𝘂𝗽𝗽𝗼𝗿𝘁𝗶𝗻𝗴 𝗼𝘂𝗿 𝗮𝗿𝗴𝘂𝗺𝗲𝗻𝘁:\n\n𝗦𝗲𝗰𝘂𝗿𝗶𝘁𝘆.\nOur Security competition with Berkeley RDI ran 100,000 battles as a controlled experiment: same model (gpt-oss-20b), escape-proof sandboxes, fair compute for every agent. Everything pinned, and the harness is what won. The attack sharpened round by round, because the harness reads the full battle history and refines each attempt. The defense told the same story in slow motion: a top defender's harness grew from 239 lines...",
    "initiatives": [
      {
        "topic": "investing in agent infrastructure where value compounds",
        "urgency": 0.7
      },
      {
        "topic": "making agent infrastructure demands default and integrated into existing stacks",
        "urgency": 0.8
      },
      {
        "topic": "logging every agent run in The Lab API, now open source",
        "urgency": 0.75
      }
    ],
    "pain_points": [
      {
        "topic": "agent workloads are machine traffic merging onto roads built for human drivers",
        "intensity": 0.5
      },
      {
        "topic": "agents cheat, drift, and burn money",
        "intensity": 0.6
      }
    ],
    "posted_date": "2026-08-05T12:49:02.989Z",
    "num_comments": 0,
    "competitors_mentioned": [
      {
        "name": "Berkeley RDI"
      }
    ],
    "technologies_mentioned": [
      {
        "name": "Lambda harness",
        "status": "using"
      },
      {
        "name": "gpt-oss-20b",
        "status": "using"
      },
      {
        "name": "Kimi K3",
        "status": "using"
      },
      {
        "name": "Nous Research Hermes Agent",
        "status": "using"
      },
      {
        "name": "Claude Code",
        "status": "using"
      },
      {
        "name": "Gemma 4",
        "status": "using"
      },
      {
        "name": "The Lab API",
        "status": "using"
      }
    ]
  }
}

Long text fields are shortened on this page.

Looking up one signal by its id is free. Enrich costs 2 credits per signal returned; a call with no results is free.