From coding to Knowledge work agents — Karan Vaidya, Composio: Summary & Key Takeaways | VibeDigest

From coding to Knowledge work agents - Karan Vaidya, Composio

youtube.com21 min

Summary

Knowledge-work agents lag behind coding agents because they lack the surrounding infrastructure…Read more

Knowledge-work agents lag behind coding agents because they lack the surrounding infrastructure that makes autonomous action trustworthy. The next bottleneck is not model capability but six primitives: centralization, history, context, verification, governance, and reversibility.

Key ideas

Coding autonomy emerged from an ecosystem, not models alone
Model improvements and better harnesses accelerated coding agents, but neither explains their reliability by itself. Software engineering already supplied repositories, commit histories, tests, CI/CD, review systems, linters, and rollback mechanisms. These systems give agents information, feedback, constraints, and recovery paths. Knowledge work agents are being asked to operate without comparable support.
Why it matters: Improving the model alone will not reliably unlock autonomous knowledge work; builders must also design the operational substrate around it.
Supporting evidence
It only worked because all the infrastructure and systems around coding were literally meant for agents.
Model improvements and better harnesses accelerated coding agents, but neither explains their re…Show more
Model improvements and better harnesses accelerated coding agents, but neither explains their re…Show moreShow less
Model improvements and better harnesses accelerated coding agents, but neither explains their reliability by itself. Software engineering already supplied repositories, commit histories, tests, CI/CD, review systems, linters, and rollback mechanisms. These systems give agents information, feedback, constraints, and recovery paths. Knowledge work agents are being asked to operate without comparable support.
Why it matters: Improving the model alone will not reliably unlock autonomous knowledge work; builders must also design the operational substrate around it.
Supporting evidence
It only worked because all the infrastructure and systems around coding were literally meant for agents.
Centralization supplies the missing source of truth
A coding agent begins with a repository that contains much of the relevant implementation and op…Show moreShow less

Why Coding Agents Are Easier to Trust

	Coding agents	Knowledge-work agents
Source of truth	Repository and infrastructure-as-code provide a central working surface.	Relevant information is fragmented across many applications and logins.
History	Git records changes and supports inspection of prior decisions.	Processes and outcomes are scattered, leaving the agent with little usable memory.
Verification	Tests, types, compilers, linters, and formatters automatically check work.	Technically valid actions may still be inappropriate or harmful.
Governance	Branches, reviewers, code owners, and deployment boundaries create layered controls.	Permissions are scattered and behavioral limits are often left to fragile prompts.
Recovery	Commits can usually be reverted after a mistake.	Sent messages, completed transfers, and hard deletes may be permanent.

Read the full digest

Overview

The speaker argues that coding became the dominant arena for autonomous agents not merely because models improved, but because software engineering already possessed an agent-ready operating environment. Repositories centralize relevant information; Git preserves history; code and conventions provide context; tests verify outputs; permissions and reviews govern deployment; and version control makes mistakes reversible. Knowledge work lacks equivalent infrastructure: customer information is fragmented across applications, organizational processes are poorly recorded, quality is difficult to test, permissions are scattered, and many actions—such as sending email or transferring money—cannot be undone. Composio’s proposed solution is a shared infrastructure layer that connects applications and credentials, records every action, derives reusable organizational skills, validates work against prior examples, simulates risky actions in sandboxes, and enforces access controls and behavioral policies outside the model’s prompt. The central thesis is that trustworthy autonomy depends less on asking agents to behave correctly and more on constructing systems that constrain, inspect, and recover from their behavior. As models become capable enough to perform hiring, sales, support, and finance tasks, infrastructure—not intelligence—becomes the limiting factor.

Sections

Strategic Implications

Higher-level conclusions implied by the six-primitives framework.

Agent reliability is an emergent property of the full operating environment. Model capability determines what an agent can attempt, while infrastructure determines whether the attempt is informed, inspectable, bounded, and recoverable.
Centralized action records can become a learning loop: integration produces observability, observability exposes recurring patterns, and those patterns can be distilled into organization-specific skills.
Trust does not require eliminating every failure. It requires making failures visible, limiting their blast radius, and preventing irreversible consequences.
The safest path to greater autonomy is stronger external control. When permissions, policies, simulations, and rollback mechanisms are reliable, fewer routine tasks require human interruption.

Coding Agents Versus Knowledge-Work Agents

The structural differences that explain their unequal levels of autonomy.

Coding agents usually begin near a consolidated source of truth, while knowledge-work agents must assemble fragmented information from multiple applications and authentication boundaries.
Coding outputs can be checked automatically through tests and static tooling, whereas knowledge-work outputs often require evaluating appropriateness, timing, tone, and real-world consequences.
Code failures are commonly reversible after execution, while many knowledge-work failures must be intercepted before execution because their effects are permanent.

Core Primitives

The six capabilities proposed as prerequisites for trustworthy knowledge-work agents.

Centralization: a unified place where applications, connections, credentials, information, and agent access are assembled.
History or record: a durable, cross-application log of what the agent touched, skipped, completed, or failed to complete.
Context: knowledge of system architecture, organizational workflows, quality standards, and individual preferences.
Verification: checks that evaluate an agent's output and intended actions before they produce unacceptable real-world effects.
Governance: externally enforced access boundaries and behavioral policies calibrated to an action's blast radius.
Reversibility: the ability either to undo an executed action or to simulate an irreversible action before it reaches production.

Proposed Infrastructure Design

Specific architectural mechanisms and operating data mentioned in the talk.

Connected applications, logins, and permissions are exposed through one integration layer so agents do not independently stitch together every system.
Cross-application action logging records resources touched or skipped and whether operations succeeded or failed; accumulated records are then distilled into reusable skills.
Governance has two layers: deterministic capability boundaries controlling resource access, and natural-language policies constraining behavior within that authorized access.
Sandboxed versions of real tools absorb the blast radius of potentially destructive or irreversible actions before approved execution against production systems.
Composio reports more than one billion cumulative tool calls and approximately 300 million tool calls per month.

In Brief Knowledge work agents lag behind coding agents because they lack the surrounding infras…Expand full summary

Overview

Sections

Strategic Implications

Higher-level conclusions implied by the six-primitives framework.

Agent reliability is an emergent property of the full operating environment. Model capability determines what an agent can attempt, while infrastructure determines whether the attempt is informed, inspectable, bounded, and recoverable.
Centralized action records can become a learning loop: integration produces observability, observability exposes recurring patterns, and those patterns can be distilled into organization-specific skills.
Trust does not require eliminating every failure. It requires making failures visible, limiting their blast radius, and preventing irreversible consequences.
The safest path to greater autonomy is stronger external control. When permissions, policies, simulations, and rollback mechanisms are reliable, fewer routine tasks require human interruption.

Coding Agents Versus Knowledge-Work Agents

The structural differences that explain their unequal levels of autonomy.

Coding agents usually begin near a consolidated source of truth, while knowledge-work agents must assemble fragmented information from multiple applications and authentication boundaries.
Coding outputs can be checked automatically through tests and static tooling, whereas knowledge-work outputs often require evaluating appropriateness, timing, tone, and real-world consequences.
Code failures are commonly reversible after execution, while many knowledge-work failures must be intercepted before execution because their effects are permanent.

Core Primitives

The six capabilities proposed as prerequisites for trustworthy knowledge-work agents.

Centralization: a unified place where applications, connections, credentials, information, and agent access are assembled.
History or record: a durable, cross-application log of what the agent touched, skipped, completed, or failed to complete.
Context: knowledge of system architecture, organizational workflows, quality standards, and individual preferences.
Verification: checks that evaluate an agent's output and intended actions before they produce unacceptable real-world effects.
Governance: externally enforced access boundaries and behavioral policies calibrated to an action's blast radius.
Reversibility: the ability either to undo an executed action or to simulate an irreversible action before it reaches production.

Proposed Infrastructure Design

Specific architectural mechanisms and operating data mentioned in the talk.

Connected applications, logins, and permissions are exposed through one integration layer so agents do not independently stitch together every system.
Cross-application action logging records resources touched or skipped and whether operations succeeded or failed; accumulated records are then distilled into reusable skills.
Governance has two layers: deterministic capability boundaries controlling resource access, and natural-language policies constraining behavior within that authorized access.
Sandboxed versions of real tools absorb the blast radius of potentially destructive or irreversible actions before approved execution against production systems.
Composio reports more than one billion cumulative tool calls and approximately 300 million tool calls per month.

From coding to Knowledge work agents - Karan Vaidya, Composio

Summary

Key ideas

Coding autonomy emerged from an ecosystem, not models alone

Centralization supplies the missing source of truth

A record of actions creates both memory and accountability

Why Coding Agents Are Easier to Trust

Ask about this source

Read the full digest

Overview

Sections

Strategic Implications

Coding Agents Versus Knowledge-Work Agents

Core Primitives

Proposed Infrastructure Design

Overview

Sections

Strategic Implications

Coding Agents Versus Knowledge-Work Agents

Core Primitives

Proposed Infrastructure Design