Definitions
Typed, file-routed agent blueprints with colocated tools, apps, memory, MCP, layers, and workbenches.
Define the possible. Persist the chosen. Assemble each agent from the context in front of it—and inspect the whole system while it works.
Traditional workflow software asks you to predict the branches. Foundry lets you define capable agents, available worlds, and operational boundaries. The system can then understand intent, create the plan, make the artifacts, ask for help, and adapt the route while it is running. Deterministic control is still there when you need it. It is no longer the only way to build.
Typed, file-routed agent blueprints with colocated tools, apps, memory, MCP, layers, and workbenches.
Persisted runtime data that selects installations, playbooks, schedules, conversations, and instance context.
Every major surface can resolve lazily from the current instance, conversation, message, and history.
Runs, retries, passes, tool calls, transmissions, artifacts, and messages share one observable timeline.
A folder is a boundary, not a dumping ground. Colocate the parts that change together. Import real definitions when code can reference code; use serializable IDs only at data and persistence boundaries.
Explore composition →import { defineAgent } from "glove-foundry";
import { components } from "./composition.js";
import { brandWorkspace } from "./workbench.js";
export default defineAgent({
description: "Leads a brand workforce",
components,
workingEnvironment: (_agent, ctx) =>
ctx.messageText.includes("campaign")
? brandWorkspace
: undefined,
tools: (_agent, ctx) =>
ctx.installations.flatMap((app) => app.tools),
systemPrompt: (_agent, ctx) =>
promptFor(ctx.agentInstance, ctx.message, ctx.history),
});