It follows a 5-step loop: Plan → Reason → Act → Reflect → Respond. Adding a WebSearchTool to test extensibility, the agent initially failed its first search, reflected on poor results, adapted its query, and then succeeded. This behavior wasn’t programmed; it emerged naturally from the architecture.

Five hours later, I integrated a FileManagerTool — it worked on the first try. Like code compiling first time, except this was intelligence composing zero-config.

Key insight: separating cognitive operations from tool orchestration enables true composability. Most frameworks conflate these, resulting in brittle, unpredictable agents.

Commit timeline: https://github.com/iteebz/cogency

It’s pip-installable (pip install cogency) with production-ready components. Currently dogfooding across projects.

Seeking feedback from the community on the approach and implementation.