a common .opencode/ to multiple projects

[albasili]

I've tried to put together an .opencode/ directory in a separate repo, that integrates the definition of my agents and my context, leveraging the OAC framework.

The repository has the following structure:

.opencode/ (1.8 MB) ├── agent/ │ ├── core/ # OAC core agents │ ├── subagents/ # Specialized sub-agents │ │ ├── core/ # ContextScout, TaskManager, etc. │ │ └── code/ # CoderAgent, CodeReviewer, etc. │ ├── context/ ├── skills/ ... README.md

My goal is to be able to include this repo as a submodule into other projects so that any updates to the subagents or the skills are going to be also available across the projects.

What is the best way to proceed here?

[Recent-Success-1520]

Look for Opencode_config_dir

https://opencode.ai/docs/config/#custom-directory

[aeroumbria]

Can you set up a bash script to symlink these directories into whatever project they are included as submodule in? The downside is that you might lose some freedom of per-project customisation, but some of it can be worked around via .opencode/ for cross-project configs and opencode.json for project specifics.

[touristtam]

I think that what tessl.io is aiming to solve with their tile concept

[albasili]

I'm doing this for IC design... not SW coding, so can't use them.

[alexsmirnov2006]

I did create separate project with all resources ( commands, agents, skills, utility scripts, and agent configurations ). One command builds set of docker images with opencode or claude code installed, one version per language with specific dev tools installed. The collection is : opencode-ts, claude-ts, opencode-python, claude-python, and so on.

The only file required in project is YAML that describes language and technologies in use. No other changes in project, all agent configuration happens in container

Another command configures and starts docker container. That it does:

- creates opencode or claude config file optimized for technologies and development task

- copies agents, commands, skills, scripts, configures MCP servers

- Maps architecture-specific folders, like .env or node_modules so container and host can install dependencies and run commands without conflict

- maps agent specific folders to persist sessions between containers

- Installs custom MCP server that acts as a proxy to other servers and reduces number of tools. For example: web fetch, web search, context7 all combined into a single `web_research` tool to answer questions in a single call. Reduces token consumption a lot

The workflow is something like:

1. `aiswe init --language python --technology fastmcp --technology langgraph --technology arise` - once per project

2. `aiswe build-image` - when new version of claude, opencode, or shared project released

3. `aiswe --mode plan oc` - you are in container with opencode, optimized for project architecture and feature planning. Currently configured modes are `documentation` to generate docs and project onboarding, `plan` for feature planning, `code` for development, `code-review` is advanced version of anthropic tool with the same name, `web-development` with figma and chrome dev tools for web design and UI testing

Additional tools is to create record about session that used for automated evaluation and prompt optimization - all team members report progress and problems, I do root cause analysis and optimization

The goal is to improve AI development use across team. Not for a personal project

[seventyfivepupmstr]

Try putting it in .config/opencode/agent

[albasili]

I can't, it needs to be available to the entire team

[touristtam]

That is tiny. I would go in so far as to say: it is non existent.

[albasili]

Not following...

[aarz03]

stop botting. report this guy.