Recently I noticed the new built-in terminal in UiPath Studio and, like any curious developer, I started experimenting with it.
What started as a quick look turned into a full exploration. Here are a few things I tried:
• Running Git commands directly from the terminal
• Using AI tools like Gemini CLI to fix and generate workflows
• Creating XAML workflows using AI prompts
• Auto-generating annotations and documentation for workflows
• Experimenting with agent projects using UiPath LangGraph
• And… running a game of Tetris & Snake in the terminal
The terminal opens up some interesting possibilities for combining AI tools, developer workflows, and automation development all in one place.
Hello @AJ_Ask, taking a look at your article and you said that you weren’t able, understandably, test with Claude due to the cost. I wanted to know if Claude CLI in the UiPath terminal is using/billing Claude through you’re own account (AWS, Dexter…) or through a UiPath managed account? Are the tokens being used based on your own personal setup or if they are through UiPath managed tokens? Did you have to connect the LLM in the AI Trust Layer via a connect for example?
The UiPath Studio terminal behaves just like any other terminal you can invoke different CLI tools directly. When you run a CLI for the first time, it asks you to sign in with the account you want to use (personal or corporate). In my case, I used my gmail account for gemini cli, so the usage and billing are tied to my own account, not UiPath. With Codex and Gemini CLI, you get some free tokens to get started, but that’s not the case with Claude. I didn’t configure the AI Trust Layer either, as the CLI authenticates directly with the provider.
If you have a Claude Pro subscription, you can simply sign in with that account. The first time you run Claude CLI, it opens your browser and prompts you to log in with your account credentials. Once authenticated, the CLI uses your own account, so the usage and billing are tied to your Anthropic subscription, not UiPath.
