About coded app projects

Coded app project architecture in Studio Web, covering how Studio Web and your local IDE split responsibilities and which files matter at each stage.

A coded app project in Studio Web is a pro-code project that lives inside a solution. Studio Web owns the project's identity and its publish lifecycle. The app's source code is written in your own local project and pushed into Studio Web with the UiPath CLI.

What Studio Web owns and what your IDE owns

Concern	Owned by Studio Web	Owned by your local IDE
Project identity inside the solution	✅	—
webAppManifest.json (project type and configuration)	✅	—
Registering bindings from the pushed bindings_v2.json	✅	—
Solution-level publish and deploy	✅	—
Read-only view of the last pushed source	✅	—
Source-code authoring, framework choice, dependencies	—	✅
bindings_v2.json — declaring which Orchestrator resources the app uses	—	✅
Local dev server, previewing the running app, debugging	—	✅

Files that matter

After initializing the project in Studio Web

Studio Web creates a single file:

Archivo	Propósito
webAppManifest.json	Describes the project's type (Coded) and configuration. Owned by Studio Web — you don't edit it directly.

Ejemplo:

{
  "type": "Coded",
  "solutionResourceSubType": "CodedAction",
  "config": {
    "isCompiled": true,
    "isActionApp": true
  }
}

In your local project (what you build and push)

Your local project is whatever your framework of choice produces. Studio Web does not require a specific folder structure; only what you push is stored.

If the app needs UiPath resources at runtime, a bindings_v2.json file at the root of what you push declares those resources. Studio Web reads this file on push and registers each declared resource — see Bindings and runtime resources.

Where to go next

Find out more about working with coded app projects:

• Initializing a coded app project
• Working in your IDE
• Bindings and runtime resources
• Publishing and deploying coded app projects