A tiny, zero-dependency, provider-agnostic agent tool-loop for TypeScript. The whole thing is one small class: ask an LLM, run the tools it asks for, feed the results back, repeat until it answers. Bring your own model.
I built an AI-agent workshop (Atelier) where agents do real work on a git repo — and wrote the agent loop from scratch rather than reaching for an SDK. This is that core, pulled out and generalized: no framework, no provider lock-in, nothing to learn but one interface.
npm i @narimangardi/agent-loopDefine some tools, plug in a provider, and run:
import { Agent } from '@narimangardi/agent-loop';
import type { Tool } from '@narimangardi/agent-loop';
const getWeather: Tool<{ city: string }> = {
name: 'get_weather',
description: 'Get the current weather for a city.',
parameters: {
type: 'object',
properties: { city: { type: 'string' } },
required: ['city'],
},
execute: async ({ city }) => `It's 24°C and clear in ${city}.`,
};
const agent = new Agent({
provider: openai, // see "Plug in a model" below
tools: [getWeather],
system: 'You are a concise assistant.',
});
const result = await agent.run('What should I wear in Erbil today?');
console.log(result.text); // the final answer
console.log(result.steps); // how many round-trips it tookrun() is the entire loop:
- Send the conversation + tool specs to the provider.
- If the provider returns a message, that's the answer — return it.
- If it returns tool calls, run them (concurrently within a turn) and append the results.
- Go back to step 1 (up to
maxSteps, default 10).
Unknown tools and thrown errors are handed back to the model as text, so it can recover instead of crashing the loop.
Pass optional hooks to watch it run — for logging, a progress UI, or tracing:
const agent = new Agent({
provider,
tools: [getWeather],
onStep: (n) => console.log(`step ${n}`),
onToolCall: (call) => console.log(`→ ${call.name}`, call.arguments),
onToolResult: (call, output) => console.log(`← ${call.name}: ${output}`),
});Hooks may be async — the loop awaits them.
There's one interface to implement — map your LLM's tool-calling API to a
CompletionResponse:
import type { Provider } from '@narimangardi/agent-loop';
const openai: Provider = {
async complete({ messages, tools }) {
const res = await fetch('https://api.openai.com/v1/chat/completions', {
method: 'POST',
headers: {
'content-type': 'application/json',
authorization: `Bearer ${process.env.OPENAI_API_KEY}`,
},
body: JSON.stringify({
model: 'gpt-4o-mini',
messages: toOpenAiMessages(messages), // small adapter you write
tools: tools.map((t) => ({ type: 'function', function: t })),
}),
});
const { choices } = await res.json();
const message = choices[0].message;
if (message.tool_calls?.length) {
return {
kind: 'tool_calls',
toolCalls: message.tool_calls.map((c: any) => ({
id: c.id,
name: c.function.name,
arguments: JSON.parse(c.function.arguments),
})),
};
}
return { kind: 'message', content: message.content };
},
};The same shape works for Anthropic, Gemini, Ollama, or anything else — it's just "messages + tools in, message-or-tool-calls out."
Complete, typechecked adapters are in examples/openai.ts
and examples/anthropic.ts — the same interface mapped
onto two very different APIs — plus a runnable
examples/weather-agent.ts.
Deliberately small. Worth knowing:
- No streaming.
run()resolves once, with the final text. - One run per call. Multi-turn chat is yours to drive (keep calling
run, or hold the returnedmessages). - No retries / rate-limit handling. Wrap your
Providerfor that. - No argument validation. Tools receive whatever the model sends; validate
inside
executeif you need to.
npm install
npm test # vitest
npm run build # tsup → dist (esm + cjs + d.ts)MIT — see LICENSE.