Vikhyath Mondreti
b7b0be8eef
* fix(memory): close app-service leak paths behind the per-task memory ramp Prod app tasks climb from ~3.0 GB to 9+ GB average (20.6 GB worst task) with uptime and reset only on deploy. The growth lives in the main Next.js process — the isolated-vm worker is a separate, bounded child and its disposal already runs in finally on every path. Four fixes at the sites that can actually accumulate there: - copilot stream teardown (lib/copilot/request/lifecycle/start.ts): the activeStreams registration, the 250ms Redis abort poller, and the SSE keepalive were acquired outside the try whose finally releases them, so a throw before the lifecycle started (e.g. resetBuffer on a Redis blip) or a throw inside the ordered teardown orphaned two immortal intervals and the registration. Add an idempotent backstop in the orchestration's outer finally; the ordered teardown sets a flag so the normal path pays nothing. - large-value cache (lib/execution/payloads/cache.ts): expiry was enforced only inside later cache calls, so on a quieting instance the last entries — parsed object graphs worth a multiple of their JSON-byte accounting — sat indefinitely instead of for the 15-minute TTL. Add a self-retiring, unref'd sweep interval, and export occupancy stats. - memory telemetry (lib/monitoring/memory-telemetry.ts): add the large-value cache occupancy and detached-context count to the periodic snapshot so the JSON-bytes-vs-heap amplification and context retention are readable from the same log line as heapUsedMB. - BYOK rotation cursors (lib/api-key/byok.ts): the tenant-keyed cursor Map had no delete, TTL, or ceiling. Bound it with an LRU; evicting an idle pool's cursor just restarts its rotation at index 0. - collab-doc converter (lib/collab-doc/converter.ts): the DOM guard read the bundled module's `window` binding while the install wrote `globalThis.window` — the same bundler mismatch documented for TipTap in next.config.ts — so a runtime where the two disagree re-allocated a multi-MB jsdom window on every conversion. Guard and install now go through globalThis, and the jsdom window is a module singleton either way. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * improvement(execution): idle-TTL touch-on-read + LRU eviction for the large-value cache Entry lifetimes were absolute-from-insert and eviction order was insertion order, so a value a live run kept referencing could expire or be pressure-evicted mid-use — while a genuinely idle entry survived the full window. Every authorized read now refreshes the expiry and moves the entry to the back of the eviction order: expiry and eviction only ever take entries nothing has read for a full TTL, and pressure eviction takes the least-recently-used recoverable entry. Strictly fewer mid-execution misses; TTL values, the admission budget, and the sole-copy (non-recoverable) eviction protection are unchanged. Touching stays behind the scope check so an unauthorized probe cannot extend a lifetime. Module TSDoc now records the standing constraint: the warm pass runs once per execution start, so the TTL must outlive the warm-to-first-reference gap — do not shorten it until warming is per-block. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
A workspace to build, deploy and manage AI agents and workflows.
Quickstart
Cloud-hosted: sim.ai
Self-hosted
npx sim-setup
Capabilities
- Connect 1,000+ integrations 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.
Tables — a database, built in |
Files — one store for your team and every agent |
Knowledge — your agents' memory |
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 slack
npx 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 data
The setup package detects how you're running and acts accordingly. Use --dir <path> 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
- Isolated Code Execution: isolated-vm
Contributing
We welcome contributions! Please see our Contributing Guide for details.
License
This project is licensed under the Apache License 2.0 - see the LICENSE file for details.
