- Renamed variables in the `App` module to improve code readability, changing `mcpPatchTree` to `_mcpPatchTree` and `cachedServerInfo` to `_cachedServerInfo`.
- Updated the `.gitignore` file to ignore all Atlas log/build artifacts by changing the entry to `**/.atlas/`, ensuring a cleaner repository.
- Introduced the `time` crate to generate session log filenames in UTC format, enhancing log file naming consistency.
- Refactored the logging setup to create log files based on the generated filenames, improving the clarity of log management.
- Updated the `compress_old_logs` function to streamline log file handling, ensuring proper cleanup of old logs.
These changes aim to improve the logging system's functionality and maintainability within the application.
- Updated log messages across `ApiContext`, `ServeSession`, `Reconciler`, and `App` to use consistent formatting for timing information, replacing placeholder syntax with `string.format` for improved clarity.
- Enhanced trace logs to provide more precise execution time measurements during various operations, including connection, reading, writing, and patch application processes.
These changes aim to standardize logging practices and improve the readability of timing information in the application.
- Added timing logs to various functions in `ApiContext`, `ServeSession`, and `Reconciler` to track performance and improve debugging.
- Introduced detailed trace logs for connection, reading, writing, and patch application processes, providing insights into execution times.
- Updated the `App` component to log the patch tree building process, enhancing visibility during session startup.
These changes aim to improve performance monitoring and facilitate troubleshooting within the application.
- Modified the `parse_roblox_log` function to prepend "[Studio]" to all log messages, enhancing clarity and consistency in log output.
- Updated corresponding unit tests to reflect the new message format, ensuring accurate validation of log parsing behavior.
These changes aim to improve the readability and organization of log messages within the application.
- Eliminated the `tracing-log` crate from `Cargo.toml` and `Cargo.lock`, streamlining the logging configuration.
- Updated the logging initialization function to remove the `tracing_log::LogTracer::init()` call, simplifying the logging setup process.
These changes aim to enhance the logging system by reducing unnecessary dependencies and improving code clarity.
- Introduced a logging system using `tracing` and related crates to improve log management and output formatting.
- Updated `.gitignore` to include the `.atlas/` directory, ensuring that log files and other generated content are not tracked by Git.
- Enhanced project templates to include the new `.gitignore` settings for Atlas in various project types.
These changes aim to improve logging capabilities and maintain a cleaner repository by ignoring unnecessary files.
- Added `schemars` and related dependencies to `Cargo.toml` and `Cargo.lock` for enhanced JSON schema support.
- Updated the `mcp.rs` file to utilize `schemars` for generating JSON schemas for various tool arguments, improving API documentation and validation.
- Enhanced the TODO list to reflect new tasks related to schema documentation and potential improvements in input validation.
These changes aim to improve the overall functionality and usability of the MCP integration by providing better schema definitions for tool arguments.
- Introduced new MCP tools for executing Luau code, inserting models, and retrieving console output, enhancing the plugin's capabilities for user interaction.
- Implemented a logging system to capture console output and provide detailed feedback during code execution and play mode operations.
- Updated the MCP stream to handle passthrough commands, allowing for better integration of tool commands and improved error handling.
- Enhanced the TODO list to reflect new tasks related to documentation for the added MCP tools and logging features.
These changes aim to improve the overall functionality and user experience of the MCP integration, particularly in script execution and model management.
- Introduced a new `get_script` command to allow agents to read script source code directly from Roblox Studio, enhancing conflict resolution during sync operations.
- Updated the MCP stream handling to support the new command, including error handling for missing or invalid parameters.
- Enhanced the App component to manage the `get_script` command and its response, ensuring proper integration with the existing MCP functionality.
- Updated the TODO list to reflect the addition of the `get_script` command and its associated documentation requirements.
These changes aim to improve the overall functionality and user experience of the MCP integration, particularly in script management.
- Updated the TODO list to include a task for ensuring well-formed MCP route documentation, enhancing agent usability.
- Modified the MCP stream handling to support additional parameters for sync commands, including mode and overrides for better control during sync operations.
- Introduced a new function to enrich sync changes with filesystem paths, improving traceability of changes.
- Updated API documentation to reflect new sync modes and override capabilities, providing clearer guidance for users.
These changes aim to improve the overall functionality and user experience of the MCP integration and sync process.
- Removed outdated tasks related to syncback optimizations from the TODO list to streamline focus on current priorities.
- Added a new task to create an agent loop for benchmarking plugin and Rust side performance, aiming to identify and resolve sync slowness.
These changes aim to enhance project tracking and improve sync efficiency.
- Expanded the TODO list with new tasks related to MCP modes, including standard, manual, fastfail, and dryrun options for better user control during sync operations.
- Introduced a new `get_script` command to allow agents to read scripts directly from Roblox Studio, facilitating conflict resolution during sync.
- Implemented a `GitIndexCache` to optimize file writes by skipping unchanged files based on blob SHA1 comparisons, improving syncback efficiency.
- Added logging for agent connections and commands to enhance traceability and debugging capabilities.
These changes aim to improve the overall functionality and performance of the MCP integration and syncback process.
- Added place ID validation in the MCP stream connection to ensure only whitelisted IDs are accepted, improving security and control over connections.
- Updated the PluginConfig structure to include an optional place ID field, allowing for better configuration management.
- Refined the TODO list to include new tasks related to hash-based comparisons and terminal command execution, enhancing project tracking.
These changes aim to strengthen the MCP integration and improve the overall functionality of the plugin.
- Added a new section in the README to document the integration of MCP (Model Context Protocol) for AI agents, detailing how to set up and use the `atlas_sync` tool.
- Introduced `McpStream` to manage WebSocket connections for real-time sync commands between the plugin and the MCP server.
- Enhanced the `App` component to initialize and manage the MCP stream, including handling sync commands and user confirmations.
- Updated the API to support WebSocket upgrades for the MCP stream, allowing for efficient communication with connected plugins.
- Improved the handling of sync commands, ensuring proper responses based on the current connection state and user selections.
These changes aim to facilitate programmatic syncs to Roblox Studio, improving the workflow for teams using AI agents.
- Added new dependencies in `Cargo.lock` and updated `Cargo.toml` to include `gix` for improved git functionality.
- Refactored git-related functions to utilize the `gix` library, enhancing performance and reliability in handling git operations.
- Simplified the process of initializing git repositories and committing changes within the CLI commands.
- Updated tests to reflect changes in git integration and ensure proper functionality.
These changes aim to modernize the git handling in the project and improve overall code quality.
- Updated several dependencies in `Cargo.lock` and `Cargo.toml`, including `anyhow`, `tempfile`, `clap`, and others to their latest versions for improved functionality and security.
- Introduced a new `CompletionsCommand` in the CLI to support shell completions, enhancing user experience by allowing users to generate command completions for various shells.
These changes aim to keep the project dependencies up-to-date and improve the command-line interface usability.
- Introduced a new function `getGitMetadata` in `ApiContext` to fetch current git metadata, including new file IDs.
- Updated the `PatchTree.build` function to handle new file IDs, allowing for better differentiation between tracked and untracked files during patch processing.
- Modified the `git_changed_files` function to return both tracked and untracked files, improving accuracy in change detection.
- Enhanced the `App` component to debounce git metadata refreshes, ensuring the UI reflects the latest changes without unnecessary calls.
These changes aim to improve the integration with git and enhance the accuracy of change detection in the application.
- Modified the button style in the Confirming page to dynamically switch between "Primary" and "Neutral" based on whether all items are selected, enhancing visual feedback for users.
This change aims to improve user experience by providing clearer indications of the current selection state.
- Introduced a new function to retrieve the current HEAD commit SHA, allowing for better tracking of changes in the git repository.
- Updated the `git_changed_files` function to accept an initial HEAD parameter, improving the accuracy of change detection.
- Modified `ServeSession` to store the initial HEAD commit SHA at session start, ensuring committed changes are reflected in the auto-selection logic.
- Enhanced tests to verify that committed changes after session start are correctly identified and included in the change tracking.
These changes aim to improve the synchronization process with git and enhance the user experience by ensuring accurate change detection.
- Removed outdated tasks from the TODO list related to one-shot mode changes, streamlining focus on current issues.
- Enhanced the selection logic in the Confirming page to prevent auto-selection of new items when changes are detected, improving user experience during updates.
These changes aim to clarify task management and enhance the handling of user selections in the application.
- Updated the TODO list to clarify tasks related to auto-selection and one-shot synchronization, ensuring better tracking of issues.
- Introduced a new flag `__oneShotSyncDone` in `ServeSession` to manage synchronization state, preventing further message processing after a one-shot sync is completed.
- Improved the handling of incoming changes during the patch visualizer, ensuring user selections are appropriately managed.
These changes aim to streamline synchronization processes and enhance user experience during patch management.
- Improved the syncback functionality by detecting unchanged output file hashes to avoid unnecessary writes, optimizing performance for larger projects.
- Updated the patch selection logic to ensure that auto-selection only occurs when the current selection matches the default, enhancing user experience during patch reviews.
These changes aim to streamline file synchronization and improve the clarity of patch management in the application.
- Updated the TODO list to consolidate and clarify tasks, removing outdated entries while retaining relevant ones.
- Enhanced the slugification logic to treat "init" and its case variations as reserved names, ensuring they are properly suffixed with an underscore.
- Added tests to verify the slugification behavior for reserved names, improving code reliability.
These changes aim to streamline task management and ensure consistent handling of reserved names in the application.
- Added support for right-click events in the PatchVisualizer component, allowing users to unselect nodes and manage subtree selections more intuitively.
- Updated the TODO list to remove outdated tasks related to the change visualizer, streamlining focus on current issues.
These changes aim to improve user interaction and simplify task management within the application.
- Introduced a new function `wait_until_all_staged` that polls for all specified files to be staged with exponential backoff, enhancing reliability in tests.
- Replaced direct assertions for file staging with calls to `wait_until_all_staged` in multiple test cases, improving test robustness and reducing reliance on fixed sleep durations.
These changes aim to ensure that all files are properly staged before proceeding with assertions, enhancing the accuracy of the tests.
- Implemented logic to insert script references into the tree when a snapshot of a script class is processed.
- Enhanced the existing snapshot insertion method to ensure proper tracking of script instances.
These changes aim to improve the management of script references within the RojoTree structure.
- Added a fallback mechanism in the `__applyPatch` method to handle errors during patch application, logging warnings for any encountered issues.
- Improved the transitive closure logic in the `__connectScriptsOnlyWatchers` method to ensure all necessary temporary IDs are included as skeleton containers, enhancing the integrity of the synchronization process.
These changes aim to improve error resilience and ensure proper handling of script references in scripts-only mode.
- Moved the `is_script_class` function to the `snapshot` module for better organization and reusability.
- Updated imports in `git.rs` and `ref_properties.rs` to reflect the new location of `is_script_class`, enhancing code clarity and maintainability.
These changes aim to streamline script class management and improve the overall structure of the codebase.
- Introduced a new flag `__applyingPatch` to track the patch application state, preventing `DescendantAdded` events during reconciliation.
- Updated the `__applyPatch` method to set and clear the `__applyingPatch` flag appropriately, enhancing control over script updates.
- Added checks in the `__connectScriptsOnlyWatchers` method to avoid processing during patch application.
These changes aim to improve the reliability of script handling during patch operations and prevent unintended side effects.
- Optimized scripts-only mode by implementing a server-side script index for efficient reads and added a `syncScriptsOnly` flag to streamline synchronization.
- Fixed WebSocket ancestor injection to ensure new scripts in pruned subtrees are sent with their full ancestor chain.
- Introduced `DescendantAdded` watchers to detect new scripts created in Studio and send them to the server with appropriate containers.
These changes aim to improve performance and reliability in scripts-only mode.
- Added a test to verify the functionality of script tracking updates in RojoTree, ensuring proper addition and removal of script references.
- Improved error handling in ServeSession by clearing temporary script IDs upon disconnection to prevent potential memory leaks.
- Updated API logic to filter out empty properties and children during instance addition, enhancing the integrity of the synchronization process.
These changes aim to optimize script management and enhance the robustness of the session handling and tree operations.
- Removed outdated tasks related to scripts-only mode from the TODO list to streamline focus on current issues.
- Enhanced the remove method in RojoTree to prevent unnecessary operations when an ID does not exist.
- Improved error handling in the remove_metadata function to gracefully handle missing metadata.
These changes aim to optimize task management and enhance the robustness of the RojoTree implementation.
- Added detailed error messages related to Rojo crashes and two-way sync operations in the TODO list.
- Included specific instances of removed references during synchronization to aid in debugging.
- Highlighted the need to address the Rojo bug and suggested filing an issue for further investigation.
These updates aim to enhance error tracking and improve the management of synchronization tasks.
- Introduced a new mechanism in ServeSession to manage scripts-only mode, ensuring proper handling of temporary IDs during script additions.
- Updated the applyPatch function to remap only scripts-only temp IDs, preventing false positives with legitimate additions.
- Modified the API to resolve intermediate container temp IDs to real tree references, enhancing the integrity of parent-child relationships for new scripts.
- Added tests to verify the functionality of scripts-only mode and the resolution of temp IDs.
These changes aim to optimize script management and improve the overall functionality of the session handling.
- Enhanced error logging in ServeSession by formatting warning messages for better clarity.
- Improved readability in applyPatch by restructuring conditional statements for clarity.
- Simplified assertions in tests for script pruning to maintain consistency and readability.
These changes aim to improve code maintainability and enhance the clarity of error messages.
- Improved error handling in ServeSession by rolling back temp IDs if encoding fails for new scripts.
- Added logic in applyPatch to remap echoed additions from the DescendantAdded handler, preventing duplicate instances.
- Updated API to resolve intermediate container temp IDs to real tree references, ensuring proper parent-child relationships for new scripts.
- Introduced new tests to verify the presence of server info flags and the resolution of temp IDs in scripts-only mode.
These changes aim to optimize script management and enhance the overall functionality of the session handling.
- Updated the TODO list to refine tasks related to sync performance in scripts only mode, emphasizing the need to prune non-script leaves.
- Enhanced the sourcemap command to handle non-terminal stdin during watch mode, allowing for graceful exit when stdin is closed.
These changes aim to improve project management and optimize the sourcemap functionality.
- Added tasks to investigate Tree reconciliation issues and improve sync performance in scripts only mode.
- Updated the project template to include ignore paths for ServerStorage/RBX_ANIMSAVES and MoonAnimator2Saves, enhancing version control practices.
These updates aim to streamline project management and optimize synchronization processes.
- Added a task to address the issue of unchanged commits in Git by suggesting the inclusion of the last Git hash.
- Included a note to add ServerStorage/RBX_ANIMSAVES to the ignore list.
These updates aim to improve task management and enhance the project's version control practices.
- Changed the format on save setting from true to false for both Lua and Luau in the VSCode configuration.
- Adjusted the editor ruler to maintain a consistent column width of 100.
These updates aim to refine formatting behavior and align with project preferences.
- Changed the editor ruler and stylua column width from 80 to 100 to accommodate wider code formatting.
These updates aim to improve code readability and align formatting preferences across the project.
- Added detailed tasks for implementing Atlas sync, including conditions for automatic acceptance and handling of connected-mode operations.
- Emphasized the need for the agent to await sync completion to ensure state integrity.
These updates aim to enhance the project's synchronization capabilities and improve task management.
- Added tasks for setting up a nightly build and suffixing the version for beta releases under the versioning section.
- Included a note on improving property diffs and merging support in the merging section.
These updates aim to enhance project management and development workflow.
- Added default formatter and enabled format on save for Lua and Luau in the VSCode settings for both the main project and the project template.
These changes aim to improve code formatting consistency and streamline the development workflow.
