Show HN：Type.com——面向非技术场景的云端多人 Codex/Claude

大家好，HN，我是 Komran，type.com 的 CTO 兼联合创始人。我们今天正式发布。我一直将 Type 描述为“面向非技术人员的 IDE”。它让你无需担心维护完美的本地开发环境，也能构建非常酷的东西。

默认情况下，一切都以云端优先。无需在交接流程中手忙脚乱，也没有其他奇怪的操作。每个线程都由一个持久化沙箱 VM 支撑；如果你在处理 Git 支持的项目，甚至无需操心 Git worktree。你可以从 Claude、Codex、Slack 或电子邮件开始工作，然后将其推送到 Type 中的共享会话，让整个团队共同提示（co-prompt）。

由于我们的“meta-harness”是对 codex-cli 和 Claude Code 的封装，你可以连接自己现有的订阅。由于我们是一款多人协作产品，必须确保只有实际撰写消息的用户才会消耗其订阅额度。如果 Alice 有订阅，并且她与 Agent 发起了一个线程，那么将使用她的订阅。如果 Bob 进入该线程并添加自己的提示，但 Bob 没有订阅，那么他的使用量将计入 Type 用量。我们不会在 token 上收取任何加价。

尽管产品还处于非常早期的阶段，我们的客户已经很喜欢它，并且更倾向于使用它而非 Claude Code。如果要说我们相较于 Claude Tag/Claude Cowork 的优势，我认为包括以下几点：

• 你可以随时切换模型/运行框架（harness），不会被锁定在单一供应商上。在 Type 上创建自定义内部应用/Artifact 更好，因为我们负责内部托管、RBAC、版本控制、开发/生产环境，甚至支持你的应用与 Type 集成进行交互。共享一个内部应用的体验非常接近于共享一份 Google 文档。

• 底层就是 Claude Code 和 Codex。总体而言，它的工作方式应该与 Codex 和 Claude Code 非常相似。

• 在我上一家公司 halp.com（已被 Atlassian 收购）时，我们创造了“Slack-first”这个词，因为我们知道人们喜欢在不切换上下文的情况下完成工作。Type 在 Slack 中表现很出色。每个 Slack 频道都会映射为一个公开或私有的“Space”，并拥有对集成的只读或读写访问授权。每个 Space 都内置默认的 harness、模型和 effort level。因此，你可以完全通过 Slack 使用自己的订阅。

• 我们的 CLI 让你即使在本地机器上以单人模式工作，也能获得 Type 最有价值的能力。type-cli 可以将你的本地会话推送到 Type，供其他人查看。它还可以推送文档以供协作编辑，甚至能在本地复用你获授权访问的同一批 Type 集成。

你今天就可以在 https://type.com 注册。

你将获得价值 100 美元的额度，可以随意体验。构建这个产品非常有趣。与 Grok Bot、Codex 和 Claude Cowork 等产品竞争也很有意思，但我认为它们仍然主要处于个人助手、单人模式阶段：每个人都必须重复配置相同的集成，技能和自动化都需要从头创建，而且每家前沿厂商的产品都会让你锁定在其模型之中。

Hey HN, I'm Komran, the CTO and cofounder of type.com. We're launching today. I've been describing type as "the IDE for non technical people." It allows you to build really cool shit without having to worry about maintaining the perfect local dev environment.

Everything is cloud first by default. No fumbling with handoff flows or anything weird like that. Every thread is backed by a persistent sandbox VM so you don't even have to worry about git worktrees if you're doing something git backed. You can start work from claude, codex, slack, or email and then push it into a shared session in Type where your whole team can co-prompt.

Since our "meta-harness" is a wrapper of codex-cli and claude code, you can connect your existing subscriptions. Because we're a multiplayer product we had to make sure that we only bill the subscription for messages authored by that user. If Alice has a subscription and she starts a thread with an agent, she will have her subscription used. If Bob comes in and add their own prompt but Bob does not have a subscription, they will be billed against their type usage. We don't charge any margin on tokens.

Even with how early the product is, our customers love us and prefer us to using claude code. If I had to say our advantages over claude tag/claude cowork it would be these:

• You can switch models/harnesses anytime, you aren't locked into a single provider. Creating a custom internal app/artifact is better on type because we handle internal hosting, RBAC, version control, dev/prod environments, and even the ability for your apps to talk to your type integrations. Sharing an internal app is very akin to sharing a google doc.

• It's just claude code and codex under the hood. In general it should work very similar to how codex and claude code work

• At my last company, halp.com (acquired by Atlassian) we invented the term "Slack-first" because we knew that people loved doing work without context switching. Type is great in slack. Each slack channel maps to a public or private "Space" which has access read only or read/write access grants to integrations. Each space has a default harness, model, and effort level built in. So you can use your subscriptions all from slack.

• Our CLI allows you to get the best parts of type even when you're working in single player mode on your local machine. The type-cli lets you push your local session up to type so that other can take a look at it. It can also push up a doc for collaborative editing, and even reuse the same integrations that you've been given access to on type locally.

You can sign up today at https://type.com.

You get $100 worth of credits to mess around with it. It's been really fun building this. Competing with the likes of grok bot, codex, and claude cowork has been really fun, but I think that they are still very much in the personal assistant, single player mode. Each person has to set up the same integrations, skills and automations need to be created all from scratch, and every frontier's product is gonna make you be locked in to their model.