# Soot Soot is the first public product from 2found: the agent backend for your product. Each agent (a Soot) is defined as code in the developer's repository, runs on one lightweight runtime the developer owns, and is reached from the product through the TypeScript SDK, a website chat or a chat app; it can improve against the developer's eval cases, with every change reviewable. It is built for product and indie developers; teams without a developer can still give recurring work — answering visitors, watching sources, writing, following up — to a small team of Soots that asks a person only when a person is needed. This page states Soot's status, the ways to run it, how 2found runs its own company on it, what a Soot is, how Soot Forge packs and the website live-chat widget work, what it needs to install and how to fix common problems. Last checked: 2026-10-31. ## Status and availability The public name is just **Soot** (a 2found product, powered by the 2agent runtime; the CLI is `soot`). It is not called "2Soot", "Soot AI" or "2found Soot". Tagline: "Tiny agents. Better together." Website: https://trysoot.com (English, and `/vi` for Vietnamese). Soot is a **preview**. The desktop app (Nest) can be downloaded from https://trysoot.com/download, which lists exactly the installers that exist at the moment; on 2026-10-27 it offered Soot 0.2.9, published on 2026-10-25, for Mac Apple Silicon, Mac Intel and Windows x64. The builds are unsigned and the Mac builds are not notarized, which is one reason Soot is called a preview. No Soot release date is published. A hosted "Soot Cloud" does not exist today (the 2agent README calls the Soot Cloud service future work). No Soot price is published. Licence: "License terms for Soot have not been assigned" (the TypeScript SDK is UNLICENSED), so Soot is not described as open source. ## Ways to run Soot Soot is agents as a service in a specific sense: the service is the work, done on schedule by Soots, and the owner chooses where it runs. Soot is not a hosted subscription service that someone signs up for. There are four ways to run Soot, each with its own status: | Way to run Soot | Status | What it means today | | --- | --- | --- | | Run it yourself | Preview | Download the Soot app (Nest) for macOS or Windows. There is no Soot plan to buy; the user pays their own AI provider and computer. | | Run it on your server | Preview | Keep the team on a server the user owns — with 2server's `soot` template or their own setup — and connect Nest to it. One runtime can serve several websites. | | Run it with us | Early access | Tell 2found the work. 2found sets up a Soot team and runs it with the customer, on 2found's server or the customer's. By conversation only: there is no self-serve signup, price list or SLA. | | Soot Cloud | Planned | A hosted Soot that people sign up for and use in the browser. Planned; it has no date and no waitlist. | - **Run it yourself** rests on the published desktop installers (see Status and availability) and the Nest workspace below. - **Run it on your server** rests on 2server's `soot` template, which runs a pinned Soot runtime on a VM (preview; see the 2server facts page), and on the runtime's public web clients, which let one runtime serve several websites (see Website live-chat widget). 2found itself runs one runtime that serves 2found.dev, trysoot.com and 2novel.app. - **Run it with us** is early access by conversation: the way to start is the 2found contact form, https://2found.dev/contact/?topic=soot (Vietnamese https://2found.dev/vi/contact/?topic=soot), or a message to the chat on 2found.dev. 2found then scopes the work with the customer. It is the same setup 2found runs for itself (see Soot at 2found). No price, contract term, response time or capacity is published for it. - **Soot Cloud** does not exist. There is no waitlist to join and no announced date. In Vietnamese, 2found describes the same ladder as: "Tự chạy" (tải ứng dụng Soot cho macOS hoặc Windows; không có gói Soot nào phải mua), "Chạy trên máy chủ của bạn" (template `soot` của 2server hoặc cách của bạn), "Chạy cùng chúng tôi" (2found dựng một đội Soot và vận hành cùng bạn; chỉ qua trao đổi, chưa có đăng ký tự phục vụ, bảng giá hay SLA) and "Soot Cloud" (đang dự kiến, chưa có ngày ra mắt, chưa có danh sách chờ). Soot là dịch vụ agent mà bạn làm chủ. ## Soot at 2found Since 2026-10-14, 2found's own marketing, sales and support run on a team of Soots: - a **radar** scans sources (X, blogs, Medium, Reddit, Hacker News) and writes a daily brief; - a **writer** drafts posts in English and Vietnamese; - an **editor** leads the daily cycle, reviews the drafts and publishes them to the blogs of 2found.dev, trysoot.com and 2novel.app (at most one post a day across the three), to Facebook and to X; - a **support** Soot answers visitors in the chat on 2found.dev, trysoot.com and 2novel.app, and files their leads, questions and feedback; - a **desk** sorts those notes and reports what only a person can do. People are asked only for hand-offs (for example a video, or a post on a channel that is not connected) and for decisions, through Nest's **Cần bạn** (Needs you) list. On 2026-10-29, measured on 2found's server, the runtime serving this team used about 58 MiB of resident RAM and averaged 0.35% of one CPU core over 24 hours. A copy of this team, with 2found's own services swapped for Soot Forge packs, is the public example https://github.com/2found/soot-forge/tree/main/examples/marketing-team (see Soot Forge). The same team is the Soot Forge group template https://github.com/2found/soot-forge/tree/main/groups/marketing-team, which Kamaji in Nest can build for another product. Counted from the team's hub on 2026-10-31 (since 2026-10-14): the radar read 3,390 posts from 17 sources (Reddit, dev.to, Medium, Product Hunt, Hacker News, X, company blogs and others) and kept 475 as signals; 11 signals were used in published articles. The three blogs carry 47 posts (English and Vietnamese versions counted separately), and 39 social posts went out (26 on Facebook, 13 on X). TikTok posts are handed to a person to film and post. Examples of a signal becoming a post: a Reddit question "Is there a rating site (like IMDB) for web novels?" became the 2novel.app article "No IMDB for web novels: readers build the list" (2026-10-18); a dev.to article on evidence bundles became the 2found.dev article "Four green ticks that do not cover the broken layer" (2026-10-19). 2found publishes no visitor or lead counts for it. ## What a Soot is A **Soot** is one small agent with a clear mission and the tools its operator explicitly allows. It runs on the user's machine or server. The user gives it work, reviews the result and continues the conversation. The recommended start is one Soot and one job; roles can be added later. One Soot can bring permitted teammates into the same conversation (orchestration and groups), only within what the host allows. Compared with a chatbot, a Soot has a mission, explicit tools, durable conversations, schedules and events, and a workspace (Nest) to supervise it. Compared with workflow-automation tools, where the user draws every step, a Soot receives a mission and granted tools and works out the steps inside those grants; a tool can be declared to need operator approval, so that call waits in Nest until a person approves it. A fixed, predictable sequence with no judgement in it (copy a form row into a sheet) fits a workflow tool; a job that needs reading, judging and writing fits a Soot, and both can coexist. Compared with an agent framework (a code library), Soot is a runtime and workspace configured with a mission, packs and grants. ## Nest workspace **Nest** is the operator workspace to create, configure, test and monitor Soots. It is not a runtime itself. The Nest desktop app prepares a local Nest and starts or reuses its bundled runtime. In Settings the flow is **save, activate, then Test**: "Saved" is not "Active" until the host acknowledges. Monitoring shows runs, known-cost estimates (not invoices) and freshness. ## Packs, capabilities and models - **Packs** bundle skills and tools; a **capability** is the group a Soot selects. Installing a pack grants nothing: the operator selects capabilities and runs `soot check --show`. - **Models:** the operator chooses the provider, the model and fallbacks. Keys or OAuth live in the host's vault, not in the Soot definition. Real model calls send relevant content to the chosen provider, and a local runtime does not mean the model runs offline. A model provider account (key or OAuth) is needed for real answers; the offline demo needs none. ## Safety, grants and control Soot's control model is "You choose the access; you can Stop a run (completed actions stay completed)". Host tools run with the host's OS access; a workspace is **not** an OS sandbox. The default `soot spawn` general Soot has write and host-shell grants, so it is not read-only; it can be narrowed, or `--empty` can be used. A Soot can read files or run commands only through granted tools, and `soot check --show` lists the grants. ## Product knowledge A Soot looks product facts up instead of carrying them in its prompt. A source declares the pages products publish about themselves (an `llms.txt` index or Markdown pages); the runtime mirrors them into a data pool, every 6 hours by default, and a Soot with that knowledge searches it (`knowledge_search`) before stating a fact. A fact customers ask for that the pages lack is recorded as a knowledge gap and reaches a person in Nest when it is asked in at least two conversations within 14 days. ## Soot inside a product Soot can be added to a product as configuration (sometimes called "agent as config"): the Soots, their missions and grants live as files next to the product's source code. A product backend talks to Soot over a conversation API with a backend-only key (`SOOT_API_KEY`); browsers never get that key. `soot spawn --product my-product` scaffolds this for an application (files only, scripted model, empty grants). ## Soot Forge Soot Forge is the catalog of community packs (skills and tools) that Soots can use: https://trysoot.com/forge ; source https://github.com/2found/soot-forge ; machine-readable catalog https://raw.githubusercontent.com/2found/soot-forge/main/catalog.json . - Catalog examples: office (Word/Excel/PowerPoint/PDF), ocr, image-gen, tts, google-workspace, video-editor, research, writing, website, email, live-chat, data-pool, browser-use, health, server-care, 2build and more. Some need host services (LibreOffice, FFmpeg, model services); installing a pack starts none of them. - Install inside a Soot workspace: `soot add https://github.com/2found/soot-forge/tree/main/packs/health` (pinning a reviewed commit instead of `main` is recommended for reproducibility). The install records the commit and digest, runs no scripts, grants nothing and never overwrites an existing pack. Then the pack README is read, the capability (for example `health/probe`) is selected in the Soot definition and `soot check --show` is run. - Share a pack: open a pull request with `packs//` plus a `catalog.json` entry, or an entry pointing at a pinned commit in the author's own repository. See CONTRIBUTING.md in the soot-forge repository. - With a coding agent: ask it to read https://github.com/2found/soot-forge/blob/main/USAGE.md and the catalog.json, find a pack for the task, explain its source and required capabilities, and install the chosen pack without automatically granting tools. - Each pack documents its own licence and terms; the catalog is public on GitHub. - Examples: https://github.com/2found/soot-forge/tree/main/examples/marketing-team is an autonomous marketing team as a Soot source (an editor, a radar, a writer and a browser poster in one group, a shared data pool, morning and afternoon schedules). It is the team 2found runs for its own blogs, with 2found's hub swapped for Forge packs. The editor publishes what passes its review and asks a person only for hand-offs (a video, an unconnected channel) and real decisions, through Nest's **Cần bạn** list. It is deployed with the `soot` CLI (`soot bundle --refresh ./soot-source`, then `soot source deploy ./soot-source`), which needs access to the private repository; with Nest alone the same Soots, group and schedules are created by hand from its files. The older `groups/marketing-team` template instead gates every publication on an operator approval. ## Website live-chat widget A Soot can answer visitors on a website, like a support chat. - The runtime host enables a public ingress and defines a **client**: a publishable key (`spk_...`), a fixed tenant, exact allowed origins, the assigned Soots, budgets and a challenge (Turnstile in production). The key grants only what the client assigns; visitors get server-issued session bearers and history is isolated per visitor. - In Nest: Settings, "External web" (Cài đặt, Web ngoài): create the client, assign eligible Soots, save, enable, apply; then copy the embed code ("Kết nối website · mã nhúng") that loads `/public/widget/loader.js` with `data-app` from the runtime's public origin. Rotating a key takes effect only after activation. - One runtime serves several websites: one client per site, each with its own key, allowed origins, assigned Soots, budgets and fixed tenant, so each site's visitor history stays separate. An agency can run one runtime for several customers' sites; a site does not need a runtime of its own. Two clients may share the same Soot. - Only safe, non-privileged Soots can be assigned to a public client. Operator and product keys must never be placed in the frontend. - The widget needs a runtime that the site owner (or an agency) operates; Soot has no hosted chat service. - **Leads, questions and feedback from the chat reach the team.** Give the website Soot a feedback desk (a private Soot) and it records a visitor's note — a lead, question, bug, feature request, complaint or general feedback, with the contact the visitor chose to give — and tells the visitor its reference (`FB-…`). The runtime can also store each note in a data pool. The desk Soot sorts the notes with its own tools; what only a person can do, such as replying to a lead, appears in Nest under **Cần bạn**. Soot has no order or CRM system of its own: notes live in the runtime and Nest, and putting them into a spreadsheet or another system takes a pack for it on the desk (for example `google-workspace` with `sheets-write`). ## Posting to Facebook, X, TikTok, Zalo and other channels Soot Forge has no ready-made Facebook, X, TikTok or Zalo pack today, so Soot does not ship an integration with any of them. Three routes exist: - **A service with an API:** a pack's tool runs a program the team provides (a script or CLI), so a pack can call the Facebook Graph API, the Zalo OA API or a company's own backend. Keys go in the host's vault and reach the tool as secret environment variables; the Soot never sees them. Writing that pack is the customer's (or their developer's) work; the docs show how (https://trysoot.com/docs , "reference" and pack authoring). - **A website without an API, through a browser:** the `browser-use` pack drives a real browser on the computer that runs the Soot. In the Nest desktop app (from v0.2.2) the browser panel offers **Cài trình duyệt / Install browser**: about 30 MB of tools and about 140 MB of Chromium, downloaded once per computer. The user logs in to the site in that panel; a Soot never asks for a password. Automating a logged-in account may break that platform's terms, and the operator decides. - **A human approves before anything goes public:** a tool can be declared `"approval": "operator"`, so the run pauses and waits in Nest until someone approves or refuses. This suits every public post, payment or bulk send. So posting automatically to TikTok, Facebook or Zalo is not available out of the box; it works with a pack that calls the platform's API or with the browser, and with an approval step the operator controls. ## Price and licence No Soot price is published, and there is no paid plan or subscription to buy. Soot is a preview with no hosted service, so its running costs go to third parties: the AI provider the user connects in Nest (billed by that provider for model usage) and the computer or VM that runs the runtime. Running a Soot team with 2found ("Run it with us") is early access by conversation: there is no self-serve signup, price list or SLA, and its scope is agreed with each customer. Licence: "License terms for Soot have not been assigned" (the TypeScript SDK is UNLICENSED); Soot is not described as open source. ## Install and requirements - Desktop installers listed on https://trysoot.com/download: Mac Apple Silicon, Mac Intel (macOS 12 or later, .dmg) and Windows x64 (64-bit Windows, .exe). They are preview and **unsigned** (Mac builds are not notarized). There is no Windows ARM or 32-bit installer and no Linux desktop installer. Desktop builds are not published automatically on every change; each release is published deliberately. - The installer cards on the download page read the published release catalog, so they show exactly what can be downloaded now: the version, the file size (MiB and exact bytes) and the SHA256. - The `soot` CLI is not publicly downloadable today. CLI archives (macOS and Linux amd64/arm64, Windows amd64) are published on the GitHub Releases of 2found/2agent, which is a **private** repository, and building from source also needs access to it (and the private 2ai dependency). For customers the path is the desktop app; the desktop app does not install the CLI. - A model provider account (key or OAuth) is needed for real answers. - Memory and CPU are small, because the model runs at the provider: no GPU is needed. Measured on 2found's own server on 2026-10-29 (runtime 0.5.0, up 24 hours), the Soot runtime serving 2found's team (5 Soots: support chat on three websites, a feedback desk, a news radar, a writer and an editor) used about 58 MiB of resident RAM (cgroup peak about 87 MiB including file cache), 0.16% of one CPU core over a 5-minute window and 0.35% averaged over 24 hours (about 300 CPU-seconds). Its container image is 12.5 MB. A data pool adds its own services (here about 12 MiB, plus about 65 MiB for its Meilisearch search engine). With 2server the `soot` template caps the runtime at 512 MiB by default (`memoryMb`). - Models: Soot calls hosted providers configured in Nest (Settings, AI provider) or `soot login `. A provider of type `openai` also takes a `base_url`, so Soot can call any OpenAI-compatible endpoint, including a gateway or a server you host yourself. 2found has not tested specific local model servers (for example Ollama), so that is not a promised setup. A local Soot runtime does not mean the model runs offline: the model provider still receives the relevant content. ## Getting started Customers start with the desktop app from https://trysoot.com/download: install it, open Nest, add an AI provider in Settings, then give the general Soot its first job. With the `soot` CLI (available to people with access to the private repository): ```sh soot version --json soot spawn my-work # creates a workspace with the general Soot, starts its runtime cd my-work soot check --show --secrets # validates config; does not call a model or run tools soot run "Help me plan this project" soot demo # scripted replies, no model key; not real AI ``` Other entry points: `soot spawn my-soot --empty` (blank), `soot nest` (start or reuse Nest), `soot spawn --product my-product` (scaffold for embedding Soot in an application), and `soot serve --config soot/deployment.json` (runtime on 127.0.0.1:7788 by default). A real provider is configured in Nest (Settings, AI provider; then pick the model and fallbacks) or via `soot login `. Docs: https://trysoot.com/docs (quick-start, initialization, operation, data-pool, orchestration, deployment, reference; append `/index.md` for Markdown). Optionally, Soot can run on a VM with 2server's `soot` template (preview); local use needs no 2server. ## Frequently asked questions - **Is Soot agents as a service (AaaS)? (Soot có phải là dịch vụ agent không?)** Yes, as agents as a service you can own: Soots do recurring work — answer visitors, watch sources, write, follow up — on schedule, and the owner chooses where they run: on their own machine (Preview), on their own server (Preview), or with 2found (Early access, by conversation). It is not a hosted service to sign up for; Soot Cloud is planned, with no date and no waitlist. See Ways to run Soot. - **Can 2found run Soot for us? (2found có chạy Soot giúp chúng tôi không?)** Yes, as early access by conversation ("Run it with us"): 2found sets up a Soot team and runs it with the customer, on 2found's server or the customer's. Start with the contact form, https://2found.dev/contact/?topic=soot (Vietnamese https://2found.dev/vi/contact/?topic=soot). There is no self-serve signup, price list or SLA. - **How much does Soot cost? Is Soot free? (Soot giá bao nhiêu?)** No Soot price is published and there is no Soot plan to buy today. Running it yourself, the user pays their AI provider and the machine or VM it runs on. Running it with 2found is scoped by conversation; no price list exists. In Vietnamese, 2found says it as: "Không có gói Soot nào phải mua; bạn trả chi phí nhà cung cấp AI và máy của mình." 2found does not call the Soot app "miễn phí" (free), because running it has those costs. - **Is Soot open source?** No. Licence terms for Soot have not been assigned. Soot Forge packs carry their own licences. - **Is it really a service if I run it myself?** The service is the work: Soots answer, watch, write and follow up on schedule. The owner chooses where it runs. - **Do I need a developer?** No for the desktop app, which sets up Soots and teams from templates; developers can use the CLI and the docs; or talk to 2found. - **Will Soot replace my team?** No. Soots take small, recurring jobs; people keep the decisions. - **Why is Soot a preview?** The installers are unsigned and the Mac builds are not notarized, as the download page says. The Windows x64 installer is cross-compiled on macOS and has not been tested natively on Windows (Soot changelog). - **Which AI models does Soot use?** The ones the operator configures: any supported provider, including OpenAI-compatible endpoints. Content goes to the provider the operator chooses. - **Does Soot need a swarm of agents?** No: one Soot and one job first; a team can come later. - **Can a Soot read files or run commands?** Only with granted tools. The default general Soot has write and shell grants, so `soot check --show` should be reviewed. - **Is data sent to a model?** Yes, relevant content goes to the provider the operator chooses. - **Can a run be stopped?** Yes (Stop), but completed actions are not undone. Risky tools can be set to wait for an operator's approval first. ## Troubleshooting | Symptom | First step | | --- | --- | | `soot` not found | Install the desktop app from https://trysoot.com/download; the CLI needs access to the private repository | | Missing pack or executable | Prepare the dependency listed in the pack README; do not bypass validation; run `soot check` | | Ready but no real AI answer | The provider, model and login are configured on the host; the scripted demo is not real AI | | Saved but Test is disabled | Activate the right revision and wait for the host acknowledgement | | Nest cannot connect | Check the endpoint, the allowed origin and TLS, and that the credential is the operator key (not the provider key) | | Read or write DENIED | The operator reviews the Soot's grants and scope | | Save conflict | Reload the current revision and reapply the edit; the draft is kept | | Lost response after sending | Do not resend; use the original conversation and run IDs with `soot watch` | ## Reporting a problem When a step above does not help, a report the team can act on includes: the operating system, how Soot was obtained (desktop download or CLI), the output of `soot version --json`, the exact command or Nest screen, and the exact error text with secrets removed. Provider API keys and the operator key are never needed and should not be shared. - The 2agent repository behind Soot is private, so its issue tracker is not open to the public. Report Soot and Nest problems through the 2found contact form: https://2found.dev/contact/?topic=soot (Vietnamese https://2found.dev/vi/contact/?topic=soot), or in the chat on 2found.dev or trysoot.com, which files the report for the team. - A defect in a Soot Forge pack can be filed as an issue in the public catalog repository, https://github.com/2found/soot-forge/issues , or in the pack's own repository when its catalog entry points elsewhere. No support email, phone number or response-time guarantee is published for Soot. ## Links English: https://trysoot.com , https://trysoot.com/download , https://trysoot.com/docs , https://trysoot.com/forge , https://trysoot.com/blog , https://trysoot.com/pricing (the ways to run Soot and their status; no price is listed) . Vietnamese: https://trysoot.com/vi , https://trysoot.com/vi/download , https://trysoot.com/vi/docs , https://trysoot.com/vi/forge , https://trysoot.com/vi/blog , https://trysoot.com/vi/pricing . Talk to 2found about running Soot ("Run it with us"): https://2found.dev/contact/?topic=soot (Vietnamese https://2found.dev/vi/contact/?topic=soot). Repositories: https://github.com/2found/soot-forge (public catalog); the 2agent repository behind Soot is private. Machine-readable Soot docs: https://trysoot.com/docs/llms.txt .