Skip to Content

Projects

Three tools, list_projects, create_project and get_project, let the agent list your projects, create one from a starter or an example app, and read a project’s state.

The agent sees only the projects of the manh.run account it signed in with.

list_projects

Lists your projects, newest first.

  • Parameters: none.
  • Returns: one row per project: id, name, publicSite (the <id>.manh.run address), createdAt.
  • When the agent calls it: at the start of a session, to get the id the other tools take.

create_project

Creates a project from a starter, or copies a running example app. The app’s database is created on the first deploy.

  • Parameters:
    • name (required): the project name, 1–60 characters.
    • starter: auth (default) or blank.
    • template: copies the app/ and spec/ of a running example app instead of a starter. The new app’s database starts empty. Pick by the kind of app, not the trade: crm (sales pipeline), kho-ban-hang (selling from stock), sua-chua (intake, quote, repair, hand-back), duyet (requests through approval levels), booking (time slots), qr-order (ordering at the table by QR code).
    • region: where the database lives: asia_pacific (default), north_america_east, north_america_west, europe_west, europe_east, oceania. Fixed after the first deploy.
  • Returns: id (also the app’s subdomain; it never changes), the starter or template used, the file list, the addresses (publicSite, workspace) and a next step. Without a template it adds two planning hints: staff screens built with the resource block, and how to build a public website with the web block.
  • When the agent calls it: when you ask for a new app.

The auth starter ships email and password sign-in and sign-up, a Google sign-in button, a users table, a users admin screen, an app frame with a role-based menu and a theme. Roles are declared in app/auth.ts. The blank starter is one page, for public single-screen tools.

get_project

Reads everything the agent needs to know about a project.

  • Parameters: project.
  • Returns:
    • idea: what you typed when you created the project in the dashboard (null if nothing).
    • urls: publicSite with publicSiteShows, which says whether that address shows the deployed app or a preview; api after the first deploy; workspace, your dashboard page, not for app users.
    • deployed, lastDeployedAt, fileCount, checkpoints, the blocks added.
    • auth: roles, the default role, whether sign-up is open, the sign-in methods.
    • routes: every API route, who may call it (public, user or a list of roles) and the file it comes from.
    • npmPackages: pinned npm packages; domain and telegram when connected.
    • handover: what still shows the platform’s name before you hand the app to your client (tab title, page text, e-mail sender…), each with a status and a hint.
    • progress and next: what is left to do.
  • When the agent calls it: when it picks up an existing project, and after each phase to see what is missing.

Next steps

Last updated