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.