Operating layer
Agent Techniques Weekly
September 19, 2026No. 22
For builders operationalizing agentic work.
Complete issue archive.
Techniques, harnesses, skills, connectors, proof of value, and enterprise controls for agentic work.
Subscribe via RSSPublished issues
22 issues · newest first
- No.22
Week 38 of 2026 · September 19, 2026
A live agent can now talk while it works, which makes cancellation and state reconciliation the new control
- No.21
Week 37 of 2026 · September 12, 2026
Three vendors shifted agent work beyond the session, but only two disclose delegation architecture
- No.20
Week 36 of 2026 · September 5, 2026
Separate execution from approval, then attribute model and runtime gains under controlled effort
- No.19
- No.18
- No.17
- No.16
- No.15
- No.14
- No.13
- No.12
- No.11
- No.10
Week 26 of 2026 · June 27, 2026
Background agents crossed from novelty to operations: the hard part is the control loop.
- No.09
Week 25 of 2026 · June 20, 2026
Loop Engineering named the shift: the prompt is no longer the unit of work.
- No.08
Week 24 of 2026 · June 13, 2026
Open-source harnesses pushed agents toward memory, channels, and self-improving skills.
- No.07
Week 23 of 2026 · June 6, 2026
Always-on personal agents made identity, policy, and audit trails first-class design problems.
- No.06
Week 22 of 2026 · May 30, 2026
Domain agent packs showed that the next frontier is reusable professional workflow.
- No.05
Week 21 of 2026 · May 23, 2026
MCP and skills made the agent harness more important than the model choice.
- No.04
Week 20 of 2026 · May 16, 2026
Subagents turned delegation from a single conversation into an agent team pattern.
- No.03
Week 19 of 2026 · May 9, 2026
Agentic work became a review problem: the scarce skill is defining good and done.
- No.02
Week 18 of 2026 · May 2, 2026
The agent operating layer moved from prompt craft to repeatable delegation.
- No.01
Week 17 of 2026 · April 25, 2026
Agentic work crossed from prompt craft into capability-gated operating practice.
Methodology
What survives into every issue
- Explain the transferable technique before naming the tool.
- Separate skills, connectors, plugins, templates, and harnesses from product launches.
- Treat large value claims as provisional until the workflow, baseline, and verification method are visible.
- Score each item through permissions, auditability, verification, data access, cost, and approval gates.