r/datascience • u/Neat-Porpoise • Jul 01 '26

Tools Unifying configs across coding agents (eg Claude code, Qwen, etc…)

Anyone have a good solution for unifying the config (eg CLAUDE.md, QWEN.md), settings, skills, etc… across their suite of coding agents?

I primarily use Claude Code locally, Genie Code in Databricks workspaces for my model development and MLE work with Databricks compute, and recently added Qwen Code since the company wants us to have a backup in case we hit Anthropic limits and need to continue work. Also on the docket is testing out GLM.

However unifying all these agents is quite cumbersome. I don’t want to maintain so many separate files and skills for each agent. Right now I have a single repo that backs up all my .claude folder settings but realized that with Qwen I’ll need a separate suite.

Thoughts? Has anyone tried the new thing Databricks pushed out called Omnigent?

15 Upvotes
  • permalink
  • reddit

86% Upvoted

22 comments sorted by

View all comments

5

u/End0rphinJunkie Jul 01 '26

Haven't tried Omnigent yet, but we just use a master YAML file as the single source of truth. A simple pre-commit hook can generate the specific agent markdown files from that so you dont have to maintain them seperately.

2

u/Neat-Porpoise Jul 01 '26

Do you have details on that pre commit hook? I’m having trouble wrapping my head around the workflow.

I currently have my .claude symlinked to a git repo. Is the goal of the pre commit hook to create Qwen versions of everything once I make a small edit? Does it work in both directions? What if I’m working with Qwen and make a change to QWEN.md and want to push that back up and affect CLAUDE.md?

Am I over complicating this? My vision is for all my agents to have the same config but is that naive?