Filter
Exclude
Time range
-
Near
Replying to @htekdev
πŸ˜‚
1
5
Replying to @htekdev
Well…. That would be really cool if you did have that robot. 😜
1
13
May 19
Most multi-agent systems collapse in production because every agent tries to be everything. I run 53 AI agents on GitHub Copilot β€” finances, meals, health, content, NICU care. 6 months autonomous. Zero chaos. 4 patterns survived: - Domain Agents (permanent, memory-rich) - Task Agents (stateless, ephemeral) - Orchestrators (pure delegation) - Team Agents (goal-scoped lifecycle) The key insight: fresh agent per cron job. No session reuse. Same pattern MegaFlow (arXiv), HearthNet, and O'Reilly's "Agentic Mesh" converge on independently. Full breakdown β€” patterns, cron architecture, orchestrator discovery: htek.dev/articles/53-agents-… Newsletter deep dive with real configs: htek.dev/newsletter/006-53-a… #MultiAgentSystems #GitHubCopilot #htekdev
3
2
93
May 19
The average enterprise runs 12 AI agents. Only 27% are connected to anything. The rest? Shadow agents. Ungoverned. Unmonitored. I compared every agent harness head-to-head β€” Copilot, Claude Code, OpenAI SDK, Bedrock, Vertex, LangChain, Cursor, Devin, and more. Key finding: only 3 platforms actually own the agentic loop. The rest are just API wrappers with marketing. Full live comparison (continuously updated): htek.dev/articles/all-agent-… #AgenticAI #AIEngineering #htekdev
2
2
148
May 14
Context Engineering > Prompt Engineering. 43 AI agents. 60 reusable skills. 30 cron jobs. Zero babysitting. The 5 patterns that make it work: β†’ 4-tier memory (core β†’ working β†’ long-term β†’ events) β†’ Reusable skills any agent can invoke β†’ Shared constitution for consistent behavior β†’ Domain ownership β€” each agent owns its data β†’ Cron-driven autonomy β€” runs on schedule, not on command The model matters less than you think. Context architecture matters more. Full deep dive: htek.dev/articles/context-en… #ContextEngineering #AIAgents #htekdev
1
2
26