Pilely
LMCD v1.0.2
Build and publish web apps
From the developer
Declared limitations
- Asking for an app with a backend server. Apps built from a chat with Pilely are frontend-only; a backend has to be built with Pam, Pilely's assistant on the user's computer. Expected: no backend is created; the reply says plainly that a backend cannot be built from a chat and offers to move the app to the user's computer, where Pam carries on with it (a frontend-only version may still be offered).
- Changing an existing app's access mode. Access mode is set when an app is created and cannot be changed afterwards. Expected: nothing is changed; the reply says the access mode is fixed at creation and offers to create a new private app instead.
- Unrelated request. Not about building or publishing a Pilely app. Expected: no Pilely tool is called.
Not specified in the available declarations: capabilities, pricing & account requirements.
Onboarding example
Make me a tip calculator app on Pilely and publish it.
Sources & dates
Developer declarations; not independently tested. Listing last checked Nov 17, 2026. Package observed Nov 17, 2026.
Description
From the marketplace listing
Pilely lets you build a web app from a chat and publish it at its own address on pilely.app, with no local tools. What you can do: - Create a new app from a starter project, or pick one of your existing apps. - List, read, write, edit and delete the app's source files. - Build and publish the app. Publishing makes the new version live at https://<your-app>.pilely.app and replaces the version that was live before. - Check the build: its progress, and on failure the step that failed and the end of the build log. - Set up the Pilely services your app uses: its database tables, user groups, rate limits and email account. The connector reads each service's manual and calls that service's routes as you. Who it is for: anyone who wants to make and ship a small web app, from a phone or a desktop chat. Limits: it works only on apps in your own Pilely account. Files are text, up to 1 MB each. Builds are frontend (Vite) builds. Service calls reach only four Pilely services (database, groups, rate limiter, email) and act with your own permissions; they can create, change or delete that service's data, and never send email. Publishing and deleting files change what is live or stored and cannot be undone by the connector.
Language: English · Automatically detected from descriptions.
Changes
No changes recorded yet. Follow this plugin to keep track of future changes.
First seen Nov 17, 2026. Last seen Nov 17, 2026.
Similar plugins
Find competitors to follow as you develop your plugin.
-
Build, edit, test, preview, and publish apps in managed nstantcode cloud projects.
Shared terms: publish, database, publishing, web
-
Akwadra lets users create, inspect, edit, validate, and preview web-app projects from ChatGPT. ChatGPT writes the source files while Akwa...
Shared terms: web, write, project, file
-
Build, test and publish Olbrain AI agents from Codex, with Olbrain's Alchemist builder.
Shared terms: publish, connector, phone, route
-
Edit and publish the apps you built with Setherion, from a chat.
Shared terms: publish, address, database, small
-
Publish the app your agent just built to your team: a private address behind sign-in, with a database, scheduled jobs and email. No serve...
Shared terms: publish, address, anyone, database
Files & skills
File archives
Skill instructions
get-started1.46 KB
--- name: get-started description: How to build and publish a web app on Pilely from this chat — find or create the app, change its files, then build and publish it. --- # Build and publish a Pilely app 1. Find the app with `list_my_apps`, or make a new one with `create_app` (it starts as a Vite starter project). 2. Look at the files with `list_files` and `read_file`. 3. Change them with `write_files` (whole files) or `edit_file` (one exact replacement). Use `delete_files` only when the user asks to remove files. 4. When the user wants it live, call `build_publish`, then call `get_build` until the state is `live` or `failed`. - `live`: give the user the URL. - `failed`: read `failed_step`, `error` and `log_tail`, fix the files, and publish again. The previous live version stays up. 5. If the app needs a database, groups, rate limits or email, read that service's manual with `read_service_api_doc` first, then call its routes: `read_service_data` for a route that only reads (its last path segment is `list`, `get`, `info`, `search`, `resolve`, `lookup` or `download`), `write_service_data` for every other route. Publishing replaces the live version at `https://<app>.pilely.app`. Confirm with the user before publishing or deleting files. Pilely's full step-by-step guide to building, publishing and moving an app with these tools — talking the app through, the app's note, setting up its services, writing the code — is available from `get_app_workflow_instruction`.
Release notes
Initial release: create, edit, build and publish Pilely web apps, and set up their Pilely services, from ChatGPT.
Declared in the saved package. Remote tools may change independently.
Package details
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
- Package author
- LMCD
- Getting started skill
- ./skills/get-started/SKILL.md
- Commerce declaration
- Does not support commerceThis does not establish whether access is free or paid.
- Review scenarios
- 5 positive · 3 negativeScenario counts, not test results.
Package observed Nov 17, 2026.
Technical details
- First seen
- Nov 17, 2026 · 18:00 UTC
- Last seen
- Nov 17, 2026 · 18:00 UTC
- Collection status
- Collected
plugin_asdk_app_6ae959af375081919629d50620bd128b
Download plugin data (JSON)Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.