展示HN：Type.com – 为非技术使用案例提供的云端Codex和Claude代码
大家好，我是Komran，type.com的首席技术官和联合创始人。我们今天正式上线。我把type描述为“非技术人员的IDE”。它允许你构建非常酷的东西，而不必担心维护完美的本地开发环境。
一切默认都是云优先的。无需处理交接流程或其他奇怪的事情。每个线程都由一个持久的沙箱虚拟机支持，因此如果你在进行与git相关的工作，甚至不必担心git工作树。你可以从Claude、Codex、Slack或电子邮件开始工作，然后将其推送到Type中的共享会话中，整个团队都可以共同进行提示。
由于我们的“元工具”是Codex-CLI和Claude代码的封装，你可以连接现有的订阅。因为我们是一个多人产品，我们必须确保只对该用户创作的消息进行计费。如果Alice有一个订阅并且她与一个代理开始了一个线程，她的订阅将被使用。如果Bob加入并添加了自己的提示，但Bob没有订阅，他们将根据其在Type上的使用情况进行收费。我们不会对令牌收取任何额外费用。
尽管产品还处于早期阶段，我们的客户非常喜欢我们，并且更愿意使用我们而不是Claude代码。如果让我说我们相对于Claude Tag/Claude Cowork的优势，那就是：
* 你可以随时切换模型/工具，不会被锁定在单一提供商上。
在Type上创建自定义内部应用/工件更好，因为我们处理内部托管、RBAC、版本控制、开发/生产环境，甚至你的应用与Type集成之间的通信能力。共享内部应用非常类似于共享Google文档。
* 它的底层就是Claude代码和Codex。总体来说，它的工作方式应该与Codex和Claude代码非常相似。
* 在我之前的公司halp.com（被Atlassian收购）时，我们发明了“Slack优先”这个术语，因为我们知道人们喜欢在不切换上下文的情况下工作。Type在Slack中表现出色。每个Slack频道映射到一个公共或私有的“空间”，该空间对集成具有只读或读/写访问权限。每个空间都有一个默认的工具、模型和内置的努力级别。因此，你可以直接在Slack中使用你的订阅。
* 我们的CLI允许你即使在本地机器的单人模式下工作时，也能获得Type的最佳部分。Type-CLI让你将本地会话推送到Type，以便其他人查看。它还可以推送文档以进行协作编辑，甚至可以重用你在Type上获得访问权限的相同集成。
你今天可以在 [https://type.com](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.<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.