sim
Sim is the collaborative workspace to build, deploy, and monitor AI agents and workflows. Used by 100,000+ builders.
- 29.9k estrellas
- 3.9k forks
- 347 issues abiertos
- Lenguaje: TypeScript
- Licencia: Apache-2.0
- actualizado
Instalación
git clone https://github.com/simstudioai/sim && cp sim/*.md ~/.claude/agents/- Clone the repository and copy the agent .md definitions into ~/.claude/agents (or .claude/agents inside a project).
- Start a new Claude Code session to load the agents.
- Delegate work to them with the Task/Agent tool or by name.
Nota editorial
Sim is an open-source, self-hostable AI agent workspace built with Next.js and TypeScript that lets teams design, run, and manage multi-step agent workflows through three distinct interfaces: a natural-language chat called Mothership, a visual block-based canvas called Workflows, and a code editor. It connects to over 1,000 integrations and supports every major LLM provider, including Claude via the Anthropic API, alongside OpenAI, Gemini, and DeepSeek. Agents can be grounded in uploaded documents through a built-in knowledge base, and structured data can be stored and queried using a native Tables feature with typed columns. A Copilot assistant can generate workflow blocks, wire variables, and debug errors from plain-language instructions. The platform is available as a cloud service at sim.ai or self-hosted via Docker Compose, with the latter requiring at least 12 GB of RAM. Teams automating multi-agent pipelines who need a single workspace to combine RAG, structured data, and LLM routing will find the most use here.
24 items en este repositorio
Create or update a Sim integration block with correct subBlocks, conditions, dependsOn, modes, canonicalParamId usage, outputs, and tool wiring. Use when working on `apps/sim/blocks/blocks/{service}.ts` or aligning a block with its tools.
Gate a block's visibility — ship an unreleased block as a preview (hidden until revealed via AppConfig/env), reveal it to admins/orgs, GA it, or kill-switch a shipped block
Add a new table column type to Sim — registry entry, icon, storage shape, coercion, and the behavioral hooks the grid and API read. Use when adding a value kind under `apps/sim/lib/table/column-types/`.
Add or update a Sim knowledge base connector for syncing documents from an external source, including auth mode, config fields, pagination, document mapping, tags, and registry wiring. Use when working in `apps/sim/connectors/{service}/` or adding a new external document source.
Add a code-defined table enrichment (registry entry) under `apps/sim/enrichments/` backed by an ordered provider cascade, ensuring every provider tool it calls has hosted-key support. Use when adding a per-row table enrichment that fills cells via existing Sim tools.
Add a runtime feature flag (AppConfig-backed on prod, secret fallback off-prod), global by default or optionally gated by workspace id, org id, user id, or platform admin
Add hosted API key support to a tool so Sim provides the key (metered and billed to the workspace) when a user has not brought their own. Use when adding a `hosting` config to a tool under `apps/sim/tools/{service}/`.
Add a complete Sim integration from API docs, covering tools, block, icon, optional triggers, registrations, resolved-secret/model-input safety, and integration conventions. Use when introducing a new service under `apps/sim/tools`, `apps/sim/blocks`, and `apps/sim/triggers`.
Add or upgrade a curated, immutable managed CLI for Sim Function sandboxes, including client-safe catalog metadata, a pinned server-only installation recipe, checksum and executable verification, provider compatibility, PATH propagation, content-addressed image identity, and tests. Use when adding a CLI to the Sandbox managed-CLI selector or changing an existing managed CLI version or recipe.
Add a new LLM model to apps/sim/providers/models.ts with specs verified against the provider's live API docs (no hallucination)
Add a new Sim settings page, or audit existing settings pages for design-system compliance with the shared SettingsPanel layout. Use when creating a settings tab, or when asked to check/clean up settings pages so they match the design system (consistent title, header, search, spacing).
Drive a PR to a clean review (Greptile 5/5, zero open threads) — ships if needed, keeps it mergeable against staging, triggers Greptile, fixes real findings, replies to and resolves every thread, and loops until clean
Run all code quality skills — effects, memo, callbacks, state, React Query, emcn design review, url-state, and comments — analyzing in parallel, then applying fixes sequentially
Spawn parallel task agents to explore a given area of the codebase from multiple angles, then use their findings to answer the question or build a plan. Use when a task needs broad fan-out exploration across many files before acting.
Author or review a Drizzle DB migration for zero-downtime safety — expand/contract phasing, backward-compatibility with the deployed app version, and writing the `-- migration-safe` acknowledgment the check:migrations lint requires. Use when adding/editing files under `packages/db/migrations/` or changing `packages/db/schema.ts`.
Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.
Review UI code for alignment with the emcn design system — components, tokens, patterns, and conventions
This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.
Design engineering principles for making interfaces feel polished. Use when building UI components, reviewing frontend code, implementing animations, hover states, shadows, borders, typography, micro-interactions, enter/exit animations, or any visual detail work. Triggers on UI polish, design details, "make it feel better", "feels off", stagger animations, border radius, optical alignment, font smoothing, tabular numbers, image outlines, box shadows.
Review PRs and diffs for unbounded memory loading, concurrency explosions, oversized payload materialization, and missing pagination or byte caps. Use when reviewing cleanup jobs, background jobs, data imports/exports, file parsing, API fan-out, workflow execution payloads, large arrays/files, or any change that reads many rows, files, responses, logs, or external API pages into process memory.
Create or migrate a protected Sim resource operation in the shared Principal and application-use-case architecture across internal APIs, public or versioned APIs, Copilot, and other trusted tool adapters. Use when adding a protected endpoint, tool command, or CRUD method; removing route- or tool-local authorization and business logic; consolidating resource reads or writes behind semantic operation policies; or adding another surface to an existing application operation while preserving contracts, identity, errors, rate limits, audit, analytics, and compatibility behavior. Treat v1, uploads, streams, large bodies, bulk recursion, and polymorphic tools as explicitly scoped special cases.
Audit React Query usage for best practices — key factories, staleTime, mutations, and server state ownership
Resumen de Subagents
A workspace to build, deploy and manage AI agents and workflows.
Quickstart
Cloud-hosted: sim.ai
Self-hosted
npx sim-setupDesktop: macOS
macOS 12+, Apple Silicon and Intel. See the desktop docs to point it at a self-hosted deployment.
Capabilities
Connect 270+ integrations (5,400+ actions, 520+ triggers) and every major LLM
Add Slack, Notion, HubSpot, Salesforce, databases, and more
Build agents visually, conversationally, or with code
Ingest files, knowledge bases, and structured table data
Monitor runs, logs, schedules, and workflow activity
One workspace, every surface
Chat and workflows are just the start — tables, files, and knowledge all live in the same workspace, in the browser or on your desktop.
Tables — a database, built in Files — one store for your team and every agent Knowledge — your agents' memory Desktop — Sim on your Mac, browser and terminal included
MCP server
Connect Claude, Claude Code, Codex, or any MCP client to Sim Cloud at https://mcp.sim.ai/mcp. Your agent can manage workspaces, run and deploy workflows, and work with tables, knowledge bases, files, and logs. Sign in with OAuth or use an API key.
Claude Code:
claude mcp add --transport http sim https://mcp.sim.ai/mcp, then open/mcpto sign inClaude: add
https://mcp.sim.ai/mcpas a custom connector under Customize → ConnectorsCodex:
codex mcp add sim --url https://mcp.sim.ai/mcp
See the MCP docs for other clients and for self-hosted URLs.
Self-hosting
Requirements: Node.js 20+ and Docker.
npx sim-setup is an interactive wizard that creates a small sim/ deployment directory, provisions the database, generates secrets, writes .env, connects a Chat API key, and starts the published Sim images with Docker Compose. It does not clone the repository.
When it finishes, open http://localhost:3000.
Inside a cloned Sim repository, run bun run sim-setup to unlock the source-only local development and Kubernetes modes.
Reconfigure an optional capability without rerunning the full wizard:
npx sim-setup config
npx sim-setup add email
npx sim-setup add storage
npx sim-setup add sandbox
npx sim-setup add jobs
npx sim-setup add cache
npx sim-setup add knowledge
npx sim-setup add chat
npx sim-setup add llm
npx sim-setup add integration slacknpx sim-setup config detects the effective local-dev, Docker Compose, or current-context
Helm configuration and reports configured, missing, or invalid capabilities and OAuth
integrations without printing credential values. This is separate from npx sim-setup status,
which reports whether installed services are running and healthy.
Manage your install from its directory:
npx sim-setup start | stop | restart # bring your install up / down / cycle
npx sim-setup update # pull and apply Compose images
npx sim-setup status # what's installed and healthy
npx sim-setup logs # follow logs
npx sim-setup doctor # diagnose configuration problems
npx sim-setup down # remove containers (data kept)
npx sim-setup reset # archive .env and wipe managed dataThe setup package detects how you're running and acts accordingly. Use --dir to create or manage a deployment somewhere other than ./sim.
Sim also supports local models via Ollama and vLLM. See the self-hosting docs for details.
Chat API Keys
Chat is a Sim-managed service. npx sim-setup connects a Chat API key for you — sign in when it opens your browser and the key is stored automatically. To view, create, or revoke keys later, go to sim.ai/selfhost/settings/chat-keys.
Environment Variables
See the environment variables reference for the full list, or apps/sim/.env.example for defaults.
Tech Stack
Next.js · Bun · PostgreSQL · Drizzle · Better Auth · Tailwind — and the rest of the stack
Framework: Next.js (App Router)
Runtime: Bun
Database: PostgreSQL with Drizzle ORM
Authentication: Better Auth
Schema Validation: Zod
UI: Shadcn, Tailwind CSS
Streaming Markdown: Streamdown
State Management: Zustand, TanStack Query
Flow Editor: ReactFlow
Docs: Fumadocs
Monorepo: Turborepo
Realtime: Socket.io
Background Jobs: Trigger.dev
Remote Code Execution: E2B
Lo que la gente pregunta sobre sim
¿Qué es simstudioai/sim?
simstudioai/sim es subagents para el ecosistema de Claude AI. Sim is the collaborative workspace to build, deploy, and monitor AI agents and workflows. Used by 100,000+ builders. Tiene 29.9k estrellas en GitHub y su última actualización registrada es del 2026-10-23.
¿Cómo se instala sim?
Puedes instalar sim clonando el repositorio (https://github.com/simstudioai/sim) o siguiendo las instrucciones del README en GitHub. ClaudeWave también te ofrece bloques de instalación rápida en esta misma página.
¿Es seguro usar simstudioai/sim?
Nuestro agente de seguridad ha analizado simstudioai/sim y le ha asignado un Trust Score de 100/100 (tier: Verified). Revisa el desglose completo de comprobaciones superadas y flags en esta página.
¿Quién mantiene simstudioai/sim?
simstudioai/sim es mantenido por simstudioai. La última actividad registrada en GitHub es del 2026-10-23, con 347 issues abiertos.
¿Hay alternativas a sim?
Sí. En ClaudeWave puedes explorar subagents similares en /categories/agents, ordenados por popularidad o actividad reciente.
¿Mantienes este repo? Muestra su Trust Score en tu README
La insignia muestra el Trust Score y el veredicto actuales de este repositorio y enlaza a esta página. Sigue los datos del catálogo: nadie puede comprar ni editar la puntuación que enseña.
[](https://claudewave.com/en/repo/simstudioai-sim)<a href="https://claudewave.com/en/repo/simstudioai-sim"><img src="https://claudewave.com/api/badge/simstudioai-sim" alt="ClaudeWave Trust Score for simstudioai/sim" width="320" height="64"></a>