UiPath Documentation
getting-started
latest
false
Getting started developer guide
  • Introduction
    • Overview
    • Environment set up
  • Getting Started with UiPath Agents
  • Getting Started with UiPath Agents using LangGraph
    • Introduction
    • Set up your environment
    • Build the agent
    • Add a tool
    • Evaluate the agent
    • Connect to Studio Web
  • Building a Low-Code Agent in Studio Web
  • Adding Tools to Your UiPath Agent
  • Getting Started with UiPath Maestro Flow

Connect to Studio Web

Connect your local LangGraph project to UiPath Studio Web and push your first version.

With local evaluation results confirmed, you are ready to connect the project to Studio Web.

Step 10 - Connect to Studio Web

Your agent is built and evaluated locally. Now connect it to Studio Web so you get version history, evaluation traces, and the ability to test in the cloud UI.

You have three options:

OptionWhat happens
A: You set it up in Studio WebOpen Studio Web, create a Coded Agent project, copy the project ID. You paste it into .env and push from the CLI.
B: CLI packages and uploadsuip codedagent pack, publish, or deploy package the agent and publish it to your personal workspace or tenant feed directly, without Studio Web setup.
C: Local dev server onlyRun uip codedagent dev for a local web UI. Nothing is published to the cloud.

For this lab, use Option A: it shows the connection model that underlies all three options.

Option A - Connect via Studio Web

  1. Log in to UiPath Automation Cloud and select Studio Web from the side navigation.

  2. Select Create New and select Agent.

  3. In the Select agent type dialog box, choose Coded as the agent type and select Start Fresh.

  4. Studio Web displays a Setup your coded agent panel. Under Sync from your IDE into Studio Web, your UIPATH_PROJECT_ID appears with a copy button. Copy this value.

  5. Return to your IDE and open the .env file in your project root to add the project ID:

    UIPATH_PROJECT_ID=your-project-id-here
    UIPATH_PROJECT_ID=your-project-id-here
    
    Note:

    Only the project ID goes in .env. uip login stores your auth token globally; you do not need UIPATH_URL or UIPATH_ACCESS_TOKEN in .env. If you have used the UiPath Python SDK before and are used to running uipath auth to populate those fields, that step is no longer needed.

  6. Add .env to the .gitignore file to avoid committing it:

    echo ".env" >> .gitignore
    echo ".env" >> .gitignore
    
  7. Push your agent to Studio Web from the command line:

    uip codedagent push
    uip codedagent push
    

A successful push returns confirmation and increments the version to 0.0.1. Open your project in Studio Web; the agent definition, your evaluation sets, and version 0.0.1 appear in the version history.


Step 11 - Iterate and improve (optional)

With evaluations in place and Studio Web connected, you can iterate on your agent and observe the effect on scores:

  1. Review evaluation results in eval-results.json or in Studio Web.
  2. Ask your coding agent to improve the agent based on the evaluation feedback.
  3. Re-run evaluations to verify improvements.
  4. Push the updated version to Studio Web.
uip codedagent eval agent evaluations/eval-sets/smoke-test.json --workers 3
uip codedagent eval agent evaluations/eval-sets/smoke-test.json --workers 3
uip codedagent push
uip codedagent push

Each push increments the version in Studio Web, giving you a full history of how the agent evolved.


What you built

You have built a LangGraph agent on UiPath using the CLI and coding agent skills:

  • Scaffolded a local Python project with the correct LangGraph structure using uip codedagent new.
  • Used your coding agent to build the agent logic, guided by UiPath skills, not detailed prompts.
  • Ran the agent locally and verified outputs before touching the cloud.
  • Gave the agent a tool to verify its own answer against a live external API.
  • Created an evaluation set, including a trajectory check on tool use, and scored the agent locally.
  • Connected to Studio Web and pushed the first version with full evaluation history.

What's next

  • Step 10 - Connect to Studio Web
  • Option A - Connect via Studio Web
  • Step 11 - Iterate and improve (optional)
  • What you built
  • What's next

Was this page helpful?

Connect

Need help? Support

Want to learn? UiPath Academy

Have questions? UiPath Forum

Stay updated