展示 HN：Type.com – 面向非技术用例的云端 Codex 和 Claude 代码
8 分•作者: krashidov•17 天前
大家好，我是 Komran，type.com 的 CTO 和联合创始人。我们今天正式上线。我一直将 type 描述为“非技术人员的 IDE”。它能让你构建出色的产品，而无需担心维护本地开发环境。
一切默认都以云端优先。无需处理复杂的交接流程或任何繁琐的操作。每个线程都由一个持久化的沙盒虚拟机支持，即使你进行 Git 操作，也不必担心 Git worktrees。你可以从 Claude、Codex、Slack 或电子邮件开始工作，然后将其推送到 Type 中的共享会话，你的整个团队都可以进行协同提示。
由于我们的“meta-harness”是 Codex CLI 和 Claude Code 的封装，你可以连接现有的订阅。因为我们是多人协作产品，所以我们必须确保只对用户创建的消息收取订阅费用。如果 Alice 拥有订阅并与代理开始一个线程，她将使用她的订阅。如果 Bob 加入并添加自己的提示，但 Bob 没有订阅，他将根据其 Type 使用量收费。我们不收取任何 token 溢价。
即使产品尚处于早期阶段，我们的客户也对我们非常满意，并更倾向于使用我们而不是 Claude Code。如果非要说我们相对于 Claude Tag/Claude Cowork 的优势，那就是：
* 你可以随时切换模型/harness，不受限于单一提供商。
在 Type 上创建自定义内部应用/产物更好，因为我们处理内部托管、RBAC、版本控制、开发/生产环境，甚至让你的应用能够与你的 Type 集成进行通信。共享内部应用就像共享 Google 文档一样简单。
* 底层只是 Claude Code 和 Codex。总的来说，它的工作方式应该与 Codex 和 Claude Code 非常相似。
* 在我上一家公司 Halp.com（已被 Atlassian 收购）时，我们发明了“Slack-first”这个词，因为我们知道人们喜欢在不切换上下文的情况下完成工作。Type 在 Slack 中表现出色。每个 Slack 频道都映射到一个公共或私有的“空间”，该空间具有对集成只读或读写权限的访问权限。每个空间都内置了默认的 harness、模型和工作级别。因此，你可以从 Slack 使用你的订阅。
* 我们的 CLI 允许你在本地机器上进行单人模式工作时，也能获得 Type 的最佳功能。Type CLI 可以将你的本地会话推送到 Type，以便其他人查看。它还可以推送文档进行协作编辑，甚至可以在本地重用你已获得访问权限的 Type 集成。
你今天就可以在 [https://type.com](https://type.com) 注册。
你将获得价值 100 美元的积分进行试用。构建这个产品非常有趣。与 Grok Bot、Codex 和 Claude Cowork 等产品竞争非常有趣，但我认为它们仍然非常偏向个人助理、单人模式。每个人都需要设置相同的集成，需要从头开始创建技能和自动化，而且每个 Frontier 的产品都会让你被锁定在其模型中。
查看原文
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.<p>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.<p>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.<p>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:<p>* 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.<p>* It's just claude code and codex under the hood. In general it should work very similar to how codex and claude code work<p>* 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.<p>* 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.<p>You can sign up today at <a href="https://type.com" rel="nofollow">https://type.com</a>.<p>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.