November¶
In November 2026, the Developer Environment lets administrators regenerate the organization's key (API key) on their own, with a confirmation flow that warns about the impact on bots and records the action in Audit.
BotCity Insights gets a new Dashboard, focused on showing how the strategic results of your automation initiative evolve over time.
The Organization gets Cost Center management: Runners can now be linked to one or more repositories, and the new Resource Allocation screen shows how Runners and automations are distributed among them.
The Integration Hub gets the MCP Server, which connects AI assistants to your organization's data on the BotCity Platform.
BeaPro is BotCity's template for building automations from a production-ready structure.
Developer Environment¶
The Developer Environment screen gets the product's new visual style and the Generate new key button, which lets you regenerate the organization's (API key) without having to contact the BotCity team. The workspace key remains visible in the top panel, regardless of the selected tab.
Impact on Bots¶
When you generate a new key, all bots using the previous key stop working immediately. They only resume operating after the new key is manually applied to each connected Runner.
No automatic key update
For security reasons, the new key is not automatically propagated to the Runners. If the previous key has been compromised, an automatic update would also benefit whoever gained improper access to it. In operations with many bots, evaluate the impact before confirming the action.
See how to update the key on each Runner at:
Full documentation
You can find the details of key regeneration in the documentation:
BotCity Insights¶
The new Insights Dashboard shows how the results of the automation initiative evolve over time:
- Consolidated cards: totals of Total Savings, ROI, Hours Saved and FTE in the period, with a shortcut to the report of each indicator.
- Operation evolution: totals of Automations, Runners, Tasks and Processed items, with the chart of the hyperautomation initiative evolution.
- Charts per indicator: consolidated evolution of each indicator and the 5 automations and 5 repositories with the highest value. ROI now displays negative values.
- Filters: custom period since the start of the account, with no 6-month limit, and automation or repository filters.
Operation evolution and filters
The Operation evolution section only responds to the period filter. When you filter by automation or repository, it shows the Filter not applicable to the chart notice.
Cost Center¶
Repositories can represent the business areas or cost centers of the organization. Now, each Runner can be linked to one or more repositories, being exclusive to one area or shared among several.
- Runners: new Linked repositories field on creation and editing, new Repositories column in the list and new Linked Repositories tab in the Runner details.
- Repositories: new Attached runners field on creation and editing, and new repository information screen.
- Automations: the Linked Runners field shows only the Runners of the automation's repository. Changing the repository is now done by editing the automation.
- Resource Allocation: new screen in Organization with the Runners and automations of each repository and the percentage of the contracted total, with export to CSV and XLSX.
Initial Runner links
So that no automation stops running, all existing Runners were linked to all repositories of the workspace. To separate the execution capacity between areas, review the Runners linked to each repository.
The link does not restrict API calls
The link between Runners and repositories organizes the execution capacity in the platform. It does not restrict the API calls that the Runner makes while executing tasks. The separation of visibility between areas still depends on the workspace groups and permissions.
MCP Server¶
The MCP Server connects AI assistants compatible with the Model Context Protocol (MCP) to the BotCity Platform data. Once connected, you query the platform in natural language, right from your assistant, without opening the Orchestrator or writing API calls.
- Compatible clients: GitHub Copilot (VS Code), Claude Code, Claude Desktop and Cursor.
- Available data: profile and repositories, automations, execution logs, errors, alerts, tasks, FTE and ROI.
- Authentication: OAuth, with login through your own BotCity account. Each person accesses only the data they can already see on the platform.
Full documentation
You can find the configuration for each client, the connection test and the prompt examples in the documentation:
BeaPro Template¶
BeaPro (BotCity Enterprise Automation Process) is BotCity's template for production automations, already used by several customers. With it, you start from a ready-made structure and focus only on the business logic of the automation.
- Ready-made structure: the framework modules live in the
framework/folder, separate from your project files. - Exception handling: business exceptions, system exceptions and interrupt requests are handled automatically, with a restart in case of a system failure.
- Orchestrator integration: logging, error reporting with screenshots, upload of result files and task completion in the BotCity Orchestrator.
- Data sources: support for CSV files and the BotCity Datapool.
To use it, create a new project from the beapro-framework template, available on BotCity's GitHub.
Getting started
You can find the installation and setup steps in the documentation: