← Automation

SmythOSSmythOS

SmythOS

agent平台Agent platform 开源MITOpen source, MIT 自托管Self-hosted 运行时Runtime 收缩中Contracting partial lifecycle: maintenance 核验Checked 2026-10-30

SmythOS 现役真相面是 GitHub 上的开源 agent 运行时 SRE（仓描述当日在册：cloud-native runtime for agentic AI， local/cloud/edge 三态）：官网 smythos.com 已 302 重定向到 SRE 仓——早期「无代码 agent 平台+托管服务」的定位不再自证；SRE/studio/docs 三仓推送停在 2026-04-03（未 archived），本站按 maintenance 口径写。

SmythOS's current truth surface is the open-source agent runtime SRE on GitHub (repo description on record same day: cloud-native runtime for agentic AI, local/cloud/edge): smythos.com now 302-redirects to the SRE repo — the early "no-code agent platform + hosted service" positioning no longer self-attests; pushes across the SRE/studio/docs repos stopped at 2026-04-03 (not archived), and this profile is written on maintenance terms.

适合与不适合When to use it, when not to

适合：要 MIT 许可的 agent 运行时自托管、读源码评估 agent 编排设计。不适合：要活跃产品与托管服务、要企业支持叙事、要大陆直连备案入口。

Fits: self-hosting an MIT-licensed agent runtime (local/cloud/edge), reading the source to evaluate agent-orchestration design. Not a fit: wanting an active product and hosted service, an enterprise-support narrative, a filed direct-mainland entry.

中文生态China availability 国产 / 国内可直接用 / 备案状态 · 快照domestic / direct access / CAC filing · snapshot 2026-10-30

出品属地Origin: 国外出品foreign-made　SmythOS（美国公司背景；官网重定向后主体信息未在册，按 GitHub org 为真相面）。SmythOS (US company background; with the site redirecting, entity info is not on record — the GitHub org is the truth surface).
国内使用Direct access: 直连未核验direct unknown　smythos.com 直连实测为 302→GitHub（GitHub 仓直连 200）——重定向目标可达但产品官网已不存在，不下「直连可用」结论。smythos.com measured a 302→GitHub direct (the GitHub repo measures 200 direct) — the redirect target is reachable but the product site no longer exists; no "direct access works" conclusion is drawn.
备案状态CAC filing: 未见于备案名单not in filing list：未见于网信办公示名单（2026-10-30 检索百炼公示页与第十六批批次清单，未见 SmythOS 条目）；该产品未面向大陆公众提供服务，备案不适用。not in the CAC public registry (Bailian disclosure page and the 16th batch list searched 2026-10-30; no SmythOS entry); the product does not serve the mainland public, so filing does not apply.

备案信息以网信办《生成式人工智能服务已备案信息》公示名单为准（按批次滚动更新，本站只抄编号不解读）；「大陆可直连」是本站从大陆网络直连实测的结果，不是厂商承诺。GitHub 类站点当日实测有波动，口径写在依据里。Filing status is quoted from the CAC public registry (updated batch by batch; this site copies the number and does not interpret it). "Direct access" is this site's own reachability measurement from a mainland network, not a vendor promise. GitHub-hosted sites fluctuated on the measurement day — the note says so.

固定坐标系Fixed coordinate system

8 个维度dimensions, 与同分区其他对象逐项可比each comparable item by item against others in the same section.

模型与开放条件Model & openness: SRE 运行时对接各家模型（仓描述当日在册：cloud-native runtime for agentic AI）； sre-models-pub 仓在册（模型配置发布面）；现役可用模型清单未逐条核验。
The SRE runtime connects to various models (repo description on record same day: cloud-native runtime for agentic AI); the sre-models-pub repo is on record (model-configuration publishing surface); the currently usable model list not verified item by item.
运行位置Where it runs: 开源自托管是现役主形态：官网 smythos.com 当日 302 重定向到 github.com/smythos/sre（官网让位于仓）； SRE 仓描述明言 local/cloud/edge 三态运行；托管 Studio 服务面未逐条核验。
Open-source self-hosting is the current main form: smythos.com redirects 302 to github.com/smythos/sre the same day (the site yields to the repo); the SRE repo description states local/cloud/edge execution; the hosted Studio service surface not verified item by item.
本地文件Local files: 自托管运行时数据在本机/自有部署（local 态在仓描述在册）；托管形态数据面未逐条核验。
Self-hosted runtime data stays on your own machines/deployments (the local mode is on record in the repo description); the hosted form's data surface not verified item by item.
关机后的任务Tasks after shutdown: agent 运行时（build/run/manage）是仓描述主轴；后台常驻与调度机制细节未逐条核验—— 且仓推送停在 2026-04-03（GitHub API 当日核验），现役维护强度存疑。
The agent runtime (build/run/manage) is the repo description's main axis; background residency and scheduling details not verified item by item — and repo pushes stopped at 2026-04-03 (GitHub API verified same day), so current maintenance intensity is in doubt.
工具与扩展Tools & extensions: smyth-docker-mcp 仓在册（MCP 方向）；skills 仓在册；具体工具/连接器清单未逐条核验。
The smyth-docker-mcp repo is on record (MCP direction); a skills repo is on record; the concrete tool/connector list not verified item by item.
上下文与记忆Context & memory: 运行时的 agent 状态管理在仓描述在册（manage intelligent agents）；跨会话记忆机制细节未逐条核验。
Runtime agent-state management is on record in the repo description ("manage intelligent agents"); cross-session memory details not verified item by item.
权限与限制Permissions & limits: MIT 运行时（许可宽松）；商业服务条款未逐条核验；训练用途开关路径未逐条核验。
MIT runtime (permissive license); commercial service terms not verified item by item; training-use toggle path not verified item by item.
适合什么任务Best for: 适合：要 MIT 许可的 agent 运行时自托管（local/cloud/edge）、读源码评估 agent 编排设计。不适合：要活跃产品与托管服务（官网已让位于仓、推送停 2026-04）、要企业支持叙事、要大陆直连备案入口。
Fits: self-hosting an MIT-licensed agent runtime (local/cloud/edge), reading the source to evaluate agent-orchestration design. Not a fit: wanting an active product and hosted service (the site already yields to the repo, pushes stopped 2026-04), an enterprise-support narrative, a filed direct-mainland entry.

头号误解Top misconception

官网让位于仓：smythos.com 当日 302→github.com/smythos/sre——按「有官网=有活跃产品」的直觉建档会错位；现役真相面是 GitHub orgThe site yields to the repo: smythos.com 302-redirects to github.com/smythos/sre the same day — the intuition "has a site = has an active product" misleads; the current truth surface is the GitHub org
收缩信号在册：SRE/studio/docs 三仓推送都停在 2026-04-03（GitHub API 当日核验，未 archived）——按「活跃项目」评估维护/安全响应有风险，本档案按 maintenance 口径写Contraction signals on record: pushes across the SRE/studio/docs repos all stopped at 2026-04-03 (GitHub API verified same day, not archived) — assessing maintenance/security response as an "active project" carries risk; this profile is written on maintenance terms
早期 SmythOS 主打「无代码 agent 构建平台+托管服务」——现官网重定向后该定位不再自证，历史定位≠现役形态Early SmythOS led with a "no-code agent building platform + hosted service" — after the site redirect that positioning no longer self-attests; historical positioning ≠ current form

未知项清单Known unknowns

托管服务现役状态（未核验）
商业主体与条款（官网重定向后未在册）
停更原因（收缩/转型/被收购均未在册——不下结论）
现役可用模型清单（未逐条核验）

Current status of the hosted service (unverified)
Commercial entity and terms (not on record after the site redirect)
Reason for the dormancy (wind-down / pivot / acquisition — none on record; no conclusion drawn)
The currently usable model list (not verified item by item)

证据来源Evidence sources

判断可回到以下一手源复核。本站核验日Every judgement can be rechecked against the primary sources below. Verified on 2026-10-30，内容更新日content updated on 2026-10-30。

类型Type	名称Name	链接Link
official	SmythOS · 官网（当日 302 重定向至 GitHub SRE 仓，重定向链当日核验）SmythOS · official site (302-redirects to the GitHub SRE repo the same day; redirect chain verified same day)	https://smythos.com
repo	SmythOS/sre · 运行时仓（MIT，GitHub API 当日核验 ★1,304/pushed 2026-04-03，未 archived）SmythOS/sre · runtime repo (MIT, GitHub API verified same day: ★1,304 / pushed 2026-04-03, not archived)	https://github.com/smythos/sre
repo	SmythOS org · 仓库列表（smythos-studio MIT ★656/smyth-docs NOASSERTION/smyth-docker-mcp MIT，推送集中于 2026-04 停摆，GitHub API 当日核验）SmythOS org · repository list (smythos-studio MIT ★656 / smyth-docs NOASSERTION / smyth-docker-mcp MIT; pushes cluster and stop at 2026-04, GitHub API verified same day)	https://github.com/orgs/smythos/repositories
changelog	SmythOS/sre · commits 页（最后推送 2026-04-03，作变更记录——仓无正式 releases）SmythOS/sre · commits page (last push 2026-04-03, serving as the change log — the repo has no formal releases)	https://github.com/smythos/sre/commits

实测记录Measured runs

本档未跑工作流搭建实测；结论只覆盖平台能力与权限边界。

实测建议（三条，都指向官方可读页没给的东西）：

SRE 在停更窗口后能否随新版依赖构建（推送停 2026-04，依赖漂移风险未核验）
托管 Studio 服务是否仍在运营（studio 仓 MIT 但服务面未在册）
local/cloud/edge 三态的实际差异与文档完整度（仓描述在册，细节未核验）

This site has not completed measured runs. The coding-oriented test protocol is at protocols/coding/_protocol.md (the coding task suite does not apply to agent platforms).

Suggested measurements (three, all pointing at things the official readable pages do not give):

Whether SRE still builds against updated dependencies after the dormancy window (pushes stopped 2026-04; dependency-drift risk unverified)
Whether the hosted Studio service is still operating (the studio repo is MIT but the service surface is not on record)
Actual differences and doc completeness across local/cloud/edge (on record in the repo description; details unverified)