A website for your business. An application for your team. An agent to help with the work behind it. Describe what you need, then build, review and improve it in MaShop.
Code and Agents serve different needs. They share the project context and available connections, while keeping their conversations separate.
Describe a website, application, dashboard or change to an existing project. Review the generated files, try the preview and refine the result. Your software code belongs in a GitHub repository you control.
Explore CodeSet instructions, choose the connected tools and add relevant skills or memory. Follow the run history and respond when an action needs your approval. Start with a task whose outcome you can verify.
Explore AgentsConnect accounts through MaShop integrations or add an MCP server that exposes the tools you need. Available actions depend on the connection, your permissions and the provider. You decide which access to grant.
Explore connectionsA useful request describes who the work is for, what should happen and how you will know it is ready.
Explain the pages, features or task you need. Include your language, visual preferences, examples and constraints rather than accepting a generic starting point.
Use Code to create or change software. Use Agents for work with connected tools. Connect the accounts the task needs before asking for actions in those services.
Inspect the files and preview for software, or the activity and outputs for an agent run. Check a real path through the result and handle any requested permissions.
Ask for focused changes. When software is ready, choose and connect a hosting provider. For recurring tasks, set up a routine and review its execution history.
Describe the people you want to help and the work you want to complete. Your brief shapes the pages, features and agent tasks.
Present a service, an agency, a portfolio or a campaign with pages and content suited to its audience.
Build a client portal, a SaaS interface or an internal tool with the screens and data flows your team needs.
Ask an agent to collect information, organize findings or prepare a report using the tools you have connected.
Define a repeatable task, select its tools and schedule it as a routine. Check the outcome of each run rather than assuming success.
Building with AI still needs clear boundaries: what it can access, what it has changed and what you want to do next.
Connect your GitHub account for project code. Review changes and saved versions before relying on a release.
How software projects workAn agent can use the actions exposed by its connected tools. Permission checks and approval requests still apply; connecting an account does not authorize every possible action.
Read about access and securityAI work uses credits. Model access and project limits depend on your account. Preview time and external hosting fees are separate; consult the current pricing before starting.
See plans and creditsUse Code to create websites, SaaS applications, dashboards and internal tools. Use Agents for research and tasks in connected services. Describe the users, actions and result you want, then review the work in your project.
Code is the conversation for building and modifying software. Agents is the space for tasks that use connected tools, instructions, skills and memory. Their conversations stay separate, and a project can need both.
Connect the accounts required by the task. Software project creation currently requires GitHub and Supabase. A hosting provider is a separate choice when you publish. Agent tools depend on the connections available to that agent.
Yes. Describe your requirements in French and specify the language you want for generated content. The public presentation and documentation have dedicated French pages; tool names and provider interfaces may use their own language.
Start with one concrete request. Review the result, then take the next step.