PUBLIC VIEWPOINTS

João (Joe) Moura

1 sources · 4 viewpoints · 4 topics

Content updated:

João (Joe) Moura on agent memory architecture, AI agent evolution, enterprise adoption metrics. Explore 4 viewpoints by topic, with evidence from 1 source.

Explore connections

Viewpoints by topic

Attributed viewpoints, ordered by source publication date. A snapshot of these conversations, not a definitive statement of someone’s beliefs.

Translations are for reading; original excerpts remain the evidence.

AI agent evolution

View this topic
AI agent evolution

Shift to autonomous, self-evolving agents

In early 2026, AI is moving beyond simple prompt-based interactions toward autonomous, long-running agents that can break down goals, execute code, and operate independently — a shift likened to the rise of the modern web stack.

Supporting evidence

Orchestrating Self-Evolving Agents with CrewAI and NVIDIA NemoClaw | CrewAI

Original excerpt

The technology landscape in early 2026 is undergoing a shift similar to the rise of the modern web stack. AI is moving beyond simple prompt-based interactions toward autonomous, continuously evolving agents. These long-running agents, which many experienced recently on a more personal level through “claws”, can break down goals, execute code, and operate independently for extended periods.

enterprise adoption metrics

View this topic

CrewAI enterprise scale claims

The article reports that CrewAI has powered roughly 2 billion agentic executions over the past year and is currently used by more than 60% of Fortune 500; it describes this as demonstrating readiness for enterprise workloads.

Supporting evidence

Orchestrating Self-Evolving Agents with CrewAI and NVIDIA NemoClaw | CrewAI

Original excerpt

This architecture has already proven itself at scale. CrewAI has powered roughly 2 billion agentic executions over the past year and is currently used by more than 60% of Fortune 500, demonstrating readiness for enterprise workloads.

runtime security design

View this topic

Infrastructure-level policy enforcement

NVIDIA OpenShell Runtime enforces every action at the infrastructure level—not within the agent’s own code—so even if an agent’s internal logic changes or behaves unexpectedly, the runtime blocks actions violating defined security policies.

Supporting evidence

Orchestrating Self-Evolving Agents with CrewAI and NVIDIA NemoClaw | CrewAI

Original excerpt

A key innovation is that the NVIDIA OpenShell Runtime enforces every action at the infrastructure level, not within the agent's own code. This means that even if an agent's internal logic changes or behaves unexpectedly, the runtime will still block any action that violates defined security policies .A key innovation in NemoClaw is that every action is enforced at the infrastructure level , not within the agent’s own code. This design ensures that even if an agent’s internal logic changes or behaves unexpectedly, the runtime will still block any action that violates defined security policies.

agent memory architecture

View this topic

Persistent cognitive memory for agents

CrewAI provides persistent cognitive memory for both Crews and Flows, enabling agents to retain information across sessions, accumulate knowledge over time, and strategically forget — shifting from stateless interactions to learning-capable, long-running workflows.

Supporting evidence

Orchestrating Self-Evolving Agents with CrewAI and NVIDIA NemoClaw | CrewAI

Original excerpt

In addition, both Crews and Flow and its agents get a persistent cognitive memory layer, allowing them to retain information across sessions and gradually accumulate knowledge, consolidating and even strategically forgetting over time. This shift, from stateless interactions to agents with memory, marks an important step in optimizing long-running agent workflows that can learn from executions itself and human feedback.
Context

Persistence is also essential when agents need to pause for human input or recover from interruptions. CrewAI’s @persist() decorator automatically saves workflow state so execution can resume later.

Statements by source date1

Statements are ordered by the original source publication date; differences in wording do not establish a change of position.