@samrahimi/smol-js 0.7.2 → 0.7.3

package/README.md

@@ -2,22 +2,23 @@
 
 **A TypeScript agentic framework inspired by [smolagents](https://github.com/huggingface/smolagents).**
 
-Build AI agents that solve tasks autonomously using the ReAct (Reasoning + Acting) pattern. Agents can write and execute JavaScript code, call tools, delegate to other agents, and orchestrate complex workflows via YAML definitions.
+Build AI agents that solve tasks autonomously using the ReAct (Reasoning + Acting) pattern. Agents can write and execute JavaScript code, call tools, run shell commands, delegate to other agents, and orchestrate complex workflows via YAML definitions.
 
 [![npm version](https://img.shields.io/npm/v/@samrahimi/smol-js.svg)](https://www.npmjs.com/package/@samrahimi/smol-js)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
 
 ## Features
 
-- **Two Agent Types**:
-  - `CodeAgent` - Writes JavaScript code to solve tasks
-  - `ToolUseAgent` - Uses native LLM function calling (OpenAI-style)
+- **Three Agent Types**:
+  - `CodeAgent` — Writes and executes JavaScript code in a sandboxed VM
+  - `ToolUseAgent` — Uses native LLM function calling (OpenAI-style)
+  - `TerminalAgent` — Executes shell commands on your macOS terminal
 - **YAML Orchestration**: Define complex agent workflows declaratively
-- **Sandboxed Execution**: JavaScript runs in Node's vm module with state persistence
-- **Extensible Tool System**: Built-in tools + easy custom tool creation
+- **Custom Tool Plugins**: Drop standalone `.ts` tool files into a folder — no build step, no config
 - **Nested Agents**: Manager-worker patterns for hierarchical task delegation
+- **Sandboxed Execution**: JavaScript runs in Node's vm module with state persistence
 - **Exa.ai Integration**: Semantic web search, content extraction, and research automation
-- **Dynamic Imports**: Import npm packages on-the-fly via jsdelivr CDN
+- **Dynamic Imports**: Import npm packages on-the-fly in CodeAgent
 - **OpenAI-Compatible**: Works with OpenRouter, OpenAI, Azure, Anthropic, and local servers
 - **Streaming**: Real-time output streaming from the LLM
 - **Memory Management**: Context-aware with truncate/compact strategies
@@ -29,6 +30,12 @@ Build AI agents that solve tasks autonomously using the ReAct (Reasoning + Actin
 npm install @samrahimi/smol-js
 ```
 
+Or run workflows directly without installing:
+
+```bash
+npx @samrahimi/smol-js workflow.yaml --task "Your task here"
+```
+
 ## Quick Start
 
 ### Via CLI (YAML Workflows)
@@ -101,6 +108,8 @@ const result = await agent.run('Calculate the first 10 prime numbers');
 console.log(result.output); // [2, 3, 5, 7, 11, 13, 17, 19, 23, 29]
 ```
 
+---
+
 ## Agent Types
 
 ### CodeAgent
@@ -127,7 +136,7 @@ await agent.run('Analyze the file data.csv and create a summary');
 
 ### ToolUseAgent
 
-Uses native LLM function calling (OpenAI-style tool calling). Better for LLMs with strong tool-calling capabilities.
+Uses native LLM function calling (OpenAI-style tool calling). Best for LLMs with strong structured-output capabilities.
 
 ```typescript
 import { ToolUseAgent, OpenAIModel } from '@samrahimi/smol-js';
@@ -142,6 +151,258 @@ const agent = new ToolUseAgent({
 await agent.run('Search for recent AI papers and summarize the top 3');
 ```
 
+### TerminalAgent
+
+Accomplishes tasks by reasoning about and executing shell commands on your terminal. Tuned for macOS — uses zsh, understands BSD conventions, and gives you full visibility into what it's doing.
+
+```typescript
+import { TerminalAgent, OpenAIModel } from '@samrahimi/smol-js';
+
+const agent = new TerminalAgent({
+  model,
+  maxSteps: 10,
+  commandDelay: 5,    // seconds before running commands (Ctrl+C window)
+  maxOutputLength: 8000, // chars of command output fed back to the LLM
+});
+
+await agent.run('Set up a new Node.js project with TypeScript and Jest');
+```
+
+**How it works:**
+1. Agent reasons about what shell commands to run
+2. Commands are displayed for your review (with a configurable delay — default 5 seconds — so you can Ctrl+C if anything looks wrong)
+3. Commands execute sequentially via `/bin/zsh`
+4. stdout, stderr, and exit codes are captured and fed back as observations
+5. Repeats until the agent signals completion with `FINAL_ANSWER:`
+
+**Key behaviours:**
+- **Verbose by default.** You see the agent's reasoning, pending commands, and live output at every step.
+- **Safety delay.** Every command batch pauses for 5 seconds before execution. Read what's about to run. Press Ctrl+C to abort.
+- **Error recovery.** If a command fails (non-zero exit code), the agent sees the error and tries a different approach.
+- **No user-assigned tools.** TerminalAgent is a pure shell agent. It can only delegate to sub-agents (via the manager-worker pattern) — it doesn't use function-calling tools.
+
+#### TerminalAgent in YAML
+
+```yaml
+name: system-inspector
+description: Gathers system information using shell commands.
+
+model:
+  modelId: anthropic/claude-sonnet-4.5
+  baseUrl: https://openrouter.ai/api/v1
+
+agents:
+  inspector:
+    type: TerminalAgent
+    maxSteps: 5
+    commandDelay: 3
+    customInstructions: >
+      Gather system information: OS version, CPU, RAM, disk usage,
+      and list running processes sorted by CPU. Summarize your findings.
+
+entrypoint: inspector
+```
+
+Run it:
+
+```bash
+npx @samrahimi/smol-js system-inspector.yaml --task "What are my system specs?"
+```
+
+#### TerminalAgent as a Sub-Agent (Manager-Worker)
+
+One of the most powerful patterns: a ToolUseAgent manager that delegates shell tasks to a TerminalAgent while handling other work itself.
+
+```yaml
+name: manager-demo
+description: >
+  A ToolUseAgent manager orchestrates a TerminalAgent (shell commands)
+  and a ToolUseAgent file reader. The manager delegates and synthesizes.
+
+model:
+  modelId: anthropic/claude-sonnet-4.5
+  baseUrl: https://openrouter.ai/api/v1
+
+tools:
+  read:
+    type: read_file
+
+agents:
+  terminal_worker:
+    type: TerminalAgent
+    description: Runs shell commands to gather system information.
+    maxSteps: 3
+    customInstructions: >
+      Gather the requested system information by running shell commands.
+      When you have everything, call final_answer with a clear summary.
+
+  file_worker:
+    type: ToolUseAgent
+    description: Reads files from the project and summarizes their contents.
+    tools:
+      - read
+    maxSteps: 3
+    customInstructions: >
+      Read the file(s) you are asked about and return a concise summary
+      of the relevant details.
+
+  manager:
+    type: ToolUseAgent
+    description: >
+      Delegates to terminal_worker for shell tasks and file_worker for
+      file reads, then synthesizes the results.
+    agents:
+      - terminal_worker
+      - file_worker
+    maxSteps: 5
+    customInstructions: >
+      You are a manager agent. You have no tools of your own — your job
+      is to delegate to your sub-agents and combine their results.
+      - terminal_worker: use for anything that needs shell commands or live system state
+      - file_worker: use for reading files on disk
+      Delegate both tasks in parallel if possible, then synthesize a final answer.
+
+entrypoint: manager
+```
+
+Run it:
+
+```bash
+npx @samrahimi/smol-js examples/js/agents/manager-demo.yaml \
+  --task "Tell me my macOS version and summarize the smol-js README"
+```
+
+---
+
+## Custom Tool Plugins
+
+The custom tool system lets you write standalone tool files that any agent can use — without modifying the framework or writing boilerplate. Drop a `.ts` file into a folder, point the CLI at it, and it just works.
+
+### How It Works
+
+1. You write a single `.ts` file that exports `TOOL_METADATA` and an `execute()` function
+2. You tell the CLI where to find your tools: `--custom-tools-folder ./my-tools`
+3. At startup, smol-js scans the folder, discovers your tools, and makes them available in YAML workflows
+4. When an agent calls your tool, smol-js spawns an isolated [Bun](https://bun.sh) process to run it
+
+The tool file is **transport-agnostic**. It has zero knowledge of how it's invoked. All the process management, argument passing, and result serialization is handled by a harness adapter that ships with the package.
+
+### Writing a Custom Tool
+
+A custom tool is a single `.ts` file. Here's a complete example — `WeatherLookup.ts`:
+
+```typescript
+/**
+ * WeatherLookup — fetches weather data from Open-Meteo API.
+ *
+ * This file exports two things and nothing else:
+ *   1. TOOL_METADATA  — describes the tool to the smol-js scanner
+ *   2. execute(args)  — the actual function; called by the toolHarness adapter
+ *
+ * It has zero knowledge of how it is invoked. The harness handles argument
+ * deserialization, protocol framing, and process lifecycle.
+ *
+ * Dependencies are resolved by Bun at runtime — no package.json or
+ * npm install needed.
+ */
+
+import chalk from 'chalk';  // Bun resolves this from npm automatically
+import dayjs from 'dayjs';  // Same here — zero config
+
+// TOOL_METADATA — parsed by the scanner at discovery time.
+// The `name` field MUST match this file's basename (WeatherLookup).
+export const TOOL_METADATA = {
+  name: 'WeatherLookup',
+  description: 'Fetches current weather for a given city using the Open-Meteo API.',
+  inputs: {
+    city: {
+      type: 'string',
+      description: 'The city to look up (e.g. "London", "Tokyo")',
+      required: true,
+    },
+    units: {
+      type: 'string',
+      description: 'Temperature units: "celsius" (default) or "fahrenheit"',
+      required: false,
+      default: 'celsius',
+    },
+  },
+  outputType: 'string',
+};
+
+// execute — the tool's entry point. Just a function.
+// args contains the deserialized parameters passed by the agent.
+// Return your result. Throw an Error if something goes wrong.
+// console.log() calls are streamed back as output the agent can see.
+export async function execute(args: Record<string, unknown>): Promise<string> {
+  const city = args.city as string;
+  console.log(chalk.dim(`  Geocoding "${city}"...`));
+
+  // ... fetch weather data ...
+
+  return `Weather in ${city}: 22°C, Partly cloudy`;
+}
+```
+
+### The Rules
+
+1. **File name must match `TOOL_METADATA.name`** — if the metadata says `WeatherLookup`, the file must be `WeatherLookup.ts`
+2. **Export exactly two things**: `TOOL_METADATA` and `execute()`
+3. **Dependencies are free** — Bun resolves npm packages natively. Just `import` them. No `package.json`, no `npm install`.
+4. **Don't add a `main()` function.** Don't read `process.argv`. Don't write `[TOOL_RESULT]` lines. The framework's harness handles all of that.
+5. **`execute` must be async** and return a `Promise`
+6. **`console.log()` works** — output is streamed back and visible to the agent as context
+
+### Using Custom Tools in a Workflow
+
+Reference your tool by its metadata name in the `tools` section:
+
+```yaml
+name: weather-assistant
+description: A helpful weather assistant.
+
+model:
+  modelId: anthropic/claude-haiku-4.5
+  baseUrl: https://openrouter.ai/api/v1
+
+tools:
+  WeatherLookup:
+    type: WeatherLookup      # Must match TOOL_METADATA.name
+
+agents:
+  assistant:
+    type: ToolUseAgent
+    tools:
+      - WeatherLookup
+    maxSteps: 5
+    customInstructions: >
+      You are a friendly weather assistant. Use WeatherLookup to get
+      current conditions. Present results conversationally.
+
+entrypoint: assistant
+```
+
+Run it:
+
+```bash
+npx @samrahimi/smol-js weather-assistant.yaml \
+  --task "What's the weather in Tokyo?" \
+  --custom-tools-folder ./custom-tools
+```
+
+### Tool-Maker Agent
+
+If you'd rather have an AI write your custom tools, there's a tool-maker agent in the examples:
+
+```bash
+npx @samrahimi/smol-js examples/js/agents/tool-maker/tool-maker.yaml \
+  --task "Create a tool that converts currencies using the ExchangeRate API"
+```
+
+The tool-maker reads the WeatherLookup reference, understands the contract, generates a new standalone tool file, creates a matching YAML workflow, and outputs a ready-to-run `npx` command. Drop the output into any `--custom-tools-folder` and it works.
+
+---
+
 ## Configuration
 
 ### Environment Variables
@@ -183,11 +444,25 @@ const agent = new CodeAgent({
   persistent: false,                        // Retain memory between run() calls
   maxContextLength: 100000,                 // Token limit for context
   memoryStrategy: 'truncate',               // 'truncate' or 'compact'
-  additionalAuthorizedImports: ['lodash'], // npm packages (CodeAgent only)
-  workingDirectory: '/path/to/dir',        // Working dir for fs operations
+  additionalAuthorizedImports: ['lodash'],  // npm packages (CodeAgent only)
+  workingDirectory: '/path/to/dir',         // Working dir for fs operations
+});
+```
+
+### TerminalAgent Configuration
+
+```typescript
+const agent = new TerminalAgent({
+  model,
+  maxSteps: 10,
+  commandDelay: 5,       // Seconds before executing commands (default: 5)
+  maxOutputLength: 8000, // Max chars of output fed back per command (default: 8000)
+  customInstructions: 'Focus on Python tooling only.',
 });
 ```
 
+---
+
 ## Built-in Tools
 
 - **FinalAnswerTool**: Return the final result (always available)
@@ -200,9 +475,9 @@ const agent = new CodeAgent({
 - **ExaResearchTool**: Multi-step research workflow
 - **AgentTool**: Wrap agents as tools for nested architectures
 
-## Creating Custom Tools
+## Creating Custom Tools (Class-Based)
 
-### Class-Based Tools
+For tools that need to live inside your TypeScript project (rather than as standalone plugin files), extend the `Tool` class:
 
 ```typescript
 import { Tool } from '@samrahimi/smol-js';
@@ -256,6 +531,8 @@ const orchestrator = new Orchestrator();
 await orchestrator.runWorkflow(workflow, 'Your task here');
 ```
 
+---
+
 ## YAML Workflow System
 
 Define complex agent architectures declaratively:
@@ -282,7 +559,7 @@ tools:
     type: write_file
 
 agents:
-  # Worker agent: specialized in research
+  # Worker: specialized in research
   researcher:
     type: ToolUseAgent
     tools:
@@ -290,25 +567,32 @@ agents:
       - read
     maxSteps: 8
     temperature: 0.3
-    customInstructions: "You are a research specialist. Be thorough and cite sources."
+    customInstructions: "Be thorough and cite sources."
 
-  # Worker agent: specialized in writing
+  # Worker: specialized in writing
   writer:
     type: CodeAgent
     tools:
       - write
     maxSteps: 5
     temperature: 0.7
-    customInstructions: "You are a skilled technical writer. Create clear, engaging content."
+    customInstructions: "Create clear, engaging content."
+
+  # Worker: runs shell commands
+  sysadmin:
+    type: TerminalAgent
+    maxSteps: 5
+    customInstructions: "Handle any system or environment setup tasks."
 
-  # Manager agent: delegates to workers
+  # Manager: delegates to all three workers
   manager:
     type: ToolUseAgent
     agents:
-      - researcher  # Available as a tool
-      - writer      # Available as a tool
+      - researcher
+      - writer
+      - sysadmin
     maxSteps: 10
-    customInstructions: "You coordinate research and writing tasks. Delegate appropriately."
+    customInstructions: "Coordinate research, writing, and system tasks. Delegate appropriately."
 
 entrypoint: manager
 ```
@@ -319,24 +603,26 @@ Run it:
 npx @samrahimi/smol-js research-workflow.yaml --task "Write a report on quantum computing"
 ```
 
+---
+
 ## Nested Agents (Manager-Worker Pattern)
 
 Use agents as tools for hierarchical task delegation:
 
 ```typescript
-import { CodeAgent, ToolUseAgent, OpenAIModel, AgentTool } from '@samrahimi/smol-js';
+import { CodeAgent, ToolUseAgent, TerminalAgent, OpenAIModel, AgentTool } from '@samrahimi/smol-js';
 
 // Create specialized worker agents
 const mathAgent = new CodeAgent({
   model,
   maxSteps: 5,
-  verboseLevel: LogLevel.OFF, // Quiet - manager handles output
+  verboseLevel: LogLevel.OFF,
 });
 
-const researchAgent = new ToolUseAgent({
+const sysAgent = new TerminalAgent({
   model,
-  tools: [searchTool],
-  maxSteps: 8,
+  maxSteps: 5,
+  commandDelay: 3,
   verboseLevel: LogLevel.OFF,
 });
 
@@ -344,25 +630,27 @@ const researchAgent = new ToolUseAgent({
 const mathExpert = new AgentTool({
   agent: mathAgent,
   name: 'math_expert',
-  description: 'Delegate math and calculation tasks to this agent',
+  description: 'Delegate math and calculation tasks',
 });
 
-const researcher = new AgentTool({
-  agent: researchAgent,
-  name: 'researcher',
-  description: 'Delegate research and information gathering to this agent',
+const sysAdmin = new AgentTool({
+  agent: sysAgent,
+  name: 'sys_admin',
+  description: 'Delegate shell commands and system tasks',
 });
 
-// Create manager that uses the workers
+// Manager delegates to workers
 const manager = new ToolUseAgent({
   model,
-  tools: [mathExpert, researcher],
+  tools: [mathExpert, sysAdmin],
   maxSteps: 10,
 });
 
-await manager.run('Research Tokyo population and calculate water consumption per capita');
+await manager.run('Check disk usage and calculate how many GB are free as a percentage');
 ```
 
+---
+
 ## Exa.ai Integration
 
 Three tools for web research powered by Exa.ai:
@@ -413,10 +701,11 @@ const researchTool = new ExaResearchTool({
 // 4. Synthesizes findings into a markdown report with citations
 // 5. Returns the complete report (typically 20-90 seconds)
 
-// Usage in agent:
-await agent.run('Use exa_research to write a comprehensive report on quantum computing breakthroughs in 2024');
+await agent.run('Use exa_research to write a report on quantum computing breakthroughs in 2024');
 ```
 
+---
+
 ## Built-in Capabilities (CodeAgent)
 
 The CodeAgent sandbox includes:
@@ -448,6 +737,8 @@ const agent = new CodeAgent({
 
 Packages are fetched from [jsdelivr CDN](https://www.jsdelivr.com/) and cached in `~/.smol-js/packages/`.
 
+---
+
 ## Examples
 
 See the `examples/js/` directory for complete examples:
@@ -455,11 +746,17 @@ See the `examples/js/` directory for complete examples:
 - **main.ts**: Main demo with custom tools and YAML workflows
 - **custom-tools.ts**: Custom tool implementations (TimestampTool, TextStatsTool, SlugifyTool)
 - **agents/**: YAML workflow definitions
-  - `custom_tools.yaml`: Workflow using custom tools
+  - `custom-tool-workflow.yaml`: Weather assistant using the standalone custom tool plugin system
+  - `manager-demo.yaml`: Manager + TerminalAgent worker + file-reader worker
+  - `tool-maker/tool-maker.yaml`: AI agent that generates custom tool files
   - `bloomberg.yaml`: Bloomberg research workflow
   - `policy.yaml`: Policy analysis workflow
   - `simple-test.yaml`: Simple test workflow
 
+And the `custom-tools/` directory at the repo root contains example standalone tool plugins:
+
+- `WeatherLookup.ts`: Fetches weather from Open-Meteo (demonstrates npm deps, streaming output, error handling)
+
 Run an example:
 
 ```bash
@@ -468,6 +765,8 @@ npm install
 npx tsx main.ts
 ```
 
+---
+
 ## Memory Management
 
 Agents track all execution steps and manage context automatically:
@@ -494,11 +793,15 @@ await persistentAgent.run('What is X?'); // Remembers X = 42
 - **truncate**: Removes oldest steps when over token limit
 - **compact**: Uses LLM to summarize older steps
 
+---
+
 ## Session Logging
 
 All sessions are logged to `~/.smol-js/`:
-- `session-<timestamp>.log` - Full session transcript with color codes
-- `packages/` - Cached npm packages from dynamic imports
+- `session-<timestamp>.log` — Full session transcript with color codes
+- `packages/` — Cached npm packages from dynamic imports
+
+---
 
 ## API Reference
 
@@ -533,7 +836,20 @@ class ToolUseAgent extends Agent {
 }
 
 interface ToolUseAgentConfig extends AgentConfig {
-  enableParallelToolCalls?: boolean; // Execute independent tools in parallel
+  enableParallelToolCalls?: boolean;
+}
+```
+
+### TerminalAgent
+
+```typescript
+class TerminalAgent extends Agent {
+  constructor(config: TerminalAgentConfig)
+}
+
+interface TerminalAgentConfig extends AgentConfig {
+  commandDelay?: number;       // Seconds before executing (default: 5)
+  maxOutputLength?: number;    // Max chars of output per command (default: 8000)
 }
 ```
 
@@ -585,11 +901,14 @@ class Orchestrator {
 ```typescript
 class YAMLLoader {
   registerToolType(typeName: string, toolClass: typeof Tool): void
+  registerToolInstance(name: string, tool: Tool): void
   loadFromFile(filePath: string): Workflow
   loadFromString(yaml: string): Workflow
 }
 ```
 
+---
+
 ## CLI Reference
 
 ```bash
@@ -601,18 +920,24 @@ npx @samrahimi/smol-js run <workflow.yaml> [options]
 npx @samrahimi/smol-js validate <workflow.yaml>
 
 # Options
---task, -t <task>    Task description (prompted if not provided)
---quiet, -q          Reduce output verbosity
---help, -h           Show help message
+--task, -t <task>                  Task description (prompted if not provided)
+--custom-tools-folder <path>       Path to folder containing standalone tool plugins
+--quiet, -q                        Reduce output verbosity
+--help, -h                         Show help message
 ```
 
+---
+
 ## Security Considerations
 
 - **Sandboxed Execution**: Code runs in Node's vm module, isolated from the main process
-- **Authorized Imports**: Only explicitly allowed npm packages can be imported
+- **Authorized Imports**: Only explicitly allowed npm packages can be imported in CodeAgent
 - **File System Isolation**: fs operations are restricted to configured working directory
-- **Execution Delay**: Configurable delay before code execution allows user interruption (Ctrl+C)
-- **Timeout Protection**: Code execution has a configurable timeout (default: 30s)
+- **Execution Delay**: Configurable delay before code/command execution allows user interruption (Ctrl+C)
+- **Timeout Protection**: Code execution has a configurable timeout (default: 30s); shell commands timeout at 2 minutes
+- **Isolated Tool Processes**: Custom tool plugins run in separate Bun processes — a misbehaving tool can't affect the main framework
+
+---
 
 ## Comparison with Python smolagents
 
@@ -625,9 +950,12 @@ npx @samrahimi/smol-js validate <workflow.yaml>
 | Async support | Optional | All tools are async |
 | HTTP requests | Requires tool | Built-in `fetch()` |
 | Remote executors | E2B, Docker, etc. | Local only |
-| Agent types | CodeAgent, ToolCallingAgent | CodeAgent, ToolUseAgent |
+| Agent types | CodeAgent, ToolCallingAgent | CodeAgent, ToolUseAgent, TerminalAgent |
 | YAML workflows | ❌ | ✅ |
 | Exa.ai integration | ❌ | ✅ Built-in |
+| Custom tool plugins | ❌ | ✅ Standalone `.ts` files |
+
+---
 
 ## Contributing
 
@@ -635,8 +963,8 @@ Contributions are welcome! Please follow OOP principles and open an issue or PR
 
 ```bash
 # Clone and install
-git clone https://github.com/samrahimi/smolagents
-cd smolagents/smol-js
+git clone https://github.com/samrahimi/smol.git
+cd smol/smol-js
 npm install
 
 # Build
@@ -659,4 +987,4 @@ MIT
 
 ## Credits
 
-This is a TypeScript framework inspired by [smolagents](https://github.com/huggingface/smolagents) by Hugging Face, with additional features including YAML orchestration, ToolUseAgent, and Exa.ai integration.
+This is a TypeScript framework inspired by [smolagents](https://github.com/huggingface/smolagents) by Hugging Face, with additional features including YAML orchestration, ToolUseAgent, TerminalAgent, custom tool plugins, and Exa.ai integration.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@samrahimi/smol-js",
-  "version": "0.7.2",
+  "version": "0.7.3",
   "description": "A TypeScript agentic framework - CodeAgent and ToolUseAgent with YAML orchestration, built-in tools, and Exa.ai integration",
   "main": "dist/index.js",
   "module": "dist/index.mjs",
@@ -72,5 +72,10 @@
   },
   "engines": {
     "node": ">=18.0.0"
+  },
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/samrahimi/smol.git",
+    "directory": "smol-js"
   }
 }