Loading the homepage
Tech Agents covers AI agents, large language models, developer tooling and the engineering underneath modern software — at the level of detail you need to make a decision, not the level you need to repeat a headline.
Four beats, chosen because they are the ones that actually change how software gets built.
Planning loops, tool and function calling, memory and context budgets, multi-agent orchestration, and the operational questions that only appear once software runs unattended.
Retrieval pipelines, streaming interfaces, evaluation harnesses, cost and latency budgets, and the failure handling that separates a demo from something people depend on.
Coding assistants, agent frameworks, vector stores and model providers — described by what each one is genuinely the right answer to, and where it stops being that.
What changes in a threat model once a language model can call tools: untrusted input reaching privileged actions, permission scoping, sandboxing and blast-radius control.
Not aspirations. Each one is a constraint on what can be published here at all.
The subject and the method are the same thing here. An agent is a model wrapped in a loop that can call tools, inspect its own output and keep going — and that pattern is now the interesting part of a great deal of software rather than a novelty bolted onto it. So the publication is organised around it: what an agent is, what it costs to run one, where the architecture leaks, and what a threat model looks like once a model can act rather than only answer.
It also shapes how this site is built. The agents section documents seven working patterns — research, coding, SEO, content, data, automation and security — as concrete roles rather than metaphors. The SEO agent in particular is not a diagram: it is a real analyser in this repository that reads every published article, scores it against a fixed hundred-point model and produces a report a person then reviews. It never edits published copy, and the human-review step is not optional. Writing about agents while running one is the cheapest way to stay honest about what they can and cannot do.
Where a subject needs a definition rather than an argument it goes in the glossary. Where it needs a side-by-side it goes in comparisons. Where it needs a shortlist it goes in the tools directory. The reference material is kept apart from the opinion on purpose, so you can use one without having to agree with the other.
Coverage is organised into four desks — the editorial desk plus agent systems, applied engineering, and security and platform — and every article carries the desk it came from.
The four author profiles shipped today are placeholders. They exist so the byline, archive and structured-data systems are complete and working, and they deliberately contain no invented credentials, employers, awards or social accounts — inventing a person is exactly the kind of fabrication the standards above rule out. Each profile is flagged as a placeholder in the underlying data and says so on its own page. They will be replaced with named contributors, and the flag dropped, before any of this is presented as reported journalism.
Browse the desks to see what each one covers.
One desk, one address. Corrections are the fastest thing we act on.