OnimatorOnimator
Check price

What is Onimator Bot Folder? The Bot Folder is the file-system directory that a specific Onimator installation uses to store everything the installation needs to persist between sessions — device registrations, per-account configurations, session histories, session queues, target lists, scheduled posts, tag structures, and every other piece of operational state the bot depends on. It is the single load-bearing data location for the installation, and it is the specific reference point every OniHelper Suite tool takes as input when it needs to read or write against the installation’s accounts. When an operator points Tag Manager, Time Manager, Post Scheduler, or any other OniHelper module at their Onimator installation, what they’re actually pointing at is the Bot Folder, and the Suite’s ability to perform bulk operations depends entirely on being pointed at the correct folder path.

What Lives in the Bot Folder

The Bot Folder contains the complete operational state of the installation. Device registrations — which physical phones, emulators, or cloud phones the installation has been configured to run against — live at the top level of the folder structure, each device with its own subfolder containing the accounts registered on that device. Per-account configurations — action limits, timing ranges, target lists, warm-up settings, tag assignments, and the specific per-tool settings each account has — live inside each account’s dedicated location within its device folder.

Beyond the configuration data, the folder holds operational state that persists across sessions: session logs recording what each account did in past runs, scheduled post queues waiting for their publish times, target lists that Follow and Engage tools work through, tag structures that Tag Manager wrote and downstream tools read, and analytics data that Stats Analyzer aggregates for reporting. All of this data lives in the Bot Folder rather than in the Onimator application binary, which is what makes the folder portable — an operator moving to a new PC can copy the Bot Folder and preserve everything about their setup without reconfiguring from scratch.

How Bot Folder Enables Cross-Tool Coordination

The specific architectural advantage of centralizing operational state in the Bot Folder is that every tool in the Onimator ecosystem can operate against the same data without requiring inter-tool communication. When Tag Manager applies tags to a set of accounts, it writes the tag data into the Bot Folder’s account configurations. When the Engage Tool later runs and checks whether an account shares tags with another account for cross-account deduplication, it reads the tag data from the same Bot Folder. No synchronization step is needed because both tools read and write to the same underlying data location.

The same pattern applies across every OniHelper Suite tool. Time Manager writes calculated schedules into the Bot Folder’s per-account Timer Tab fields. The core Onimator execution engine reads those Timer Tab fields when deciding when to run sessions. Clone Detector writes app-cloning assignments into the Bot Folder’s device configurations. The core execution engine reads those assignments to know which cloned Instagram instance to open for each account. Every cross-tool coordination happens through the shared Bot Folder rather than through explicit inter-tool APIs.

Why “Select Bot Folder First” Is the Universal Rule

Every OniHelper Suite tool requires the Bot Folder to be selected before it can populate its device and account lists. This is the universal rule across the Suite: click Select Bot Folder, point at the correct installation path, then work with the tool. The specific reason is that without the folder path, the tool has no data source to read from and no target to write to — every operation the tool performs is fundamentally an operation against the Bot Folder’s contents.

The most common operator error is running an OniHelper tool without selecting the Bot Folder first (in which case device and account panes stay empty), or selecting the wrong Bot Folder (in which case operations happen against accounts the operator didn’t intend to modify). Both errors produce confusing outcomes that trace back to the specific Bot Folder path each tool is pointed at.

The Suite’s shared header includes a Select Bot Folder button that sets the default folder for all tools in the current session. Individual tools that operate on non-default installations (like the Threads Manager tab, which typically points at a different installation than the Suite’s default) expose their own Select Bot Folder button within the tab to override the default for that tool specifically.

Multi-Installation Considerations

Some operator configurations involve multiple Bot Folders. The most common case is running IGBot alongside the Threads bot on the same device fleet — IGBot has its own Bot Folder for Instagram accounts, and the Threads bot has its own Bot Folder for Threads accounts. Coordination between the two (through the Threads Manager’s Avoid Conflicts with Instagram Accounts on Same Device option) requires specifying the correct IGBOT Folder path in the Threads Manager configuration so it can read Instagram schedules from the right location.

Agencies running separate installations for separate client operations maintain a Bot Folder per client, and the operator switches between them by re-pointing OniHelper Suite tools at the appropriate folder when working with each client’s accounts. This isolation prevents accidental cross-client operations (tagging one client’s accounts with another client’s tags, scheduling posts to the wrong account fleet) that would produce operational chaos if all installations shared a single folder.

Testing versus production installations follow the same pattern. Some operators maintain a separate Bot Folder for testing new configurations before pushing them to the production installation, which lets them validate changes without risking production account safety. The separation lives at the folder level; the operator’s workflow involves consciously switching folder targets when moving between test and production work.

Backup and Migration

The Bot Folder is portable — copying the folder to a new location, PC, or backup destination preserves the complete state of the installation at the moment of copy. Restoring from backup involves pointing the Onimator installation at the restored folder location and letting the installation pick up where the folder’s data left off.

The specific implication is that operator backup workflows should focus on Bot Folder backup rather than on backing up the application binary itself. Losing the application binary is trivial to recover from (reinstall the software); losing the Bot Folder loses every device registration, account configuration, session history, and target list the installation had accumulated, which can represent months of operational work if not backed up.

Well-configured operator setups back up the Bot Folder on a regular schedule (daily or weekly), store the backups on separate storage from the working folder (external drive, cloud storage, network attached storage), and test the backup recovery process periodically to confirm that restoration actually works when needed. Skipping this discipline produces the specific catastrophic loss case where a drive failure or accidental deletion destroys the operational state that would take weeks to rebuild.

Where Bot Folder Sits in the Onimator Architecture

The Bot Folder is the specific persistence layer that makes every other part of the Onimator architecture work. The core execution engine reads its runtime configuration from the folder. OniHelper Suite tools operate against the folder for all bulk operations. Sibling bot installations reference the folder when coordinating shared-device schedules. Backup, migration, and multi-installation workflows all happen at the folder level.

Understanding the Bot Folder as the load-bearing data location — rather than as an implementation detail — matters for operators specifically because most operational problems trace back to either wrong-folder selection (working against the wrong installation) or folder corruption/loss (losing operational state that lived only in the folder). Both categories of problem are preventable through the specific practices of always checking the current folder selection before running bulk operations and backing up the folder regularly.

Why It Matters for Automation

The Bot Folder is the specific mechanism that makes Onimator’s split-tool architecture practical. Without a shared persistence layer, coordinating operations across the core Onimator execution engine, the OniHelper Suite’s fleet-management tools, and sibling bot installations would require an explicit inter-process API that would add architectural complexity without providing benefits over the folder-based shared-state approach. With the Bot Folder as the shared reference point, every tool operates against the same underlying data without needing to know about the other tools, which is what lets each tool stay focused on its specific job rather than having to handle cross-tool coordination itself.

Related Terms