Changelog

What’s new.

Everything we ship to cix — new features, improvements, and fixes. Newest first.

1.1.0

August 15, 2026

A default install stops carrying operator tools, and Cursor stands on its own

Installs now carry only what a customer needs, and upgrading removes the operator-only commands an older install left behind. Cursor gets a complete command surface of its own. And several notices that stated things cix had not actually checked now say what is true.

NewCursor installs its own commands and workflow layer, so a Cursor-only setup is complete without another client present. Where the same command is visible through more than one editor's folder, every copy now says the same thing — so whichever copy your editor picks is the right one, and it names the client you are actually in rather than assuming.
NewWhen two copies of cix end up installed in one environment, health checks now name the conflict and print the exact commands to repair it. Running that repair is opt-in and needs an explicit confirmation; if it stops partway it tells you a package was already removed and exactly what is left to run, rather than leaving you to discover it at the next command.
ImprovedA default install now carries only what a customer needs. The parse-error report (/cix-errors) and the hook on/off commands (/cix-disable-hooks, /cix-enable-hooks) are operator tools and now require the developer profile. Upgrading REMOVES them if an earlier install left them in place — add --dev to keep them. Your own commands in the same folder are never touched.
ImprovedInstalling every client now includes Cursor.
FixedThe startup notice that said repository intelligence was unavailable no longer implies your calls are being refused when nothing is refusing them. It states what actually follows in the session you are in, and says when the answer came from a cached check that may since have moved on.
Fixedcix no longer switches on a global hooks setting you had deliberately turned off. Your choice stays as you set it, and cix tells you the hooks it just installed will not run until you change it back. Uninstalling no longer silently turns that setting back on either.
FixedA search that finds nothing stops reporting that as proof the name does not exist when recent local work was not part of what was searched. It now says what was actually covered and how to include the rest, so a missing result no longer reads as licence to write a duplicate.
FixedEvery client now states what a default install does not enforce. Two of four said nothing, so their users carried an assumption the profile does not deliver.

1.0.63

August 14, 2026

Sessions start knowing your conventions — in your language

Every session now opens with your repository's convention state, worded once by the service and delivered the same to every client — with Spanish as the first translation. Cursor becomes a supported client, and machine-wide guidance moves into one file per client instead of a copy per repository.

NewSessions open with a summary of what your repository's conventions declare — or the honest statement that they declare none — before any work begins, so rules get followed on the first attempt rather than corrected after. The summary arrives in your language when a translation exists (Spanish first); anything untranslated falls back to English rather than disappearing, and file paths and rule names are never translated. If the summary can't be fetched in time, the session simply starts without it — never an error, never a slow start.
NewCursor is now a supported client: registration, health checks, and staleness warnings arrive with install, and the guardrails profile adds the same deterministic convention enforcement other clients get. In folders you haven't trusted, Cursor runs no hooks at all — and cix reports itself absent there, rather than pretending to be merely degraded.
ImprovedMachine-wide guidance now lives in one file per client, written once at install, and each repository's own block shrinks to what only that repository can say. Fewer copies means fewer stale copies — the drift this replaces was measured at eight stale documents on one machine. And if you have edited cix's block in your global file, cix refuses to touch your version and says so, instead of backing it up and rewriting it.
ImprovedAntigravity's one enforceable surface is now wired by the guardrails profile, and each client's support matrix states plainly what every profile does and does not enforce.
FixedA file's convention rules now come from the repository the file lives in — never from the directory a command happened to run from. Previously, checking a file from another directory could answer with the wrong repository's rules.

1.0.62

August 13, 2026

Convention checks that answer renames, and name the fix

Checking a file against your project's conventions now covers renaming and moving, not just creating — and when something is denied, cix tells you what to call the file instead. Every request also identifies which client version sent it, so support can see exactly what you're running.

NewConvention checking now answers the three questions that come up in real work — can I create this, can I rename this, can I move this — instead of only the first. A denial names the compliant filename rather than leaving you to guess, and when a less obvious rulebook governs a path, cix says which one, once.
NewYour AI assistant is reminded of the relevant naming and placement rules at the moment it starts work, not after it has already written a file somewhere wrong — so conventions get followed on the first attempt instead of corrected in review.
ImprovedWhen conventions can't be evaluated, cix now says so and names the state it found, instead of silently reporting success. A published support matrix says exactly which languages and clients convention delivery covers — and a check that could never fire is no longer promised.
ImprovedEvery request now carries the version of the client that sent it, and the service records it. When something behaves oddly, support can see exactly which version you were running instead of asking you to find out.
FixedA broken guidance lookup can no longer block a write that should have been allowed — guidance failures degrade to silence, never to a refusal. And removing cix from a project restores the editor prompt entries that an earlier version could drop.

1.0.61

August 11, 2026

Your planning and design work now lives with your account

cix now ships a research, design, and planning workspace alongside the index, so the reasoning behind a change survives a new machine, a fresh checkout, and a cleared context window — and your AI client can read and update it directly. Assistant-facing output is machine-readable, and removing a single project now finishes cleanly.

NewResearch notes, designs, and multi-step plans are now stored with your account rather than in files you have to keep and carry. They are available from any machine you sign in on, and your AI client can read and update them while it works — so the reasoning behind a change is still there weeks later, when the conversation that produced it is long gone. Included with a paid plan.
NewThe read commands an AI client uses can now emit machine-readable output — one self-describing record per line, each naming the schema it follows — so an assistant consumes a plan or a design directly instead of parsing text meant for people. Fields that look like credentials are refused outright rather than printed, and diagnostics never mix into that output.
ImprovedIf your plan does not include the workspace, cix now says exactly that in one line and points you to the page that changes it, instead of failing with a generic error. Anything you have already stored stays untouched and becomes readable again the moment the plan is active — a refusal never deletes your work.
FixedRemoving cix from a single project no longer stops partway through, and now takes cix's own editor entry and the git hook cix installed with it. Entries and hooks belonging to your other tools are left exactly as they were. Previously this could fail outright, leaving your editor pointing at a project connection that no longer worked.
ImprovedEverything cix adds to a project is recorded at the moment it is written, so removing it takes back exactly what cix put there — and nothing that was already yours.

1.0.60

August 10, 2026

A clean first run, and a clean exit on Windows

Setting up a project no longer stalls when nothing is there to answer a prompt, uninstalling on Windows now takes cix's own editor entry with it, Windows commands hand your prompt back only once they have actually finished, and the upgrade notice finally names a command that works.

FixedSetting up a project no longer stalls when cix runs unattended — in a script, a scheduled job, or any pipeline where nothing is there to answer a question. cix now recognises that no one is available to answer, skips the optional step, and prints the link you need to continue. Previously it waited for an answer that could never arrive, and the run hung until it was killed.
FixedUninstalling on Windows now removes cix's own entry from Claude Desktop. Previously cix left that entry behind, so Claude Desktop kept listing a cix connection that no longer existed and showed it as permanently failing. Entries belonging to your other tools are left exactly as they were.
FixedCommands on Windows now hand your prompt back only after they have finished printing, and report their real success or failure. Previously the prompt could return while output was still being written, leaving the cursor in the wrong place, making Ctrl+C unpredictable, and reporting a misleading result even when the command had succeeded.
FixedThe notice that tells you a newer version is available now names an upgrade command that actually exists, matched to the way you installed cix. Previously it pointed at a command no release has ever included, so following the suggestion produced a "command not found" error.
ImprovedThe uninstall summary now states more precisely which data is removed from your machine and which stays with your account.

1.0.52

August 5, 2026

Files stay readable after you commit

On projects cix indexes directly from your machine, a file you can read once stays readable — through new commits, through branch switches, and when a second person is working in the same project. Previously an ordinary commit that did not even touch the file could make it unreadable for the rest of your session, and the usual repair reported success without fixing anything.

FixedReading a file no longer breaks after you make an unrelated commit. Previously any new commit could strand the copy cix was reading from, and every later read of that file failed until you restarted — even though the file itself had not changed.
FixedRefreshing a single file now actually refreshes it. Previously, for a committed and pushed file on a directly-indexed project, the refresh reported success while doing nothing at all — so the one repair available could not fix the one thing it was needed for.
FixedA routine sync no longer discards the only copy cix holds of your committed files. On projects indexed directly from your machine, that copy is the sole source cix can read from, and the cleanup step was removing it.
FixedTwo people working in the same project no longer affect each other's reads. Previously, an answer cached for one account could be reused for another, causing cix to choose the wrong source and make otherwise readable files temporarily unavailable through cix.
ImprovedWhen a read finds its copy missing, cix now repairs it once and returns your file, instead of failing. The repair is reported alongside the result, so a project that needs it on every read is visible rather than just slower.
ImprovedFiles whose names contain unusual characters, such as a line break, are now recognised correctly during cleanup. Previously they were treated as a different file, so cix discarded its copy of them and they became unreadable through cix.
ImprovedWhen cix cannot determine what a project contains, the cleanup step is skipped and says so, instead of proceeding as though the project were empty.

1.0.40

July 28, 2026

The last silent lookups now explain themselves

Four read surfaces that still answered an empty lookup with a bare not-found now say what happened — and stale-index advice no longer stands in for an explanation.

FixedThe four remaining read surfaces that answered an empty lookup with a bare not-found now name the cause. If the name exists but a path you passed excluded it, the response says so, lists where it actually lives, and spells out the call that would succeed. If nothing carries that name at all, it says that instead and points at the fuzzy search — this lookup matches whole names only, so a near miss in spelling returns empty rather than the closest match. Previously both cases were the same silent response, and they call for opposite reactions: drop the filter, or stop looking.
FixedA lookup that found nothing no longer advises refreshing the index. On an otherwise silent miss that advice was the only actionable-looking field in the response, so it read as the explanation — and no refresh can make an absent name resolve. Freshness advice now appears only where a freshness check actually ran on real content; on a miss, the response says the emptiness is explained elsewhere and points to the explanation. The advice itself is unchanged where it is real: it still appears, unmodified, whenever a lookup finds something.
ImprovedAn empty file listing now separates three causes that used to look identical: the filters you passed excluded every indexed file — the response names only the filters you actually used, against the measured total they excluded — or the project has nothing indexed yet, which is a property of the project rather than the query, or the limit left no room. Each answer names its own remedy.
ImprovedAsking for the outline of a path with no indexed symbols now explains the two ways that happens and how to tell them apart — and when another indexed file shares the same filename, the response points at it, since a differently-rooted path is the usual cause of this miss.

1.0.39

July 28, 2026

An empty answer now tells you why it is empty

When cix comes back with nothing, it says which of two very different things happened — the thing is not here, or a filter you passed removed it.

FixedA lookup that finds nothing now says why. If a filter you supplied removed the result, cix names that filter, says how many rows it removed, and lists the values that do exist for what you asked about — so the retry is a single obvious edit. If the thing genuinely is not indexed, it says that instead. Previously the two were the same response, and they call for opposite reactions: drop the filter, or stop looking.
FixedA lookup that reports finding nothing no longer returns that same thing's callers alongside. Previously the response could say it had not found something while listing what calls it, which is not an answer anyone can act on.
FixedA request cix rejects as invalid is no longer reported as the service being unreachable. The reason cix actually gave — usually a missing or misspelled argument — is now the headline. Previously the advice was to check your network and configuration, which is the one place the problem was not, while the real reason sat unread further down the response.
ImprovedListings that come back empty no longer claim a filter matched nothing when no filter was passed. If your project simply has none of that kind of thing, cix now says so — a property of the project, not of the query — instead of implying different arguments might help. Two filters that can never match anything are now named as such rather than reported as an ordinary near miss.
ImprovedSuggested follow-up calls are now built from what was actually found, and are left out when there is nothing specific to suggest. Previously a staleness audit could advise inspecting a candidate while returning no candidates, with the placeholder still unfilled, and some empty responses carried the same generic suggestion regardless of what had been asked.
ImprovedA staleness audit that returns nothing now distinguishes "nothing was eligible to check" from "nothing is stale." The first is not a clean bill of health, and reading it as one is how an audit gets quietly trusted.

1.0.35

July 27, 2026

File refreshes are now strictly project-scoped

Refresh operations now validate that a file belongs to the active project before reading or sending any content. Unsupported files are rejected locally, and multi-file reads retain freshness verification for every file. Upgrading is recommended — see the first two items.

FixedPaths given to a refresh are now canonicalized and confirmed to resolve inside the active project before the file is read or any content is sent. File refresh previously validated paths too late, so an explicitly supplied path outside the project could reach the refresh request and have that file's contents transmitted and indexed. This affects all published versions up to and including 1.0.34. Exploitation required a refresh request running locally with an explicitly supplied path outside the project. We have no reports or other indication that this occurred. Content held for refresh also expires within 24 hours. Upgrade to 1.0.35 to close it.
FixedFiles the service does not support are now rejected locally, so nothing is transmitted for a file that will not be indexed. Previously the contents were sent before that determination came back, which meant a file such as an environment file or a certificate could be transmitted while the response correctly reported that the refresh had been skipped. Same affected versions and same upgrade guidance as above.
ImprovedChange-impact answers now distinguish code that has no callers from code whose callers cannot be measured. Where a language's relationships between files are matched by text rather than parsed, the answer states that the measurement was unavailable, names the language, and points to what to check directly. Previously an unmeasurable result was presented the same way as a confirmed absence of callers.
ImprovedReading several files at once now verifies freshness for every file and reports each one's status individually. Freshness verification previously applied to single-file reads only, so the multi-file view — the one recommended for scanning a set of files — returned without it.
ImprovedA file that defines no functions of its own — a page that is entirely markup, or entirely inline script — is now reported distinctly from a file that is absent from the index, together with how to confirm which of the two applies.
ImprovedHealth scores for repositories shared with you now use the authoritative index — the owner's — when reading index status. The score previously looked for a record that exists only for repositories you index yourself and treated its absence as the lowest possible reading, which moved an otherwise healthy repository from green to amber.
ImprovedProject safeguards now apply only to files inside the active project, so creating unrelated scratch files elsewhere on your machine proceeds normally.

What’s new.

A default install stops carrying operator tools, and Cursor stands on its own

Sessions start knowing your conventions — in your language

Convention checks that answer renames, and name the fix

Your planning and design work now lives with your account

A clean first run, and a clean exit on Windows

Windows reliability: edits and reads no longer hang, and CRLF files edit cleanly

An optional profile that keeps AI edits routed through your index

Full uninstall now removes all local CIX data

Clean uninstalls, and tool guidance that improves between releases

File listings follow the branch you're actually on

Search file contents, not just symbol names

Files stay readable after you commit

You can check whether an index really matches your project

Deleting files removes them from your index

Files read normally in repositories you index from your machine

One answer about where a file's content came from, instead of two

Reading several files at once now accounts for your local work

Asking about several files at once no longer describes the ones that aren't there

A version-control flag that was never about version control

One word in a response no longer means two different things

A read of a file that isn't there stops describing one that is

Two lookups now say which argument they need

The last silent lookups now explain themselves

An empty answer now tells you why it is empty

Narrowing a lookup by kind or language now actually narrows

Code search stops turning away kinds your project actually has

Search tells you what it matched on

File refreshes are now strictly project-scoped

Shared repositories report their real state, and duplicates have an exit

Repositories shared with you just work

The health check tells you what actually updates your index

Working across several repos keeps all of them current

Setup follows how your repo is actually indexed

Index a private repo from your own machine

Six honesty fixes in one night

Deleted files no longer haunt your reads

A mistyped project id can no longer touch the wrong repo

Your unpushed work is now findable by name

One answer per file, and misses that explain themselves

Reads see your unpushed work

More honest file reads

Seven tools restored

Clearer tool guidance

Better symbol lookups

General improvements

cix-serve improvements

Follow-up refinements

Further tool improvements

Leaner tool responses, everywhere

Leaner tool responses

Worktree editing, anchored to the file

Edit files inside a git worktree

Correct across multiple repositories

Edits that don't drift, and a faster first session

Honest index health on feature branches

Clearer status, sharper pre-commit impact

cix is on PyPI