Segment 04: Tejas Kumar (IBM): agent harness primitives, loop control, and trust over black box models

• Timestamp: 00:48:50
• Duration: 19m 04s
• Livestream range: 00:48:50 → 01:07:54
• Transcript evidence: 38 chunks, about 4062 words

Actionable Insights

1. Turn agent harness primitives into an operating checklist. Turn the speaker’s idea into a concrete workflow: define the user, the input, the tool boundary, the review step, and the failure condition.
2. Separate capability from accountability. The recurring lesson in this chapter is that more capable AI changes who does the work, but not who owns the outcome. When applying it to secure agent execution and harnesses, write down what the system may do autonomously and what still requires explicit human judgment.
3. Instrument the loop before scaling it. The useful operating loop is: capture context, let the tool act, review the result, preserve the learning, and tighten the next run. Write down acceptance criteria and review notes early so the workflow can be audited later.
4. Design for the failure mode, not the demo. The polished demo version of agent harness primitives, loop control, and trust over black box models is less important than the places it breaks: weak context, unsafe permissions, weak evaluation, unclear ownership, latency, or poor human review.
5. Convert this into a agent reliability checklist. The durable takeaway from Tejas Kumar (IBM) is to turn “agent harness primitives, loop control, and trust over black box models” into explicit operating rules: what the system may do, what it must prove, what evidence a reviewer needs, and where a human must stay accountable. The next useful artifact is a short checklist or eval case that someone can actually run.

What they actually use/show that is worth copying

• Claude for slides/drafts: Claude is used for first drafts, speeches, and slides. The key lesson is using a frontier model to speed up expression while the human still owns the judgment and accountability.
• ChatGPT / AGI builder stack: The valuable part is preserving editability and taste. The tool is useful when it keeps design intent alive instead of producing generic one-shot output.
• Exa search primitive: The agent is embedded in the existing delivery workflow. That makes review, testing, and handoff happen where the team already works.
• Simular computer-use agents: The infrastructure choice affects product behavior. Latency, cost, routing, and model availability shape what kind of agent experience is actually possible.
• Cursor / Baby Cursor: The harness is the product. Model capability becomes dependable only when planning, tools, execution, review, and rollback are explicit.
• ElevenLabs speech/turn-taking stack: This is a concrete mechanism from the talk. The useful question is whether it reduces friction, improves reliability, or makes human review easier in a real workflow.
• Bluelabs relationship AI: This is a concrete mechanism from the talk. The useful question is whether it reduces friction, improves reliability, or makes human review easier in a real workflow.

Core thesis

Tejas Kumar (IBM) uses this chapter to make a specific argument about agent harness primitives, loop control, and trust over black box models. The useful pattern is not just the named product or institution; it is how the segment exposes the new operating model for secure agent execution and harnesses: humans keep taste, accountability, and deployment judgment while agents or models absorb more of the execution loop.

The chapter starts from this evidence: “Look, look, it’s it’s it’s a it’s a dialogue, not a monologue, you know, like I I’m here to talk to you, not at you. He’s just setting up my slides right here.” That opening matters because it frames the segment as a concrete slice of the broader AIE Singapore Day 2 theme: agentic systems are moving from demos into production workflows, evaluation harnesses, creative tools, owned infrastructure, robotics, and enterprise runtimes. The analysis should therefore be read as a nested talk-level packet, not as a generic summary of the entire livestream.

Comment insights

The extracted YouTube comments do not provide reliable speaker-specific audience reactions for Tejas Kumar (IBM). So this section should not pretend there is detailed sentiment about the talk. The useful audience-facing read is instead content-based: this segment is valuable for viewers who care about agent harness primitives, loop control, and trust over black box models, especially the concrete implementation choices and operating constraints called out in the transcript.

Deep research

The research value of this talk is the practical architecture behind agent harness primitives, loop control, and trust over black box models. Tejas Kumar (IBM) is not only making a broad claim; the useful details are the concrete mechanisms named in the transcript: Claude for slides/drafts, ChatGPT / AGI builder stack, Exa search primitive, Simular computer-use agents, Cursor / Baby Cursor, ElevenLabs speech/turn-taking stack.

The main question to take away is how those mechanisms change the workflow. What becomes cheaper, what needs a stronger checkpoint, and what must remain human-owned? For this talk, the strongest evidence is in the speaker’s examples rather than in generic AI optimism. Use the named tools and operating choices as the starting point for further research, then validate whether the same pattern fits your own environment, security constraints, and evaluation loop.

Verdict

• The talk contains a specific operating lesson about agent harness primitives, loop control, and trust over black box models: Agree. The speaker gives enough segment-level evidence to extract concrete implications rather than treating it as generic conference commentary.
• The named tools/examples should be copied blindly: Disagree. They are useful design references, but each needs to be checked against local security, data, latency, cost, and human-review requirements.
• The most valuable part is the concrete workflow detail: Agree. The strongest takeaways are the mechanisms, constraints, and examples the speaker actually names.
• The implementation details are transcript-supported: Agree. This page cites details such as Claude for slides/drafts, ChatGPT / AGI builder stack, Exa search primitive, Simular computer-use agents.
• Human accountability disappears when agents improve: Disagree. The recurring production pattern is to move execution into tools while keeping ownership, review, and failure handling explicit.

Screen-level insights

• 49:51 — opening frame: Tejas Kumar (IBM) frames the talk around agent harness primitives, loop control, and trust over black box models, with the useful setup being: “various tech companies with with really great teams and learning from the best. In fact, I’m not really here to show you uh opinions, but just facts of lessons I’ve learned, not from myself, but from uh very very smart people, people who are far smarter than m…”
• 51:54 — Claude for slides/drafts: The talk shows or names this as part of the actual workflow. The relevant evidence is: “maybe some people one or two people here. If you’re the the vast majority of us, what you do is you send a prompt to some vendor with a black box and you say, “Hey, do this for me.” And then you hope for the best, right?”
• 49:21 — ChatGPT / AGI builder stack: The talk shows or names this as part of the actual workflow. The relevant evidence is: “would be so lost without them. Excuse me one second. Oh my god, he’s spoiling my slides. That’s It’s all good. Let’s go here. There we go. That’s me. Okay. Hello. I’m the yellow hand. See, it’s way Hi, I’m Tis. Hello, everybody.”
• 53:27 — Exa search primitive: The talk shows or names this as part of the actual workflow. The relevant evidence is: “we think about a harness like cloud code or codecs, they have tools. read and write from the file system. Search the web, right? Number two, there’s a language model.”
• 51:54 — Simular computer-use agents: The talk shows or names this as part of the actual workflow. The relevant evidence is: “maybe some people one or two people here. If you’re the the vast majority of us, what you do is you send a prompt to some vendor with a black box and you say, “Hey, do this for me.” And then you hope for the best, right?”
• 1:03:45 — closing implication: The later part of the talk turns the idea into a practical takeaway: “final form? We add a file. We call it login handler. And what does this function actually do? It’s just a function. But here’s what it does. This is the line that’s important. Um if we’re not on the login page, don’t do anything. So this function is a no.”

Verification notes

Verified against the extracted transcript for Tejas Kumar (IBM)’s talk on agent harness primitives, loop control, and trust over black box models. The supported claims in this page are based on concrete tools/artifacts named in the talk: Claude for slides/drafts, ChatGPT / AGI builder stack, Exa search primitive, Simular computer-use agents, Cursor / Baby Cursor, ElevenLabs speech/turn-taking stack, Bluelabs relationship AI. I treated auto-caption wording cautiously, kept only details that are explicitly present in the segment transcript, and avoided importing claims from adjacent speakers or from the overall conference description.