A website

Get a working preview you can click through, then adjust the layout visually instead of only describing changes.

Try first: Ask for one page with a clear purpose, such as a tutoring landing page. Test its buttons in the preview before adding more.

The free plan currently limits you to 7 messages a day. Treat the output as a starting point: check forms, mobile layout and security before publishing. A generated preview does not mean payments or a backend are ready.

Build and preview in the browser. Useful for trying a small interactive idea before installing a development environment.

Try first: Describe a single-page app with one interaction. Try that interaction in the preview before adding accounts or payments.

Free usage is capped at 300,000 tokens a day and 1 million a month. Larger projects consume more context. Custom domains and removing branding are paid. Generated code still needs functional and security checks before serving real users.

Describe the flow you want and refine the web app through conversation. Useful when you can explain the product but do not want to start by writing code.

Try first: Ask for one small workflow using sample data, such as a tutoring booking request. Test every step before adding real customer information.

Build credits, Cloud hosting and AI inside the finished app have different allowances. A free prototype is not unlimited free hosting. Inspect permissions, form behavior and usage costs before publishing a real service.

Use an AI starting layout, then change the actual page on a canvas. A good fit for a public portfolio or service page, not a complex backend.

Try first: Create one portfolio page, replace the sample work with your own and check the phone layout before publishing.

The free plan includes a one-time 500 AI credits, not a recurring allowance. Custom domains require a paid site plan, and free hosting has bandwidth limits. Confirm forms and links work; a designed page is not a complete business system.

Keep AI changes, code and the running app together. Useful when an idea needs working behavior, not just a static page mockup.

Try first: Start a small app with sample data. Run it and test its main action before enabling external services or a real database.

Starter has limited Agent access and daily credits. Publishing allowances do not mean every model, integration or hosting workload is free. Review usage and app security before using real user data or accepting payments.

Work inside the editor with your project's files in context. Useful for a change that crosses several files, not another isolated code snippet.

Try first: Open a backed-up project, ask for one small change and review the diff. Run the project's tests before accepting it.

This is a desktop code editor, not a no-code builder. Free Agent, chat and completion usage is limited. Keep secrets out of prompts and review changes carefully; suggested code can introduce bugs or security problems.

Use assistance inside a supported editor, without moving every question into a separate chat window. Useful when you want to keep your current coding setup.

Try first: Enable Copilot in your supported editor. Write a small function and its test, then inspect the suggestion before accepting it.

Free completions and AI requests have separate limits; it is not unlimited Agent access. An editor integration does not make code correct, secure or licensed for every use. Review the result and run tests.

Try model-backed behaviour on your own computer before building around a metered cloud service. Useful for developers who want control over a small experiment.

Try first: Choose a small local model that fits your computer. Test it against ten sample prompts for your intended feature before connecting it to an app.

Models need downloading, disk space and enough memory; speed and quality depend on the model and hardware. Local use is separate from cloud plans. Check each model's licence before commercial use and do not assume a local model matches a leading hosted assistant.

Use a desktop interface to try a model and ask questions about a sample document before deciding whether it belongs in your project.

Try first: Download a small compatible local model and ask a question about a document whose answer you already know. Compare the answer with the source.

You need disk space, memory and an initial model download. Select local processing if offline use is the reason you chose it; cloud features have separate plans. Model licences and hardware requirements differ, and answers still need checking.

Compare prompts and model settings on a small sample before wiring them into a bot or website. Useful when you need repeatable behaviour, not just a helpful chat reply.

Try first: Use a free-tier project and ten invented customer messages. Ask for a category for each, then check the mistakes before changing the prompt.

Model availability, rate limits and eligibility vary. Linking a paid API key can make usage chargeable. Data terms differ by account and region; do not put secrets or sensitive customer data into a free experiment. A good demo is not a production reliability test.