coder-config 0.42.4 → 0.42.6

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -1,22 +1,35 @@
1
1
  # Coder Config
2
2
 
3
- Configuration manager for AI coding tools **Claude Code**, **Gemini CLI**, **Codex CLI**, and **Antigravity**. Manage MCPs, rules, permissions, memory, and workstreams through a visual UI or CLI.
3
+ A configuration manager for AI coding tools. Works with Claude Code, Gemini CLI, Codex CLI, and Antigravity.
4
4
 
5
5
  > **Migration note:** This package was renamed from `@regression-io/claude-config` to `coder-config`. The `claude-config` command still works as an alias.
6
6
 
7
- ## Why?
7
+ ## The Problem
8
8
 
9
- One tool to configure all your AI coding assistants:
9
+ AI coding assistants are powerful, but managing their configuration across projects is tedious. Each tool has its own config format. MCP servers need to be set up per-project. Context gets lost between sessions. Working across multiple repos means re-explaining relationships every time.
10
10
 
11
- | | |
12
- |---|---|
13
- | **MCP Servers** | Configure without editing JSON/TOML files |
14
- | **Permissions** | Visual editor for allow/deny rules |
15
- | **Multi-Tool** | Claude Code, Gemini CLI, Codex CLI, Antigravity |
16
- | **Rules & Commands** | Manage project-specific guidelines |
17
- | **Memory** | Persistent context across sessions |
18
- | **Workstreams** | Group projects with shared context |
19
- | **Ralph Loops** | Autonomous development until task completion |
11
+ ## What Coder Config Does
12
+
13
+ **Workstreams**
14
+ Group related repos together. When a workstream is active, Claude automatically knows which directories it can access and receives your custom context. Useful for microservices, monorepos, or any multi-repo workflow where projects relate to each other.
15
+
16
+ **Unified MCP Registry**
17
+ Define your MCP servers once in a global registry. Enable them per-project with a toggle. Configuration inherits from global → workspace → project, so common tools are always available while project-specific ones stay scoped.
18
+
19
+ **Hierarchical Rules**
20
+ Rules cascade from `~/.claude/rules/` down to project-specific rules. Global conventions apply everywhere; project-specific instructions stay local.
21
+
22
+ **Persistent Memory**
23
+ Store preferences, corrections, and patterns that persist across sessions. When you tell Claude "always use our logger instead of console.log," it remembers — not just for this session, but permanently.
24
+
25
+ **Plugin System**
26
+ Install LSP servers, MCP tools, and custom commands from plugin marketplaces. Plugins can be scoped globally or per-project.
27
+
28
+ **Multi-Tool Output**
29
+ Write one config, generate outputs for Claude Code (`.mcp.json`), Gemini CLI (`settings.json`), Codex CLI (`config.toml`), and Antigravity. Switch tools without reconfiguring.
30
+
31
+ **Web UI**
32
+ Visual interface for managing everything above. File explorer for `.claude` folders, MCP toggles, memory editor, workstream management. Runs locally on port 3333.
20
33
 
21
34
  ## Installation
22
35
 
package/lib/constants.js CHANGED
@@ -2,7 +2,7 @@
2
2
  * Constants and tool path configurations
3
3
  */
4
4
 
5
- const VERSION = '0.42.4';
5
+ const VERSION = '0.42.6';
6
6
 
7
7
  // Tool-specific path configurations
8
8
  const TOOL_PATHS = {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "coder-config",
3
- "version": "0.42.4",
3
+ "version": "0.42.6",
4
4
  "description": "Configuration manager for AI coding tools - Claude Code, Gemini CLI, Codex CLI, Antigravity. Manage MCPs, rules, permissions, memory, and workstreams.",
5
5
  "author": "regression.io",
6
6
  "main": "config-loader.js",