AI Tools
The words that come with AI agents — tool, loop, harness, skill, plugin — explained in the order they build on each other, then a short list of tools worth using for code, testing, images, video and building your own, with which one to pick when.
How the pieces fit
A model only turns text into text. Everything that makes it do things is wrapped around it, layer by layer — each term below is one of those layers.
The thing that predicts the next token.
A large language model takes text (and often images) in and produces text out. On its own it cannot read files, browse or remember anything between calls — everything it knows about your task has to be in the request.
e.g. Claude, GPT, Gemini, Llama, DeepSeek, Qwen.
Not the app. ChatGPT and Claude.ai are products built around a model; the model is the engine inside.
Everything the model can see in one request.
The system prompt, the conversation so far, file contents, tool results — all of it is packed into the context window, which has a fixed size measured in tokens. When it fills up, something has to be summarised or dropped.
e.g. A coding agent pasting three source files and your question into one request.
Not memory. Nothing survives to the next request unless the app sends it again.
A function the model may ask the app to run.
The app describes each tool — a name, a description and a JSON schema for its arguments. The model replies with "call read_file with path=…" instead of prose; the app runs it and sends the result back. The model never executes anything itself.
e.g. read_file, run_shell, web_search, query_database.
Not an "AI tool" in the product sense. In agent vocabulary a tool is one callable function.
Call the model, run its tools, repeat until done.
The loop is what turns a chat model into something that does work: send context → model asks for a tool → run it → append the result → call the model again. It stops when the model answers without asking for a tool, or hits a limit.
e.g. Fix a failing test: read the test → run it → read the source → edit → run again → report.
Not a cron-style loop. "/loop" in Claude Code re-runs a whole prompt on a schedule; the agent loop is the inner cycle of one task.
A model plus tools plus a loop, pointed at a goal.
An agent decides its own next step rather than following a fixed script. The same model becomes a different agent depending on its instructions and which tools it is given — a read-only research agent and a code-editing agent can share one model.
e.g. A support agent that looks up an order, checks the refund policy and drafts a reply.
Not a workflow. A workflow's steps are decided by the author in advance; an agent's are decided by the model at run time.
The program wrapped around the model that runs the loop.
The harness owns everything the model cannot: the loop itself, the built-in tools, permissions and sandboxing, what goes into the context and when to compact it, and the UI. Two products on the same model can behave very differently because their harnesses differ.
e.g. Claude Code, Cursor's agent, OpenAI Codex CLI, Gemini CLI.
Not the model. Swapping the model changes how well it reasons; swapping the harness changes what it is able to do.
A standard plug for giving any harness new tools.
The Model Context Protocol lets a separate process expose tools (and resources and prompts) to any harness that speaks MCP. Write a GitHub or database connector once and it works in Claude Code, Cursor, VS Code and others.
e.g. A MySQL MCP server exposing list_tables and execute_query.
Not a skill. MCP adds new actions the agent can take; a skill adds know-how about how to take them.
A folder of instructions the agent loads only when relevant.
A skill is a SKILL.md file (plus optional scripts and references) with a name and a one-line description. Only the description sits in context; the full instructions are read when a task matches, so you can install many without filling the context window.
e.g. A deploy-prod skill describing how to tag a release and push it.
Not a tool. A skill contains no new capability — it teaches the agent a procedure using the tools it already has.
A second agent the main one hands a sub-task to.
The subagent runs its own loop in a fresh context and returns only a summary. It keeps big searches and file dumps out of the main conversation, and lets independent jobs run in parallel.
e.g. An explore agent that sweeps 200 files and reports back the three that matter.
Not a separate product. It is the same harness starting another loop with narrower instructions and tools.
Your own script the harness runs at a fixed moment.
Hooks fire on events — before a tool runs, after a file is edited, when the agent stops. They are deterministic: the harness runs them every time, rather than hoping the model remembers an instruction.
e.g. Run the formatter after every file edit; block rm -rf before it executes.
Not a prompt instruction. "Always run lint" in a prompt is a request; a hook is a guarantee.
An installable bundle of skills, commands, agents, hooks and MCP servers.
A plugin is the packaging layer: one install that brings a coherent set of the pieces above, usually from a marketplace or a git repo. It exists so a team can share a working setup instead of copying files around.
e.g. A code-review plugin shipping a /review command, a reviewer subagent and a lint hook.
Not a capability of its own. Everything a plugin does is done by the skills, hooks and servers inside it.
Retrieve relevant documents, then let the model answer from them.
Retrieval-augmented generation searches your own data — usually via embeddings in a vector database — and puts the best matches into the prompt. It is how a model answers about documents it was never trained on.
e.g. A help-centre bot that finds the three closest articles before answering.
Not fine-tuning. RAG changes what the model reads per request; fine-tuning changes the model's weights.
Tool vs MCP vs skill vs hook vs plugin
| Piece | What it adds | When it runs | What it looks like |
|---|---|---|---|
| Tool | One new action | The model chooses to call it | A function + JSON schema |
| MCP server | A set of tools, reusable across harnesses | The model calls one of its tools | A separate process speaking MCP |
| Skill | Know-how, not new actions | The task matches its description | A folder with SKILL.md |
| Hook | A guaranteed side effect or check | Always, on a fixed event | A shell command in settings |
| Plugin | All of the above, installed together | Whenever its parts do | A package from a marketplace |
Recommended tools
A short list per job rather than every product on the market. Pricing and model versions change monthly, so check the vendor’s site before committing.
Reading GitHub stars and weekly downloads…
Coding agents
Harnesses that read, edit and run code in your repo. The model matters, but the harness decides how much of your project it can see and do.
Anthropic
Autonomous multi-file work from the terminal or IDE
Terminal-first agent with skills, hooks, subagents, plugins and MCP. Runs in the CLI, VS Code, JetBrains, desktop and web.
Anysphere
An AI-first editor with fast inline edits
VS Code fork with tab completion, an agent panel and rules files. Lets you switch between models from several vendors.
GitHub / Microsoft
Teams already living in GitHub
Completions and agent mode in VS Code and JetBrains, plus a cloud coding agent that works from issues and opens PRs.
OpenAI
OpenAI models in a terminal or cloud sandbox
Open-source CLI plus a cloud version that runs tasks in parallel sandboxes. Included with ChatGPT plans.
A free terminal agent with a very large context
Open-source terminal agent for Gemini models, with MCP support and a generous free tier on a personal Google account.
Community
Git-native pair programming with any model
Commits every change it makes, works with almost any API or local model. Pay only for the model you plug in.
| Which coding agent? | |
|---|---|
| Claude Code | You want to hand over whole tasks and customise the agent with skills, hooks and subagents. |
| Cursor | You mostly write the code yourself and want fast completions and inline edits in an editor. |
| GitHub Copilot | Your company already pays for GitHub and you want agents working from issues and PRs. |
| Codex / Gemini CLI | You prefer OpenAI or Google models, or want an open-source CLI you can read. |
| Aider | You want every change as a git commit and the freedom to use any model, including local ones. |
Testing agents
End-to-end tests written as goals in plain language; an agent drives the browser or phone to reach them, instead of you scripting every click.
TesterArmy
End-to-end tests described as goals, for web and mobile
Write a goal in plain language and an agent drives Chromium, Firefox, WebKit or an iOS / Android simulator to reach it, then checks the result with locators and assertions. Replays past runs without model calls while the app is unchanged. `npx e2e init`; bring your own model; runs in CI with PR reports.
Image
Text-to-image and image editing. The split is between aesthetics, following instructions exactly, and running it yourself.
Midjourney
The most striking, art-directed look
Strong default aesthetics and style references. Weaker at exact text and precise instructions; subscription only.
OpenAI
Following detailed instructions and rendering text
Conversational — describe, then refine in follow-ups. Good at legible text, diagrams and edits to an uploaded image. Also via the OpenAI API.
Editing photos while keeping the subject consistent
Fast conversational editing: change the background, outfit or pose and the same person stays recognisable. In the Gemini app and API.
Black Forest Labs
Photorealism, with open weights to self-host
Top-tier quality via API and many hosts; some variants have downloadable weights for ComfyUI or your own server.
Comfy Org
Full control over local image and video pipelines
Node-graph UI for Stable Diffusion, FLUX, video models, LoRAs and ControlNet. Free and local; steep learning curve, needs a decent GPU.
Ideogram
Logos, posters and typography
Built around getting words in images right. Good for marketing graphics where the text has to be spelt correctly.
Adobe
Commercial work inside Photoshop and Illustrator
Trained on licensed content and built into Creative Cloud (Generative Fill). The safe choice where usage rights matter.
| Which image tool? | |
|---|---|
| Midjourney | It should look beautiful and you are flexible on the details. |
| ChatGPT / Gemini | It must follow the brief exactly, contain readable text, or edit an existing photo. |
| Ideogram / Recraft | The output is a logo, poster, icon or SVG. |
| Adobe Firefly | It is commercial work and you need clear usage rights. |
| FLUX + ComfyUI | You want it free, private and fully controllable on your own GPU. |
Video
Text- or image-to-video. Clips are short — seconds, not minutes — so real projects stitch many generations together.
Google DeepMind
Realistic clips with generated sound and dialogue
Generates synchronised audio with the video. Available in Flow, the Gemini app and the Gemini API.
OpenAI
Physically plausible scenes and cameos
Text-to-video with audio, in its own app and via the API.
Runway
Editing and controlling footage, not just generating it
Generation plus pro tools: motion brush, camera control, video-to-video restyling, act-one performance transfer.
Kuaishou
Image-to-video with strong motion, at a good price
Popular for animating a still image; realistic human movement and longer extended clips.
Luma AI
Quick cinematic shots and keyframe transitions
Set a start and end frame and it generates the motion between them. Simple interface, fast iterations.
| Which video tool? | |
|---|---|
| Veo / Sora | You need the most realistic clip, with sound, from a text prompt. |
| Kling / Luma | You are animating a still image or need many cheap iterations. |
| Runway | You are editing or restyling real footage and need fine camera and motion control. |
| HeyGen | Someone needs to talk to camera — explainers, training, translated versions. |
LLM frameworks
Libraries for building your own agents, RAG pipelines and chat features in code.
LangChain
Swapping between many model providers and integrations
Python and JS. A common interface over models, vector stores, loaders and tools, plus a prebuilt agent. The biggest integration catalogue.
LangChain
Stateful, multi-step agents you need to control precisely
Models an agent as a graph of nodes and edges with persisted state — human approval steps, retries, resuming after a crash.
LlamaIndex
RAG over your own documents
Focused on ingesting, parsing, indexing and querying data — PDFs, tables, knowledge bases. Python and TS.
Vercel
AI features in a TypeScript / Next.js app
Streaming chat UI hooks, tool calling and structured output with one API across providers. The natural fit for this site's stack.
Anthropic
Building on the same harness as Claude Code
The Claude Code loop as a library — file and shell tools, context compaction, subagents, MCP and permissions out of the box. TS and Python.
OpenAI
Lightweight multi-agent handoffs
Small set of primitives — agents, tools, handoffs, guardrails — with built-in tracing. Python and JS.
CrewAI
Role-based teams of agents
Define agents as roles (researcher, writer, reviewer) with tasks, and let the crew collaborate. Python.
| LangChain, LangGraph or something else? | |
|---|---|
| LangChain | A straightforward agent or chain where swapping providers and integrations matters most. |
| LangGraph | Long-running, branching agents that need saved state, retries or a human approval step. |
| LlamaIndex | The hard part is the documents — parsing, chunking and retrieving them well. |
| Vercel AI SDK | You are building a chat or AI feature into a TypeScript web app. |
| Claude / OpenAI Agents SDK | You are committed to one vendor and want its agent loop without building your own. |
Visual builders
Drag-and-drop canvases for chaining models, tools and data — prototypes and internal automations without writing the plumbing.
FlowiseAI
LangChain-style chatbots and RAG without code
Drag LangChain / LlamaIndex nodes onto a canvas, get an API endpoint and an embeddable chat widget. Self-host with npm or Docker.
DataStax / IBM
Visual flows you can drop into Python code
Python-based canvas; every component is editable Python, and flows can be exported, served as APIs or exposed as MCP tools.
n8n
Business automation that happens to use AI
Hundreds of app integrations (Slack, Sheets, CRMs) with AI agent nodes on top. Fair-code licence; self-host free or use their cloud.
LangGenius
Shipping a full LLM app with a knowledge base and admin UI
Chat apps, workflows and agents plus built-in RAG, prompt management, logs and user-facing web apps. Self-host or cloud.
| Flowise, Langflow, n8n or Dify? | |
|---|---|
| Flowise | A chatbot or RAG endpoint quickly, and you already think in LangChain terms. |
| Langflow | The same, but your team writes Python and wants to customise components. |
| n8n | The job is mainly connecting apps — AI is one step in a bigger automation. |
| Dify | You need a complete product: knowledge base, prompt versions, logs and an end-user UI. |
Run locally
Download open-weight models and run them on your own machine — private, offline and free per call, limited by your RAM and GPU.
Ollama
Running open models from the command line or an API
`ollama run llama3` and you have a model plus a local OpenAI-compatible endpoint that LangChain, Flowise and n8n can call.
| Ollama or LM Studio? | |
|---|---|
| Ollama | You want a background service and API for other tools to call. |
| LM Studio | You want to browse and compare models in a GUI before wiring anything up. |
Model APIs
Models you call from your own code for one narrow job rather than chat with — cheaper, faster and more predictable than a general LLM at that job.
TypeSafe AI
Fast typed decisions in code: classify, route, rank, verify
A "System One" model, not an LLM: send a structured question, get back a typed answer (a choice or score) with a calibrated confidence, so code can act or escalate. Generates no text, so the output always fits the schema, though the answer can still be wrong. Much cheaper and faster than an LLM for these jobs. Early access.
Instructions
A plain-language reference for AI agent vocabulary and a short, opinionated list of AI tools with links and when to pick each.
- Read How the pieces fit top to bottom — the terms are ordered so each one builds on the last, from the model up to plugins.
- Check the Tool vs MCP vs skill vs hook vs plugin table when you are deciding how to extend an agent.
- Under Recommended tools, pick a category button, or leave it on All. Turn on ★ Good only to see just the proven go-to picks.
- Where a category has a Which one? table, use it to choose, then follow the Site or GitHub link.
- On an open-source tool, the line above Site shows its GitHub repo and ★ stars, its weekly downloads on npm and / or PyPI, and how active it is — Active means a push in the last three months; otherwise it says how long since, e.g. 1 yr no commit.
Tips
- The search box filters terms and tools together — try
harness,open source,SVGor a maker such asGoogle. - Badges: Open source means you can self-host it; Free tier means a usable free plan with paid limits; Paid means a subscription is needed. ★ Good marks a proven first choice in its category; new, niche or waitlisted tools don’t get it yet.
- The page holds no version numbers or prices on purpose — both change too often. The vendor’s site is the source of truth.
- Stars, last commit and downloads are read live from GitHub, npm and PyPI and cached for six hours. Hover a number for the exact figure. “…” means it is still loading, “—” that it is unavailable right now.
- Your search text, category and Good only setting are kept in local storage on this device only; nothing is sent anywhere.
- Hit Example and click the search box to look up
langchain.