Make updating a project less painful

[yluom]

AgentOS Update Process Feedback

Hello,

I appreciate the rapid iteration and deployment pace—it's great to see continuous improvements!

However, AgentOS updates are currently somewhat challenging to manage.

Commands and Workflow Changes

I'm working to set up AgentOS for my team, but the frequent changes require me to regularly inform them about modifications to commands and workflows.

While the core concepts remain stable, the implementation details shift often.

Customizations Lost After Updates

To effectively use AgentOS on a large legacy project, I need to extensively customize the default tech stack, agents/skills.
The issue is that updates overwrite all customizations. While I could exclude certain files from updates, I want to stay current with the latest AgentOS version.

Example: Removing Frontend Components

A significant customization I make is removing all frontend-related content from AgentOS, as my application is backend-only. This helps preserve context. After each update, I must re-apply these frontend removals across all files (using Claude Code, naturally).

Example: Tech Stack Configuration

When upgrading a project, the existing global/tech-stack.md file is deleted and replaced with the generic template version requiring manual completion.

Suggestion

Would you consider leveraging Claude Code's capabilities to implement a smarter update mechanism that retrieves the latest AgentOS files while intelligently merging existing customizations ?
Thanks !