You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+11-17Lines changed: 11 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ A cross‑platform desktop UI (Avalonia/.NET 8) for driving the Codex CLI app se
8
8
- Start a Codex session and stream assistant output in real time
9
9
- Send user input that is wrapped as protocol `Submission`s (app server)
10
10
- Auto‑approve exec/patch requests (automatic)
11
-
- Pick a model (built-in or from `config.toml` profiles) and load MCP servers from a JSON config (see [Windows setup](README.windows.md) for a WSL recipe)
11
+
- Pick a model (built-in or from `config.toml` profiles) and load MCP servers from the Codex CLI `config.toml` (`[mcp_servers]` section); see [Windows setup](README.windows.md) for a WSL recipe
12
12
- Keep multiple Codex sessions active at once using the tabbed header (each tab title shows its live status, e.g., `Session 2 – thinking…`)
13
13
– See live token usage and estimated context remaining in the header
14
14
@@ -28,21 +28,18 @@ Semantic Developer can drive the Codex CLI from Linux, macOS, or Windows.
28
28
### Linux
29
29
30
30
- Install the .NET 8 SDK and the Codex CLI in your Linux environment.
31
-
- Profiles live under `~/.codex/config.toml`; prompts under `~/.codex/prompts/`.
- Profiles & MCP servers default to `%USERPROFILE%\.codex\config.toml` (respects `CODEX_HOME`); prompts live under `%USERPROFILE%\.codex\prompts\`.
46
43
47
44
## Build & Run
48
45
@@ -65,11 +62,8 @@ Semantic Developer can drive the Codex CLI from Linux, macOS, or Windows.
65
62
- Any profiles defined in `config.toml` (e.g., `$CODEX_HOME/config.toml`, defaulting to `~/.codex/config.toml`) are appended to the list and marked with an asterisk (`*`). Selecting a profile locks the reasoning controls and lets the profile determine the model/effort.
66
63
- Profiles are optional—if you don’t have one, simply pick a built-in model.
67
64
- Verbose logging (show suppressed output)
68
-
- Enable MCP support (loads MCP servers from your JSON config and passes them directly to Codex)
- Enable MCP support (mirrors the `[mcp_servers]` entries from your Codex CLI `config.toml` and passes them directly to Codex)
66
+
- Config defaults to `~/.codex/config.toml` on Linux/macOS and `%USERPROFILE%\.codex\config.toml` on Windows; both honor `$CODEX_HOME`.
73
67
- Use API Key for Codex CLI (pipes the key to `codex login --with-api-key` before sessions; does not rely on existing CLI auth)
74
68
- Allow network access for tools (sets sandbox_policy.network_access=true on turns so MCP tools can reach the network)
75
69
- Without API key enabled, the app proactively authenticates with `codex auth login` (falling back to `codex login`) before sessions so your chat/GPT token is used.
@@ -222,18 +216,18 @@ Notes
222
216
## MCP Servers Panel
223
217
224
218
- The left pane includes an MCP section below the file tree:
225
-
- Servers list: a checkbox per server from `mcp_servers.json`. Only selected servers are injected at session start.
219
+
- Servers list: a checkbox per server defined under `[mcp_servers]` in your Codex `config.toml`. Only selected servers are injected at session start.
226
220
- Tools list: after session starts, tools are grouped under their server names using short identifiers (the full identifier is available as a tooltip).
227
221
- Header buttons:
228
-
- ⚙ opens `mcp_servers.json` in your editor.
222
+
- ⚙ opens `config.toml` in your editor.
229
223
- ↻ reloads the config and updates the server list.
230
224
- Only local stdio servers are supported (command/args/cwd/env). Remote transports (e.g., SSE) are not injected.
> Unlike the Codex CLI's `config.toml`, which may also list MCP servers, the app only reads from `mcp_servers.json`. Keep your server command/argument definitions in this JSON file so Semantic Developer can surface them in the UI and pass them to Codex automatically. Profiles still live in`config.toml`, but MCP server wiring should follow the Semantic Developer format.
230
+
> Semantic Developer now shares the same MCP source as the Codex CLI. Define servers once inside`config.toml` and both the CLI and UI will pick them up automatically.
237
231
238
232
Selection behavior:
239
233
- The checkbox state in the MCP pane determines which servers are passed to Codex at session start.
Copy file name to clipboardExpand all lines: SemanticDeveloper/SemanticDeveloper/Views/CliSettingsDialog.axaml
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -78,7 +78,7 @@
78
78
IsChecked="{Binding McpEnabled, Mode=TwoWay}"
79
79
HorizontalAlignment="Stretch"
80
80
Margin="0,0,24,0"/>
81
-
<TextBlockMargin="0,4,24,6"Foreground="#888"FontSize="12"Text="Loads MCP servers from mcp_servers.json in your app data folder and passes them directly to Codex."TextWrapping="Wrap"/>
81
+
<TextBlockMargin="0,4,24,6"Foreground="#888"FontSize="12"Text="Loads MCP servers from the Codex CLI config.toml ([mcp_servers]) so they flow straight into Codex sessions."TextWrapping="Wrap"/>
82
82
<StackPanelIsEnabled="{Binding McpEnabled}">
83
83
<CheckBoxContent="Allow network access for tools (MCP, web fetches)"
0 commit comments