Skip to content
Changelog

Report a bug

Apps

Apps are working tools AI builds inside a Space. Use them for product dashboards, CRMs, trackers, intake forms, review queues, project boards, and internal workflows.

An app can use persistent data and stay securely available to your team. It lives in the Space Library with the thread that created it, so everyone can understand where it came from and keep improving it.

Describe the job, data, views, actions, and access the app needs. AI can build a first version and show it in the thread.

From there, your team can prompt together, comment, select part of the app, and ask AI to change it. The working version updates as you iterate.

Keep the request specific. Name the fields, filters, workflows, and decisions the app should help with.

AI can use the Space’s connections to build and update an app with business data. The app itself does not receive every Space credential. Type keeps connection use inside the work that updates it.

Use Automations when the app should refresh or reconcile data on a schedule.

For example, an automation can:

  • Refresh a dashboard every morning.
  • Add records found during a recurring sweep.
  • Compare app data with a connected source.

Keep the recurring logic in the automation and the app focused on storing and presenting its data.

Apps become part of the Space Library. Open an app from the Library to use it, review its history, or jump back to the threads that changed it.

The same Space can hold the app, the documents that explain it, the skills used to maintain it, and the conversations where your team makes decisions.

Claude, Codex, and other local development tools can check out a Type App with the Type CLI, run its frontend locally, and use a Type-managed Convex development backend. The CLI synchronizes the complete authored source tree without requiring a Git repository and stops instead of merging divergent edits automatically.

Local development updates shared editable source but does not automatically create a hosted draft. Push an update when it is ready for hosted review, then publish it separately. The first push for a new app is the exception: it creates the initial live release and requires explicit confirmation.

See Type CLI: Develop Type Apps locally for setup, synchronization, conflict recovery, publishing, and access safety.

An app can be shared with specific people, private Spaces, the workspace, or through a public link when workspace policy allows it.

Anyone with access can use the app and its data. Review both before sharing outside your team.