You're Invited:Meet the Socket Team at RSAC and BSidesSF 2026, March 23–26.RSVP
Socket
Book a DemoSign in
Socket

@getfoundry/foundry-openclaw

Package Overview
Dependencies
Maintainers
1
Versions
4
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@getfoundry/foundry-openclaw

The forge that forges itself — self-writing meta-extension for OpenClaw

latest
Source
npmnpm
Version
0.2.3
Version published
Weekly downloads
133
-35.44%
Maintainers
1
Weekly downloads
 
Created
Source

Foundry

Foundry

The forge that forges itself.

FDRY

Foundry is a self-writing meta-extension for OpenClaw that learns how you work, researches documentation, and writes new capabilities into itself. It observes your workflows, crystallizes patterns into tools, and upgrades itself to match how you operate.

$FDRYdexscreener · Solana

┌─────────────────────────────────────────────────────────────┐
│                         FOUNDRY                             │
│                                                             │
│   Observe ──► Research ──► Learn ──► Write ──► Deploy      │
│       │          │          │          │          │         │
│       ▼          ▼          ▼          ▼          ▼         │
│   workflows   docs.openclaw  patterns  extensions  gateway  │
│   tool calls  arXiv papers   insights  tools       restart  │
│   outcomes    GitHub repos   workflows hooks       resume   │
│                                        skills              │
└─────────────────────────────────────────────────────────────┘

OpenClaw vs Foundry

OpenClaw (originally Clawdbot) is the platform — an open-source agent runtime with:

  • Gateway, channels, memory, sessions
  • Tool execution and skill loading
  • Model providers and routing
  • The infrastructure everything runs on

Foundry is a plugin that runs on OpenClaw:

  • Observes how you work → learns your patterns
  • Researches docs → writes new extensions/skills/hooks
  • Has its own learning engine (not part of OpenClaw core)
  • Can modify itself via foundry_extend_self
  • Publishes to Foundry Marketplace via x402
OpenClaw (platform)
├── Gateway
├── Channels (Discord, Slack, Telegram...)
├── Skills & Tools
└── Plugins
    └── Foundry (this repo)
        ├── observes → your workflows
        ├── researches → docs, papers, repos
        ├── writes → extensions, skills, hooks
        ├── learns → from outcomes
        ├── crystallizes → patterns into tools
        └── publishes → to marketplace

Key distinction: OpenClaw doesn't have built-in self-learning. Foundry adds that capability on top. Foundry is an "agent that builds agents" — it uses OpenClaw's infrastructure to create new OpenClaw capabilities, and upgrades itself to match how you work.

Why Self-Writing Matters

The key insight isn't "LLM writes code for you" — it's "the system upgrades itself."

Knowledge vs Behavior

Knowledge (Patterns)Behavior (Self-Written Code)
Stored as textBaked into the system
LLM must read and apply each timeRuns automatically
Uses tokens every invocationZero token cost
Can be forgotten or ignoredAlways executes

A pattern says: "When X happens, do Y." Self-written code does Y automatically when X happens.

Workflow Learning

Foundry tracks every workflow you run:

Goal: "deploy to staging"
Tools: git → build → test → deploy
Outcome: success
Duration: 45s

Over time, patterns emerge. When a pattern hits 5+ uses with 70%+ success rate, Foundry crystallizes it into a dedicated tool.

What took 8 tool calls now takes 1.

The Recursive Loop

Foundry observes how you work
    ↓
Learns patterns, researches docs
    ↓
Writes tool/hook to match your workflow
    ↓
That code becomes part of Foundry
    ↓
Foundry is now better at working like you
    ↓
Better Foundry learns more, writes more
    ↓
Repeat

The system that writes the code IS the code being written.

Why This Compounds

Traditional AgentsFoundry
Same logic every timeLearns your patterns
You adapt to the agentAgent adapts to you
Each capability is isolatedEach upgrade improves the upgrader
Linear improvementCompound improvement

Example:

  • You deploy to staging 5 times using git→build→test→deploy
  • Foundry recognizes the pattern (87% success rate)
  • Crystallizes into deploy_staging tool
  • Now "deploy to staging" is a single command
  • You save time → do more deploys → pattern strengthens
  • Foundry learns variations (deploy to prod, deploy with migrations)
  • Loop

The Bet

Traditional software: Human improves software → software does more

Foundry: Software upgrades software → software upgrades faster

This is recursive self-improvement — each capability makes acquiring the next capability easier.

Features

Self-Writing Code Generation

  • Writes OpenClaw extensions with tools and hooks
  • Generates API skills following AgentSkills format with YAML frontmatter
  • Generates browser automation skills with CDP integration
  • Generates standalone hooks with HOOK.md + handler.ts pattern
  • Can extend itself with new capabilities
  • Validates code in isolated sandbox before deployment

Workflow Learning & Crystallization

  • Tracks goal → tool sequence → outcome for every workflow
  • Extracts keywords from goals for pattern matching
  • Calculates success rates and average durations
  • Crystallizes high-value patterns (5+ uses, 70%+ success) into dedicated tools
  • Suggests relevant patterns when you start similar tasks

The Overseer

  • Runs autonomously on hourly interval
  • Identifies crystallization candidates
  • Auto-generates tools from high-value patterns
  • Prunes stale patterns (30+ days unused)
  • Tracks tool performance metrics (ADAS-style evolution)
  • Reports actions taken

Native OpenClaw Integration

  • AgentSkills Format: Proper YAML frontmatter with metadata (emoji, requires, events)
  • Browser Automation: CDP-based browser tool integration for authenticated workflows
  • Skill Gating: Auto-generates requires.config, requires.bins, requires.env for dependencies
  • Hook System: Full support for OpenClaw hook events (gateway:startup, command:new, etc.)
  • ClawdHub Ready: Skills can be published to the ClawdHub registry

Proactive Learning

  • Records tool outcomes (success/failure) with context
  • Builds patterns from repeated workflows
  • Shares learnings via the Foundry Marketplace
  • Injects relevant context into agent conversations

Sandbox Validation

  • Runs generated code in isolated Node process
  • Catches runtime errors before they crash the gateway
  • Static security scanning (blocks shell exec, eval, credential access)
  • Only deploys code that passes all checks

Restart Resume

  • Saves conversation context before gateway restart
  • Automatically resumes after restart via managed hook
  • No lost work when self-modifying

Installation

openclaw plugins install @getfoundry/foundry-openclaw

That's it. This will download, extract, enable, and load Foundry automatically.

Alternative: Manual Config

Add to ~/.openclaw/openclaw.json:

{
  "plugins": {
    "entries": {
      "foundry": { "enabled": true }
    }
  }
}

Then restart:

openclaw gateway restart

Option C: GitHub Source

Add to ~/.openclaw/openclaw.json:

{
  "plugins": {
    "entries": {
      "foundry": {
        "enabled": true,
        "source": "github:lekt9/openclaw-foundry"
      }
    }
  }
}

Option D: Nix (Reproducible)

nix run github:lekt9/openclaw-foundry

Option E: Manual Clone

git clone https://github.com/lekt9/openclaw-foundry ~/.openclaw/extensions/foundry
cd ~/.openclaw/extensions/foundry && npm install

Then restart:

openclaw gateway restart

Configuration

Full config options:

{
  "plugins": {
    "entries": {
      "foundry": {
        "enabled": true,
        "source": "github:lekt9/openclaw-foundry",
        "config": {
          "autoLearn": true,
          "sources": {
            "docs": true,
            "experience": true,
            "arxiv": true,
            "github": true
          },
          "marketplace": {
            "autoPublish": false
          }
        }
      }
    }
  }
}
OptionDefaultDescription
autoLearntrueLearn from agent activity automatically
sources.docstrueLearn from OpenClaw documentation
sources.experiencetrueLearn from own successes/failures
marketplace.autoPublishfalseAuto-publish high-value patterns

Tools

Research & Learning

ToolDescription
foundry_researchSearch docs.openclaw.ai for best practices and patterns
foundry_docsRead specific documentation pages (plugin, hooks, tools, etc.)
foundry_learningsView recorded patterns, workflows, insights

Code Generation

ToolDescription
foundry_implementResearch + implement a capability end-to-end
foundry_write_extensionWrite a new OpenClaw extension with tools/hooks
foundry_write_skillWrite an API skill package (SKILL.md + api.ts)
foundry_write_browser_skillWrite a browser automation skill with CDP integration
foundry_write_hookWrite a standalone hook (HOOK.md + handler.ts)
foundry_add_toolAdd a tool to an existing extension
foundry_add_hookAdd a hook to an existing extension
foundry_extend_selfAdd capabilities to Foundry itself

Management

ToolDescription
foundry_listList all written extensions and skills
foundry_restartRestart gateway with context preservation
foundry_publish_abilityPublish patterns/extensions to Foundry Marketplace
foundry_marketplaceSearch, browse leaderboard, and install abilities

Bundled Skills

Foundry ships with built-in skills that are automatically available:

foundry-browser-helper

Helper skill for browser automation patterns. Provides guidance on using the OpenClaw browser tool effectively.

# Quick reference
browser open https://example.com
browser snapshot           # AI-readable format
browser click ref=btn_submit
browser type ref=input_email "user@example.com"

How It Works

1. Observe Phase

Foundry watches every workflow:
  - Goal: What the user is trying to do
  - Tools: Sequence of tool calls
  - Outcome: Success, failure, or partial
  - Duration: How long it took

2. Research Phase

User: "Add a tool that fetches weather data"

Foundry:
  1. Searches docs.openclaw.ai for tool registration patterns
  2. Finds examples of API-calling tools
  3. Identifies best practices for error handling

3. Learn Phase

Foundry:
  1. Records workflow patterns
  2. Tracks success rates per pattern
  3. Identifies crystallization candidates
  4. Builds knowledge base of what works

4. Write Phase

Foundry:
  1. Generates extension code following patterns
  2. Includes proper TypeScript types
  3. Adds error handling and logging
  4. Validates in isolated sandbox

5. Deploy Phase

Foundry:
  1. Writes to ~/.openclaw/extensions/
  2. Creates openclaw.plugin.json
  3. Triggers gateway restart
  4. Resumes conversation automatically

Skill Generation

Foundry generates skills in the AgentSkills format with proper YAML frontmatter:

---
name: my-api-skill
description: Integrates with My API service
metadata: {"openclaw":{"emoji":"🔌","requires":{"env":["MY_API_KEY"]}}}
---

# My API Skill

## Authentication
This skill requires the `MY_API_KEY` environment variable.

## Endpoints
- `GET /users` - List all users
- `POST /users` - Create a new user

Browser Skills

Browser automation skills automatically gate on browser.enabled:

---
name: my-browser-skill
description: Automates login workflow
metadata: {"openclaw":{"emoji":"🌐","requires":{"config":["browser.enabled"]}}}
---

# My Browser Skill

## Workflow
1. Open login page
2. Fill credentials
3. Submit form
4. Verify success

Standalone Hooks

Hooks follow the HOOK.md + handler.ts pattern:

my-hook/
├── HOOK.md          # Frontmatter + documentation
└── handler.ts       # Event handler code

Sandbox Security

Generated code is validated before deployment:

Blocked Patterns (Instant Reject)

  • child_process / exec / spawn — Shell execution
  • eval() / new Function() — Dynamic code execution
  • ~/.ssh/ / id_rsa — SSH key access
  • ~/.aws/ / aws_secret — Cloud credentials
  • Exfiltration domains (ngrok, webhook.site, etc.)

Flagged Patterns (Warning)

  • process.env — Environment variable access
  • fs.readFile / fs.writeFile — Filesystem access
  • Base64 encoding — Potential obfuscation

Runtime Validation

1. Write extension to temp directory
2. Spawn isolated Node process with tsx
3. Mock OpenClaw API
4. Try to import and run register()
5. If fails → reject with error message
6. If passes → deploy to real extensions directory

Foundry Marketplace

Publish and download abilities with x402 Solana USDC payments:

# Publish a workflow pattern you discovered
foundry_publish_ability type="pattern" name="Deploy Staging" patternId="wp_123"

# Search for existing patterns
foundry_marketplace action="search" query="deploy" type="pattern"

# See the leaderboard
foundry_marketplace action="leaderboard"

# Download and apply
foundry_marketplace action="install" id="abc123"

x402 Protocol

HTTP 402 "Payment Required" + Solana USDC:

  • Request a skill download
  • Server returns 402 with payment requirements
  • Sign USDC transaction with your wallet
  • Retry with signed transaction in header
  • Receive the skill

No intermediaries. Direct creator payment. Network effects compound.

Ability Types & Pricing

TypePriceDescription
PatternFREEWorkflow patterns (crowdsourced)
Technique$0.02Reusable code snippets
Extension$0.05Full OpenClaw plugins
Agent$0.10High-fitness agent designs

Configuration

{
  "plugins": {
    "entries": {
      "foundry": {
        "enabled": true,
        "config": {
          "dataDir": "~/.openclaw/foundry",
          "openclawPath": "/path/to/openclaw",
          "autoLearn": true,
          "sources": {
            "docs": true,
            "experience": true,
            "arxiv": false,
            "github": false
          },
          "marketplace": {
            "url": "https://api.claw.getfoundry.app",
            "autoPublish": false
          }
        }
      }
    }
  }
}

Config Options

OptionDescriptionDefault
dataDirDirectory to store forged artifacts~/.openclaw/foundry
openclawPathPath to OpenClaw installation for local docs-
autoLearnAutomatically learn from agent activitytrue
sources.docsLearn from OpenClaw documentationtrue
sources.experienceLearn from own successes/failurestrue
sources.arxivLearn from arXiv paperstrue
sources.githubLearn from GitHub repostrue
marketplace.urlFoundry marketplace URLhttps://api.claw.getfoundry.app
marketplace.autoPublishAuto-publish high-value patternsfalse

Research Foundations

Foundry's self-improvement mechanisms draw from recent advances in autonomous learning agents:

Self-Improving Code Agents

PaperKey InsightFoundry Application
Self-Improving Coding Agent (Robeyns et al., 2025)Agent systems with coding tools can autonomously edit themselves, achieving 17-53% improvement through "non-gradient learning via LLM reflection and code updates"foundry_extend_self — the agent modifies its own codebase
From Language Models to Practical Self-Improving Computer Agents (Shinn et al., 2024)LLM agents can "systematically generate software to augment themselves" starting from minimal capabilitiesSelf-written tools/hooks that expand Foundry's capabilities
SelfEvolve (Jiang et al., 2023)Two-step pipeline: knowledge generation + self-reflection debugging using interpreter feedbackLearningEngine records outcomes → patterns → crystallization

Recursive Introspection

PaperKey InsightFoundry Application
RISE: Recursive Introspection (Qu et al., 2024)Iterative fine-tuning teaches models to "alter responses after unsuccessful attempts" via multi-turn MDPsWorkflow tracking learns from outcomes, suggests improvements
HexMachina (Liu et al., 2025)"Artifact-centric continual learning" — separates discovery from strategy evolution through code refinementPatterns (knowledge) crystallize into hooks/tools (behavior)
PaperKey InsightFoundry Application
ADAS: Automated Design of Agentic Systems (Hu et al., 2024)Meta-agent iteratively discovers improved agent designs through archive-based evolutionOverseer tracks tool fitness, evolves patterns

Core Principle

"An agent system, equipped with basic coding tools, can autonomously edit itself, and thereby improve its performance" — Robeyns et al.

Foundry operationalizes this: the system that writes the code IS the code being written.

Key Directories

~/.openclaw/foundry/            — Data directory
  ├── workflows.json            — Recorded workflows
  ├── workflow-patterns.json    — Crystallization candidates
  ├── learnings.json            — Patterns, insights, outcomes
~/.openclaw/extensions/         — Generated extensions go here
~/.openclaw/skills/             — Generated skills go here
~/.openclaw/hooks/foundry-resume/ — Restart resume hook

Development

# Type check
npx tsc --noEmit

# Test extension locally
openclaw gateway restart
tail -f ~/.openclaw/logs/gateway.log | grep foundry

License

MIT

Built with OpenClaw. Forged by Foundry.

Keywords

openclaw

FAQs

Package last updated on 31 Jan 2026

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts