GitOps sync for Skills & Agent configurations with GitHub Action

🎯 What is it?

We've released a new official GitHub Action called dust-github-action that lets you manage your Dust Skills and Agent configurations directly from your Git repository. You can now version-control your Dust setup, review changes through pull requests, and automatically sync your workspace from CI/CD pipelines.

💡 Why is it useful?

Managing Dust configurations through code gives you the same benefits you already get with your application code: change history, peer review, rollback capabilities, and automation. Instead of manually updating agents and skills in the Dust interface, you can define them in your repository and let your CI pipeline keep everything in sync. This is particularly valuable for teams that want to maintain consistency across workspaces, review configuration changes before deployment, or integrate Dust setup into their existing development workflows.

⚙ How does it work?

The GitHub Action provides methods to "upsert" (create or update) Skills and Agent configurations from your repository into your Dust workspace. When you push changes to your repo or merge a PR, the action automatically applies those configuration changes to your workspace.

✨ Concrete Use Cases

Here's how you could use it:

Development workflow: Define your agents in YAML files in your repo, have teammates review changes in pull requests, then automatically deploy approved configurations to your production Dust workspace when merged to main.

Multi-workspace management: Maintain a single source of truth for your agent configurations and sync them across development, staging, and production Dust workspaces using different GitHub Actions workflows.

Audit & rollback: Track every change to your Dust setup in Git history, see who made what changes and why, and easily roll back to previous configurations if needed.

📈 Benefits for you

• Better collaboration: Review agent and skill changes through pull requests before they go live

• Version control: Full history of all configuration changes with the ability to roll back

• Automation: Reduce manual work by syncing configurations automatically from CI

• Consistency: Keep multiple workspaces aligned using the same configuration source

• Integration: Fits into your existing development workflows and tooling

🚀 How to access it?

The GitHub Action is available now for all workspace admins and developers using GitHub Actions. Check out the repository and documentation to get started: https://github.com/dust-tt/dust-github-action

The feature is in General Availability (GA) and ready for production use.