How to deploy Sanity v3 schemas so they appear in Vision tool and sanity.io/manage

I can see the issue you're running into! When you're running Sanity Studio embedded in your Next.js app (at localhost:3000/studio), you're essentially running a local development version of the Studio. This is different from any hosted/deployed Studio you might have at manage.sanity.io.

The key thing to understand: Your schemas are defined in your code (in your Next.js project), and they work locally because your local Studio reads them directly from your codebase. The Vision tool should work perfectly fine with just your local schemas for basic querying - you don't actually need to "deploy" schemas to query them in Vision.

If Vision isn't showing your documents correctly, here are the most common issues:

1. Dataset mismatch: In Vision, check the dropdown at the top to make sure you're querying the correct dataset (likely "production" or "development"). Your new documents might be in a different dataset than what Vision is currently pointing to.

2. API version: Also in Vision's dropdown, verify you're using the correct API version. Try using the latest API version to ensure you're getting the most up-to-date behavior.

3. Document creation: Make sure you've actually created documents with your new schema types in the Desk view. Just adding the schema doesn't create documents - you need to create actual content using those schemas first.

4. Authentication/Perspective: Vision uses your authenticated session and can see drafts. Try querying with *[_type == "yourSchemaType"] to see all documents of that type.

Regarding manage.sanity.io:

The Manage interface at manage.sanity.io is for project administration (managing team members, datasets, API tokens, etc.). It's separate from your Studio. If you're running an embedded Studio in Next.js, you typically won't see schema changes reflected at manage.sanity.io because that's not where your Studio is hosted.

When you DO need to deploy schemas:

Schema deployment via sanity schema deploy is only necessary if you're using newer AI features like Agent Actions, AI Assist, or Canvas. For basic Vision querying in your local embedded Studio, it's not required.

However, if you want a hosted version of your Studio at yourproject.sanity.studio (which would show up in manage.sanity.io), you'd run sanity deploy - this builds and deploys your entire Studio to Sanity's hosting, including your schemas.

Try this first: In your Vision tool, make sure you're on the right dataset and try a simple query like *[_type == "yourNewSchemaType"] - that should show you if documents of that type exist. The issue is almost always dataset selection rather than schema deployment!