Skip to content

Commit e49da68

Browse files
authored
Add v0.4.4 release notes (#105)
Co-authored-by: uchebnick <uchebnick@users.noreply.github.com>
1 parent e163efa commit e49da68

1 file changed

Lines changed: 18 additions & 0 deletions

File tree

.github/releases/v0.4.4.md

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
# unch v0.4.4
2+
3+
`v0.4.4` is a small MCP and Codex reliability release. It makes the Codex integration safer to use across real workspaces and refreshes the project documentation around the current setup flow.
4+
5+
## Highlights
6+
7+
- MCP tools now accept an optional `directory` argument, so `workspace_status`, `search_code`, and `index_repository` can operate on the active repository instead of the directory where the MCP server process was launched
8+
- The MCP backend now routes tool calls to a repository-scoped backend and keeps `workspace_status` cheap: checking another workspace does not create `.semsearch`
9+
- The Codex MCP setup docs were simplified around the recommended flow: install the npm wrapper, run `unch codex install`, then restart Codex
10+
- The npm package docs now point users at the same Codex setup flow as the main README and Mintlify docs
11+
- `CONTRIBUTING.md` now includes a fuller project overview, module map, and development workflow for contributors
12+
13+
## Upgrade notes
14+
15+
- If you use Codex with the npm wrapper, update and re-run `unch codex install`, then restart Codex
16+
- The MCP tool names are unchanged: `workspace_status`, `search_code`, and `index_repository`
17+
- Existing `.semsearch` indexes remain compatible; this release changes MCP workspace routing, not the index format
18+
- Source installs can use `go install github.com/uchebnick/unch/cmd/unch@v0.4.4`

0 commit comments

Comments
 (0)