Browse / Software development / multi-agent-workspace
multi-agent-workspace
mdnadeemai
File-based workspace template so Claude, Codex, and other coding agents start with project context instead of rebuilding it every session.
Open mdnadeemai/multi-agent-workspace → Does not match the four rules.
agentic-workflowsai-agentsclaude-codecodexcontext-engineeringdeveloper-toolsmulti-agent
Works with any agent
ships AGENTS.md, the cross-tool instruction file.
In its own words
A tool-agnostic, markdown-first workspace for running repeatable multi-agent workflows across Claude, Codex, CoWork, ChatGPT, and other AI tools without lock-in.
If you use more than one AI tool, you already know the failure mode:
- Claude knows one version of the task
- Codex knows another
- CoWork has different context again
- your laptop has local notes the other machine cannot see
- the same business facts get pasted over and over
- every new session starts with reconstruction instead of execution
Multi-Agent Workspace fixes that by moving the system out of chat history and into files you control.
No framework. No SDK. No custom backend. No lock-in to one vendor or one laptop.
- shared truth in markdown
- thin agent entry files
- reusable command files
- active work folders
- a structure that any serious AI assistant can read
What this is
Multi-Agent Workspace is an open template for people who want to work with multiple AI assistants on real work without rebuilding context every time.
- founders
- operators
- solo builders
- small teams
- anyone switching between AI tools and losing momentum
It works especially well when:
- one tool is better for strategy
- another is better for drafting
- another is better for file edits
- you work across multiple laptops or environments
- you want the system to stay readable without a custom app
What problem it solves
Most multi-agent setups fail for boring reasons:
Quoting 25% of the README. Read the rest on GitHub ↗
Read from the repository's git tree on 2026-08-17.