
Security News
TC39 Advances Temporal to Stage 4 Alongside Several ECMAScript Proposals
TC39’s March 2026 meeting advanced eight ECMAScript proposals, including Temporal reaching Stage 4 and securing its place in the ECMAScript 2026 specification.
@getfoundry/foundry-openclaw
Advanced tools
The forge that forges itself — self-writing meta-extension for OpenClaw
The forge that forges itself.
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.
$FDRY — dexscreener · 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 (originally Clawdbot) is the platform — an open-source agent runtime with:
Foundry is a plugin that runs on OpenClaw:
foundry_extend_selfOpenClaw (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.
The key insight isn't "LLM writes code for you" — it's "the system upgrades itself."
| Knowledge (Patterns) | Behavior (Self-Written Code) |
|---|---|
| Stored as text | Baked into the system |
| LLM must read and apply each time | Runs automatically |
| Uses tokens every invocation | Zero token cost |
| Can be forgotten or ignored | Always executes |
A pattern says: "When X happens, do Y." Self-written code does Y automatically when X happens.
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.
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.
| Traditional Agents | Foundry |
|---|---|
| Same logic every time | Learns your patterns |
| You adapt to the agent | Agent adapts to you |
| Each capability is isolated | Each upgrade improves the upgrader |
| Linear improvement | Compound improvement |
Example:
deploy_staging toolTraditional 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.
openclaw plugins install @getfoundry/foundry-openclaw
That's it. This will download, extract, enable, and load Foundry automatically.
Add to ~/.openclaw/openclaw.json:
{
"plugins": {
"entries": {
"foundry": { "enabled": true }
}
}
}
Then restart:
openclaw gateway restart
Add to ~/.openclaw/openclaw.json:
{
"plugins": {
"entries": {
"foundry": {
"enabled": true,
"source": "github:lekt9/openclaw-foundry"
}
}
}
}
nix run github:lekt9/openclaw-foundry
git clone https://github.com/lekt9/openclaw-foundry ~/.openclaw/extensions/foundry
cd ~/.openclaw/extensions/foundry && npm install
Then restart:
openclaw gateway restart
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
}
}
}
}
}
}
| Option | Default | Description |
|---|---|---|
autoLearn | true | Learn from agent activity automatically |
sources.docs | true | Learn from OpenClaw documentation |
sources.experience | true | Learn from own successes/failures |
marketplace.autoPublish | false | Auto-publish high-value patterns |
| Tool | Description |
|---|---|
foundry_research | Search docs.openclaw.ai for best practices and patterns |
foundry_docs | Read specific documentation pages (plugin, hooks, tools, etc.) |
foundry_learnings | View recorded patterns, workflows, insights |
| Tool | Description |
|---|---|
foundry_implement | Research + implement a capability end-to-end |
foundry_write_extension | Write a new OpenClaw extension with tools/hooks |
foundry_write_skill | Write an API skill package (SKILL.md + api.ts) |
foundry_write_browser_skill | Write a browser automation skill with CDP integration |
foundry_write_hook | Write a standalone hook (HOOK.md + handler.ts) |
foundry_add_tool | Add a tool to an existing extension |
foundry_add_hook | Add a hook to an existing extension |
foundry_extend_self | Add capabilities to Foundry itself |
| Tool | Description |
|---|---|
foundry_list | List all written extensions and skills |
foundry_restart | Restart gateway with context preservation |
foundry_publish_ability | Publish patterns/extensions to Foundry Marketplace |
foundry_marketplace | Search, browse leaderboard, and install abilities |
Foundry ships with built-in skills that are automatically available:
foundry-browser-helperHelper 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"
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
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
Foundry:
1. Records workflow patterns
2. Tracks success rates per pattern
3. Identifies crystallization candidates
4. Builds knowledge base of what works
Foundry:
1. Generates extension code following patterns
2. Includes proper TypeScript types
3. Adds error handling and logging
4. Validates in isolated sandbox
Foundry:
1. Writes to ~/.openclaw/extensions/
2. Creates openclaw.plugin.json
3. Triggers gateway restart
4. Resumes conversation automatically
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 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
Hooks follow the HOOK.md + handler.ts pattern:
my-hook/
├── HOOK.md # Frontmatter + documentation
└── handler.ts # Event handler code
Generated code is validated before deployment:
child_process / exec / spawn — Shell executioneval() / new Function() — Dynamic code execution~/.ssh/ / id_rsa — SSH key access~/.aws/ / aws_secret — Cloud credentialsprocess.env — Environment variable accessfs.readFile / fs.writeFile — Filesystem access1. 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
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"
HTTP 402 "Payment Required" + Solana USDC:
No intermediaries. Direct creator payment. Network effects compound.
| Type | Price | Description |
|---|---|---|
| Pattern | FREE | Workflow patterns (crowdsourced) |
| Technique | $0.02 | Reusable code snippets |
| Extension | $0.05 | Full OpenClaw plugins |
| Agent | $0.10 | High-fitness agent designs |
{
"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
}
}
}
}
}
}
| Option | Description | Default |
|---|---|---|
dataDir | Directory to store forged artifacts | ~/.openclaw/foundry |
openclawPath | Path to OpenClaw installation for local docs | - |
autoLearn | Automatically learn from agent activity | true |
sources.docs | Learn from OpenClaw documentation | true |
sources.experience | Learn from own successes/failures | true |
sources.arxiv | Learn from arXiv papers | true |
sources.github | Learn from GitHub repos | true |
marketplace.url | Foundry marketplace URL | https://api.claw.getfoundry.app |
marketplace.autoPublish | Auto-publish high-value patterns | false |
Foundry's self-improvement mechanisms draw from recent advances in autonomous learning agents:
| Paper | Key Insight | Foundry 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 capabilities | Self-written tools/hooks that expand Foundry's capabilities |
| SelfEvolve (Jiang et al., 2023) | Two-step pipeline: knowledge generation + self-reflection debugging using interpreter feedback | LearningEngine records outcomes → patterns → crystallization |
| Paper | Key Insight | Foundry Application |
|---|---|---|
| RISE: Recursive Introspection (Qu et al., 2024) | Iterative fine-tuning teaches models to "alter responses after unsuccessful attempts" via multi-turn MDPs | Workflow tracking learns from outcomes, suggests improvements |
| HexMachina (Liu et al., 2025) | "Artifact-centric continual learning" — separates discovery from strategy evolution through code refinement | Patterns (knowledge) crystallize into hooks/tools (behavior) |
| Paper | Key Insight | Foundry Application |
|---|---|---|
| ADAS: Automated Design of Agentic Systems (Hu et al., 2024) | Meta-agent iteratively discovers improved agent designs through archive-based evolution | Overseer tracks tool fitness, evolves patterns |
"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.
~/.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
# Type check
npx tsc --noEmit
# Test extension locally
openclaw gateway restart
tail -f ~/.openclaw/logs/gateway.log | grep foundry
MIT
Built with OpenClaw. Forged by Foundry.
FAQs
The forge that forges itself — self-writing meta-extension for OpenClaw
The npm package @getfoundry/foundry-openclaw receives a total of 133 weekly downloads. As such, @getfoundry/foundry-openclaw popularity was classified as not popular.
We found that @getfoundry/foundry-openclaw demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

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.

Security News
TC39’s March 2026 meeting advanced eight ECMAScript proposals, including Temporal reaching Stage 4 and securing its place in the ECMAScript 2026 specification.

Research
/Security News
Since January 31, 2026, we identified at least 72 additional malicious Open VSX extensions, including transitive GlassWorm loader extensions targeting developers.

Research
Six malicious Packagist packages posing as OphimCMS themes contain trojanized jQuery that exfiltrates URLs, injects ads, and loads FUNNULL-linked redirects.