What is MaShop?
An AI workspace for creating software and getting work done with connected tools.
Two ways to work
Use Code to create and change a website or application. Describe the result, inspect the files and preview, then refine it in conversation. You can work on a portfolio, an internal tool, a booking service or a business application; your request determines the product.
Use Agents to research a question, work with connected services or configure a reusable agent for a specific job. An agent combines your instructions, selected tools and permission settings. For a recurring task, you can also create an automation with its own model and instructions, without assigning an agent. Connecting a service gives access to its available tools; it does not approve every action.
Choose the starting point
- For a site, a screen or a code change, open a Code conversation and describe the result you need.
- For research or an operational task, open Agents and state the task, the source of information and the expected output.
- If the task needs an account you have not connected, follow the connection proposal before asking the agent to use its private data.
Check the result
A response, a saved file, a successful tool action and a published site are different results. Check the relevant preview, execution history or connected service before relying on a task. If an approval is pending, the action has not happened yet.
Start with a small task you can verify: one working page, one research summary with sources or one draft in a connected tool. Add the next requirement once that result is clear.
Use the two areas together
Code and Agents serve different parts of the same work. You can build a service website in Code, then use Agents to research suppliers or prepare a report from connected tools. Keep each request in the area suited to its outcome; connect only the services that task needs.
For example, ask Agents to compare appointment software using current public sources. Then give Code the selected requirements for a booking interface. A page that looks like a booking form is still a demonstration until the actual scheduling service, data flow and permissions have been connected and tested.