What's new in Componecat

New features

See your search results as a graph

The catalog now has a Graph view next to Tree and List. Run any search, switch to Graph, and you see the entities you found and every relationship between them, so the shape of a system or a team's services is visible at a glance. Pick which relationship kinds to draw, and if you searched by scorecard, each entity shows the same score badge it has in the list. Collections get the same view, so a hand-picked set of services can be seen as one connected picture.

Describe relationships with attributes

Relationships can now carry attributes that describe the connection itself — the protocol one service calls another over, the SLA it depends on, or free-form notes. Declare them in a componecat.yaml descriptor, or set them through GraphQL, REST or MCP. Give a relationship kind an attribute schema to make attributes typed and required, using the same field types as custom fields, and Componecat rejects a relationship that is missing a required attribute or has a value it doesn't accept, naming the attribute at fault.

Relationships now show where they came from

Every relationship now records how it came to exist: added by hand, declared in a componecat.yaml descriptor, or inferred by automation. Descriptor relationships name the repository, descriptor path and commit they came from, and show when a sync last confirmed them; hand-added ones record who added them. If you add a relationship by hand and later declare it in a descriptor, it's upgraded in place and the change is noted in the entity's activity log. The source badge on the Relationships tab shows the details, and the same information is available over GraphQL, REST and MCP.

Explore an entity's neighborhood as a graph

Every entity page now has a Graph tab that draws the entity and everything connected to it. Go out up to five hops, follow outbound, inbound or both directions, pick the relationship kinds to follow, color entities by kind or source, and hide inferred relationships. Click an entity for a summary and a link to its page, double-click it to expand one more hop, or click a relationship to see where it came from and its attributes. The view is part of the page address, so you can share it, and your last-used settings are remembered.

Find how two entities are connected

Ask how one entity ends up depending on another and get the answer as paths: the chains of relationships that connect them, shortest first, across whichever relationship kinds and direction you choose. Explain a dependency, confirm a link you assumed, or find a coupling you didn't expect — all in one GraphQL request.

Fix relationships right from the graph

The Graph tab is now a place to edit, not only to look. Drag one entity onto another to add a relationship, or select an entity and choose "Add relationship to…" if you prefer the keyboard. Select a relationship to edit its description and attributes, or remove it after confirming. If a rule such as a cycle or cardinality limit refuses the change, the dialog tells you why and nothing is drawn. When a teammate adds or removes a relationship between entities you are looking at, the graph updates on its own.

See your whole catalog as one graph

A new Graph page in the sidebar draws your entire catalog at once: every entity and every relationship between them, filling the screen. Pick which relationship kinds to draw, color entities by kind, source or lifecycle, hide inferred relationships, and click any entity or relationship for its details. From there, one click takes you into that entity's own Graph tab to walk its neighborhood, measure impact or find paths. The view lives in the address bar, so it can be bookmarked and shared, and it redraws itself as the catalog changes. The small graph at the bottom of an entity's Relationships tab is retired in favor of the Graph tab.

See the blast radius and the paths on the graph

The Graph tab on an entity page now has Impact and Path views. Impact highlights everything affected if the entity changes, ringed and numbered by how many hops away it is, with a count and a legend. Path lets you pick another entity and draws how the two are connected, shortest path found first, with the alternatives a click away. Copy a link to share either view, or export it as a PNG or SVG, legend included, for a review or an ADR.

Agents see the whole graph in one call

AI agents connected to Componecat can now ask "what is around this component?" and "how are these two connected?" directly. traverse_graph returns everything reachable from an entity — across any relationship kinds, in either direction — and find_paths returns the chains of relationships linking two entities, shortest first. Each edge says whether it was entered by hand, declared in a descriptor, or inferred, so an agent knows how much to trust it. The same tools are available in AI Chat.

See how much to trust each relationship

The Relationships tab now tells you where every relationship came from at a glance. Inferred relationships show how confident Componecat is, and hovering or focusing a badge shows who added it or which descriptor or run declared it, and when it was last confirmed. Descriptor relationships link straight to the file that declares them, and you can filter the list to one source. Relationship attributes now show up right in the list, you can fill them in when you add or edit a relationship, and admins can define each relationship kind's attributes, including required ones, from the Relationship Kinds page.

Graph traversal and path finding over REST

Scripts, CI checks and dashboards that don't speak GraphQL can now explore the catalog graph over REST. GET /catalog/{id}/graph returns everything reachable from an entity across the relationship kinds you choose, in either direction, and GET /catalog/{id}/paths/{targetId} returns the chains of relationships linking two entities, shortest first. Every edge says how it was asserted, how confident Componecat is in it, and its attributes — the same answers the GraphQL API and AI agents get.

Connected agents stay connected

Agents and API clients no longer need re-approving every month. An authorization now renews itself in the background, so a connected agent keeps working until you revoke it or it goes 30 days unused. Clients that don't support renewal ask you hourly instead.

Integrations also got safer and clearer: deleting one now asks for confirmation, and testing a connection reports the result.

Traverse the catalog graph in one request

Ask for everything reachable from an entity — across one or several relationship kinds, outbound, inbound or both, up to a chosen number of hops — and get the whole subgraph back in one GraphQL request, with each entity's distance from the start and every relationship between them. Narrow the walk with the same search language as the catalog, for example to stay inside production.

Improvements

Impact analysis covers all your dependency kinds, in either direction

Impact analysis now follows every relationship kind you mark as a dependency — depends-on, calls, reads-from, whatever you use — instead of only the first, so the blast radius it reports is the whole one. You can also choose the direction: downstream (what this entity relies on), upstream (what relies on it), or both, and each result shows how many hops away it is and which relationship kinds reached it. Available to AI agents through get_impact_analysis, and over the GraphQL and REST APIs.

Bug fixes

Deleted custom fields no longer get stuck on collections

When you delete a custom field, it now drops off the display settings of every collection that was showing it. Any collection still carrying a field that no longer exists shows it as removed in the collection editor, so you can clear it with one click.

MCP create and wiki tools work again

AI agents connected over MCP can once again create teams, catalog entities and wiki pages, read wiki guides, and edit the schema. These tools had been failing with a generic error. Agents whose token lacks the needed access still get a clear access-denied message.

Plans page names each integration provider directly

The plans page now lists integration providers by name — GitHub, GitLab, Bitbucket, Atlassian, Microsoft 365 — grouped directly under Integrations, instead of repeating "integration" after each one in an arbitrary order.

Bug fixes

Teams load reliably on the home page

Organizations with many teams sometimes saw the teams list fail to load when returning to the home page, until a refresh. That no longer happens.

New features

Let teams own who edits their entries and sees private interfaces

You can now reserve two things for the team that owns an entity. Turn on "Limit editing to the owning team" and only that team's members and your admins can add or change its entities. Turn on "Limit private interfaces to the owning team" and interfaces marked Private are shown only to those same people.

Each control has its own switch under Organization settings, in the new Team Access section, and both start off. Any team can differ from the organization: edit the team and choose whether it follows the organization, is always limited to its members, or is always open to everyone.

Improvements

Collection pages use the full width of your screen

A collection's page now stretches across the whole window, so you see more of its items at once on a wide screen.

Bug fixes

Picking an organization now lands on Home

Choosing an organization from the organization list, or finishing onboarding into a new one, now lands you on that organization's Home page. Previously those two paths dropped you into the catalog, while signing in directly already went to Home.

Cleaner page structure for screen readers

Every page in the app now has exactly one main content region. Previously screen readers listed two nested "main" landmarks, which made landmark navigation confusing. The "Skip to main content" link still takes you straight to the page content.

The wiki editor explains frontmatter tags

If you paste a page from a Git repository into the wiki editor, its frontmatter tags: list doesn't tag the page: pages written in the app are tagged with the tag bar. The editor now shows a note under the tag bar whenever the page body has frontmatter tags, so you can add them with Add reference instead of finding out later that the page has no tags.

Improvements

One name for every select option

Select and multi-select options no longer have a hidden internal key behind the name you see. The value shown in the app is now exactly what the APIs, the MCP server and your componecat.yaml files use, so an option that reads "Core Platform" on screen is "Core Platform" everywhere. Existing catalogs are converted automatically, including collections, saved searches and scorecard rules that compared one of these fields to the old internal key.

Improvements

A more dependable REST API for syncing your catalog

Bulk relationship updates over the REST API work again, and you can now choose which fields each entity kind carries without leaving the API. Search results include each entity's custom field values, so exporting your catalog takes far fewer requests. Creating an entity no longer reports an error for a change that was actually saved.

Bug fixes

Webhook delivery history stays up to date

A webhook's delivery history now shows the latest deliveries as soon as you open it, and a refresh button lets you check for new ones without reloading the page.

Improvements

Choose exactly which changes each webhook receives

Webhooks can now be narrowed by record type, action, and entity kind. For example, you can send only updates to Services, or only scorecard results for your Systems. You can also attach custom headers, such as an authorization token your endpoint expects. Event types now name the record that changed, such as componecat.catalog-entity.updated. If your endpoint routes on the event type, update it.

Improvements

Catalog API responses now name the owning team

When you fetch a catalog entity through the REST API, the response now includes the owning team's name and, for teams synced from your directory, the team's ID there. You no longer need a second request to find out who owns something.

Webhooks now tell you more about who owns what

Catalog entity webhooks now include the owning team's ID and, for synced teams, its ID in your team directory. You can route work to the right team without an extra lookup. Webhooks also fire when a team is created, renamed, relinked, or removed, so systems that mirror ownership stay in step right away.

Improvements

Synced teams show their external ID in the API, and outgoing webhooks are documented

Teams synced from Atlassian, GitHub, GitLab or Microsoft 365 now include their ID in that system when you read them through the REST API or an AI agent. Scripts can use it to find the same team upstream, for example when setting a team on a Jira issue. There is also a new reference page for outgoing webhooks. It covers each event, the payload format, and how to verify the signature on a request.

Webhooks now tell you more about who owns what

Catalog entity webhooks now include the owning team's ID and, for synced teams, its ID in your team directory. You can route work to the right team without an extra lookup. Webhooks also fire when a team is created, renamed, relinked, or removed, so systems that mirror ownership stay in step right away.

Bug fixes

Service accounts can look up their organization over MCP

AI agents connected with a service account can now ask which organization they are working in. Before, that request failed for service accounts even though it worked for people.

Validation errors now report a consistent error code

Validation errors from the GraphQL API and MCP tools now consistently return the VALIDATION_ERROR error code with the invalid field named in the field extension, instead of occasionally reporting the field name as the error code itself. REST responses for these errors now correctly return 422 Unprocessable Entity.

Improvements

A complete reference for the catalog REST API

The REST API's OpenAPI schema now describes every catalog field, filter and search option, so you can generate clients and explore the API without guesswork. Detected repository languages are no longer part of the catalog entity payload, and lifecycle values are spelled the same way in every response.

Bug fixes

The AI assistant panel opens reliably again

Opening the AI assistant could leave the whole screen blank. The assistant panel now opens beside your page as expected, and you can keep working while it is open.

Bug fixes

Fixed the Tree view expand chevron drifting away from wrapped entity names

In Catalog Tree view, the expand chevron and kind icon now stay anchored to the entity name at narrow viewport widths. Before, once an entity's name and badges wrapped onto several lines, the chevron and icon could drift down next to an unrelated badge in the middle of the stack.

Fixed the Documentation tab's Add Link button doing nothing

The Documentation tab's "Add Link" button now always opens the add-link dialog. Before, it silently did nothing unless the Links item in the Contents sidebar was already selected.

Fixed unreadable entity reference wrapping in parent/system links

Entity reference links that fall back to showing the raw ref URI (e.g. when an entity has no display name) now wrap at natural / and - boundaries instead of breaking character-by-character at narrow viewport widths.

Clearer error when importing a spec for an interface without a URL

When an AI agent asks to import the spec for an interface that has no spec URL configured, the import_interface_spec MCP tool now says exactly that, instead of returning a generic tool failure.

Bug fixes

Choose which relationships impact analysis follows

You can now mark any relationship kind as a dependency, right from its settings page, and impact analysis follows it to show what a change could affect. Your existing "depends on" relationships are picked up automatically, and kinds you create from a template keep their built-in behavior.

Clearer errors when an AI agent calls a tool the wrong way

When an AI agent passes a wrong or misspelled argument to a Componecat tool, the error now says which arguments the tool expects. Agents can correct the call and carry on instead of getting stuck on a vague failure.

New features

Three built-in scorecards, ready to turn on

Every organization now starts with three scorecards already built — Field Completeness, Freshness, and Agent Readiness — sitting disabled until you're ready to turn one on. Field Completeness flags entities missing a value your kind marks required. Freshness scores how recently a record, its synced descriptor, and its docs were last touched (it's upfront that it can't see commit or deploy activity yet). Agent Readiness checks what an AI agent needs to use an entity correctly: a reachable owning team, a real description, documentation, a spec URL on its API, and reasonably current data. All three are ordinary scorecards — rename them, edit their rules, or delete them like any other, and doing so is remembered even across a restart.

Search dates relative to right now

Date filters in the search box now understand relative time, not just fixed dates. updatedAt:<now-90d finds everything not touched in the last 90 days — and keeps meaning that every day, instead of the fixed date you'd otherwise have to keep retyping. Use now on its own, or follow it with a sign, a number, and a unit: hours (h), days (d), months (mo), or years (y) — for example now-24h, now+30d, now-6mo, or in a range like updatedAt:[now-30d TO now]. This works everywhere a search query does, including saved searches and dynamic collections, so "updated this week" can finally be saved and stay true.

One side effect: exact-date matching (:) on your own custom date fields now compares the actual date rather than the exact stored text, so it matches anything recorded on that day instead of only values written in exactly that form. If a saved search or dynamic collection filters on a custom date field, its results may include a few different entities than before.

Define standards with Scorecards

Scorecards let you define what "good" looks like for a slice of your catalog — a scope, a set of weighted rules, and an optional Bronze/Silver/Gold-style ladder — and Componecat checks every matching entity against it automatically. Open Scorecards to create one: as you write the scope and each rule, a live preview shows how many entities are in scope and how many currently pass or fail, with a sample of the failing ones, so you can calibrate a standard against your real catalog before you publish it. Any organization member can view scorecards and how the catalog scores against them; creating, editing, and deleting them is restricted to organization admins.

REST endpoints for scorecard definitions and rollup reports

The REST API now has a proper scorecard resource, not just per-entity results. List your scorecards, read one's full definition (scope, rules, weights), or pull its rollup report — distribution, team/kind breakdowns, per-rule failure counts, and trend — the same data the app's Report tab shows. Like the rest of the scorecards automation surface, it's read-only: standards are still authored in the app.

Scorecard rollups — a report, a trend, and team standing

Every scorecard now has a Report tab: entity count in scope, mean score, percent fully passing, a score distribution, and worst-first breakdowns by ladder level, owning team, kind, and per-rule failures — every number linking straight into the catalog filtered to exactly what it counts. A trend chart shows the score over time, marking when the scorecard's definition last changed. Team pages now summarize each team's standing across its applicable scorecards.

Scorecard scores, now visible where you look

Scorecard results are no longer confined to the authoring screen. Every entity page gets a Scorecards tab (when a scorecard applies) showing its score, attained level, and which rules are passing or failing, with a link to fix each failure. Search understands scorecard:, score:, and level: clauses — scorecard:security AND score:>=80 — and a matching row shows its score right there in the results.

Scorecards over MCP, REST, and outgoing webhooks

Scorecard results now follow your standards everywhere you automate against Componecat. An AI agent can list your scorecards, check an entity's results, or list everything failing a standard — read-only, so agents can look but not touch. The REST API exposes the same results at /api/rest/v1/catalog/{id}/scorecards. And an outgoing webhook subscription can now react the moment a scorecard's score or level changes for an entity, with the failing rules right in the payload — not on every routine re-check, only on a real change.

Bug fixes

Fixed illegible catalog list-view results on mobile

Catalog search results in List view no longer hide the entity name and overflow their badges off-screen at mobile viewport widths — badges now wrap under the title instead.

Fixed scorecard score badge disappearing on catalog rows at mobile widths

A catalog or search result row's scorecard score/level badge no longer disappears entirely at narrow (mobile) viewport widths — it now wraps onto its own line alongside the Team, Lifecycle, and Kind badges instead of being hidden.

Catalog search result badge no longer shows a misleading 100% for scorecards with no rules

Searching the catalog for entities against a scorecard whose rules were all removed after creation used to show a green "100" score badge on every matching row, as if every entity had been checked and passed. It now shows an explicit "No rules defined" badge instead.

Fixed the catalog search toolbar clipping the Saved button at mobile widths

The catalog page's search toolbar (search box, Filters, Saved) no longer clips the Saved button off the edge of the screen at mobile widths — it now wraps onto additional lines so every control stays visible and reachable.

Fixed clipped Tree/List toggle label on the catalog results toolbar

The catalog search results toolbar (Sort and the Tree/List view toggle) no longer clips its labels at mobile viewport widths — it now wraps onto additional lines so "Tree" and "List" stay fully readable.

Catalog Tree view now shows scorecard score badges

Searching the catalog for entities against a scorecard (scorecard:<name>) now shows each entity's score badge in Tree view too, matching List view — previously the badge, and the "No rules defined" state for a scorecard with no rules, only appeared in List view.

"Create Scorecard" now requires at least one rule

The scorecard creation form previously let you create a standard with no rules and no warning, producing a scorecard that could never evaluate anything. "Create Scorecard" is now disabled until you've added at least one rule.

More dialogs opened from a button now return focus to that button on close

Closing more dialogs across the app — including creating entity/relationship kinds (directly or from a template), deleting entity/relationship kinds, adding or removing catalog relationships, and saving, renaming, or deleting a saved search — via Escape, the × control, or Cancel now returns keyboard focus to the button that opened them, instead of dropping focus to the page body.

The rest of the app's dialogs now return focus to the button that opened them on close

Closing any remaining dialog across the app — including catalog and collection filters, creating a catalog entity, documentation sections and links, interfaces, Git integration webhook secret rotation, entity editing/deletion, entity kind fields and relationship kinds, and team membership/editing/deletion — via Escape, the × control, or Cancel now returns keyboard focus to the button that opened it, instead of dropping focus to the page body.

Dialogs opened from a button (not a menu trigger) now return focus to that button on close

Closing several dialogs across the app — including Create Team, delete confirmations on collections/scorecards/field definitions, and the field "Create from Templates" dialog — via Escape, the × control, or Cancel now returns keyboard focus to the button that opened them, instead of dropping focus to the page body.

Documented scorecard search clauses in the Search syntax help popover

The catalog's Search syntax help popover now shows an example of the scorecard:, score:, and level: clauses, so they're discoverable without hitting the ambiguity error first.

Fixed the entity detail Status panel's Created label overlapping or clipping its date at tablet widths

The entity detail page's Status panel no longer renders the "Created" label on top of its date value, or silently trims the date, at 768px-wide (tablet) viewports.

Fixed the entity detail tab bar overflowing at mobile widths

The entity detail page's tab bar (Overview, Documentation, Scorecards, and the rest) no longer overflows the screen at mobile widths with a clipped, hidden-off-screen tab — it now wraps onto additional rows so every tab, including Scorecards, stays visible and reachable.

Fixed unreadable entity identifier wrapping and title overlap on mobile

The entity resource identifier on the entity detail page (e.g. component://my-service) now wraps at natural / and - boundaries at mobile viewport widths instead of breaking character-by-character, and the entity title no longer visually overlaps the Edit/Trash buttons at narrow viewports.

Fixed a crash on the entity Scorecards tab

The entity detail page's Scorecards tab could fail to load when an unevaluated scorecard's scope query used certain search fields (e.g. hasDocs, interface, scorecard). It now loads correctly.

Entity Scorecards tab badge now shows the total scorecard count

The entity detail page's Scorecards tab badge showed how many scorecards weren't fully passing, which could be mistaken for the total scorecard count. It now shows the total, with a separate "N failing" indicator inside the tab for scorecards that aren't fully passing.

Fixed keyboard focus dropping to the page body after creating a collection

After creating a collection, keyboard focus now moves to the new collection's page heading instead of silently dropping to the page body.

Fixed keyboard focus dropping to the page body after creating a scorecard

After creating a scorecard, keyboard focus now moves to the new scorecard's page heading instead of silently dropping to the page body.

Fixed low-contrast primary buttons and badges

Primary-styled buttons and badges (e.g. "New Entity", the Enabled/Disabled scorecard status badge) now meet WCAG AA text contrast requirements.

Added a "Skip to main content" link for keyboard and screen-reader users

A "Skip to main content" link is now available at the top of every authenticated page, letting keyboard and screen-reader users bypass the sidebar navigation and header to reach the page content directly.

Fixed Create Scorecard form auto-focusing the wrong field

The Create Scorecard form now focuses Display name — the first required field — on load, instead of jumping ahead to the Scope query field.

Disabled scorecards no longer get stuck showing a stale "Errored" status

Re-enabling a scorecard now automatically re-checks it, the same way "Evaluate now" does — so an Errored status from before it was disabled clears itself instead of sticking around forever. While a scorecard stays disabled, its status banner now says plainly that it may be out of date rather than suggesting a retry that isn't happening.

Scorecard Report tab charts now expose their data to screen readers

The "Score distribution" and "Score trend" charts on a scorecard's Report tab now expose the numbers they plot to screen readers, instead of only the chart's axis labels.

Scorecard report chart and tables no longer clip on mobile

The Scorecard Report tab's Score distribution chart now shows all of its bucket labels, and the By owning team/By kind/Rule failures tables show every column on a stacked card per row, instead of clipping at phone-width viewports.

Fixed unreadable scorecard rules on mobile

Rule cards on a scorecard's Definition tab no longer wrap their query and description one character per line at phone-sized widths — the text now wraps normally and the row's action buttons move to their own line.

Fixed scorecard rule editor dialog not returning keyboard focus on close

Closing the rule editor dialog on a scorecard's Definition tab (via Escape, the × close button, or Save) now returns keyboard focus to the "Add Rule" or row "Edit" button that opened it, instead of dropping focus to the page body.

Fixed scorecard rule names overflowing on mobile

Scorecard rule names that are a single long unbroken word (e.g. a hyphen-chained identifier) now wrap instead of overflowing the row at phone-sized widths.

Scorecard rule weight percentages now always sum to 100%

The Rules list on a scorecard's Definition tab could show weight percentages that summed to slightly more or less than 100% (e.g. six equally-weighted rules each rounding up to 17%, totaling 102%). Percentages are now rounded together so they always add up to exactly 100%.

Scorecards list shows status fields without scrolling on mobile

The scorecards list now shows Scope, Rules, Enabled, and Updated on a stacked card per scorecard at phone-width viewports, instead of requiring a sideways scroll inside the table to see them.

Catalog search suggestions show full field descriptions on hover

Field-name suggestions in the catalog search box now show their full description in a native tooltip on hover, so a long description clipped by the dropdown's single-line row is no longer permanently hidden.

Fixed search syntax help examples being cut off on mobile

The catalog's Search syntax help popover no longer truncates long query examples with an ellipsis on narrow/phone-sized viewports — they now wrap onto multiple lines so the full example stays visible.

Fixed the search syntax help popover overflowing on mobile

The catalog's Search syntax help popover no longer overflows its card border on narrow/phone-sized viewports when an explanation contains a long unbreakable token.

Search syntax help popover now scrolls instead of overflowing on short screens

The catalog's Search syntax help popover now scrolls its own content when it doesn't fit the viewport, instead of overflowing past the bottom of the screen with no way to reach the rest on short/mobile viewports.

"Scorecard evaluations" now selectable as an outgoing webhook event type

The Create/Edit Webhook dialogs in Organization Settings now offer "scorecard.evaluated" alongside created/updated/deleted, so you can subscribe to scorecard result changes without editing a webhook's filters through the API directly.

Scorecards with no rules no longer show a misleading 100% pass rate

A scorecard whose rules were all removed after creation used to show a 100% pass rate and a fully-filled green progress bar everywhere, as if every in-scope entity had been checked and passed. It now shows an explicit "No rules defined" state on the Report tab, the Team detail page, and on each entity's Scorecards tab card instead.

Zero-rule scorecards now score entities as passing, not failing

A scorecard with no rules defined previously scored every entity in its scope 0/100 and reported them all as failing. It now scores every in-scope entity 100/100 with 0 of 0 rules failing — consistent with a standard that has nothing to fail — across the report, entity detail, and catalog search views.

New features

Enterprise plan

There's now an Enterprise plan for organizations that need more room than Pro: unlimited catalog entities, user limits set to fit your team, and priority support, on top of everything in Pro. You'll find it on the Pricing tab in organization settings. Get in touch from there and we'll set it up for you.

Improvements

Over-limit notice stays accurate

When your organization is over its catalog entity limit, the notice at the top of the Catalog page now reflects where you are right now. Delete back under the limit and it clears straight away. There's nothing to wait for.

Search box front and center

The global search trigger now sits in the middle of the top bar as a proper search box, instead of being tucked in among the action icons on the right. Same shortcut, same results, easier to find.

Search that opens where you click

The search palette now expands out of the search box in the header instead of popping up in the middle of the screen, so your eye stays where it was. Admins can also type "settings" to jump straight to Organization settings.

New features

See exactly what your plan includes

The Pricing page now shows your organization's current plan with the exact limits and features in effect for you. Plan cards read their numbers from the same source the product enforces, so what a card advertises is always what you get. And if your organization has negotiated custom terms with us, the values you see are your own, not the standard tier's.

Improvements

Settings pages fit their dialogs

The organization and user settings dialogs are roomier, and the pages inside them no longer scroll sideways on laptop screens. Tables tuck secondary details under the main column when space is tight, and show them in the expanded row instead.

New features

Start each day on your new Home page

Signing in now opens on Home, a single view of where your organization stands. A tile for each kind of entity shows how many you have, and clicking one takes you straight to that slice of the catalog. Beside it you get the entities that changed most recently and the teams you belong to, so you can pick up where things left off without hunting for them. Everything on the page is a shortcut into the catalog and team pages you already use.

Bug fixes

Atlassian team members now show their names and pictures

Teams synced from Atlassian used to list their members as long account identifiers, which made a roster hard to read. Each member now appears with the name and profile picture from their Atlassian account, and with their email when their profile shares it. Your existing teams update on their next sync, with nothing for you to do.

Improvements

AI agents get better guidance when they connect

When an AI assistant such as ChatGPT or Claude connects to your Componecat catalog, it now receives a short briefing on how the catalog is organized and the best order to use its tools, along with Componecat's name, icon, and version. Agents find the right component faster and are clearer about which actions change data. The connect guide now also covers ChatGPT step by step.

Bug fixes

AI agent connections no longer expire after a week

Registered AI agent integrations (such as a ChatGPT app or Claude connector pointed at the Componecat MCP server) previously stopped authorizing after about a week, failing with an "invalid client" error until the integration was set up again. Registrations are now stored durably and keep working indefinitely. An integration that had already hit the error needs to be re-added once; after that it stays connected.

Improvements

Teams show everyone on them, not just the people who have signed in

A team member no longer needs a Componecat account. When you sync teams from GitHub, GitLab, Atlassian, or Microsoft 365, everyone on the upstream team now appears on the roster, not just the handful of people who happen to have logged in. A team's size in Componecat is its real size.

People without an account are marked No account. They are there so you know who owns what and who to contact, and being on a team grants nobody any access. The moment someone signs up with a matching email, their entry links itself to their account and picks up their name and picture.

You can add someone by hand the same way. Add Member now takes a name and email for a person with no account, alongside the picker for existing users.

New features

Save a search you keep running

The slice of the catalog you check every morning no longer has to be rebuilt every morning. Saved, next to the filters on the catalog page, keeps the search you are looking at under a name and puts it one click away.

It keeps the whole search, not just the words: the query, every filter chip, the tree or list view, and the sort order. Opening one puts the page back exactly as you left it.

Saved searches are yours alone. Nobody else sees them, and two people can each keep a "My services" without treading on each other. Rename one, delete one, or update it to match what is on screen once you have tweaked the search it opened. That last option only appears when the page has actually moved on from what you saved.

Want to share a search instead of keeping it? That is what a collection is for.

Improvements

Filters and the search box are now the same thing

Click a filter and it appears in the search box as text. Take it off and the text goes with it. What the box shows is the whole search that ran, so a filter you built by clicking is also a worked example of the query language, ready to edit when you need an "or" that chips cannot express.

It reads the other way too. Type kind:service and Service ticks in the kind picker, because a filter you wrote by hand belongs on the control that owns it as much as one you clicked.

Filters now open in a dialog rather than pushing the results down the page, with a running count at the top so you can see what each choice leaves you. And if your organization defines a lot of fields, you pick the ones you want to filter by instead of scrolling past all of them.

Build a collection by clicking, not by typing a query

Collections are now put together with the same search you use everywhere else. Whether you are writing the query behind a dynamic collection or picking entities for a static one, Filters opens the catalog's filter dialog and every choice you make writes itself into the search.

Saved starts you from one of your saved searches, so a view you already worked out can become a collection the whole team can see.

The picker also understands the full query language now, so you can find what you are adding with the same expressions the catalog takes rather than typing names one at a time.

Improvements

A sharper install and a fixed app description

Installing Componecat to your home screen or desktop now shows a real description of the product instead of placeholder text, and the app's icon and splash colours are drawn from the same brand definition as componecat.ai and the documentation site — so all three look like one product.

Bug fixes

AI agents connect reliably on first try

Connecting an AI agent such as Claude Code, Claude.ai, Cursor, or VS Code to the Componecat MCP server no longer fails intermittently with a "Session not found" error right after connecting. Connections now succeed on the first attempt.

Bug fixes

Connecting AI tools no longer stalls for multi-organization users

Approving an AI tool's access request could fail with an authorization error if you belong to more than one organization and hadn't picked one yet. In some cases the approval screen stayed blocked until you signed out. It now loads no matter which organization is active, and granting access still asks you to choose the organization it applies to.

Improvements

Search your whole member list

The Users screen in organization settings now searches your entire membership — by name or email, including people with invitations still pending — and pages through every member instead of showing only the first page.

Improvements

One-click install for the MCP server

Connecting an AI agent to your catalog is now a single click. The connect guide has install buttons for VS Code and copy-paste setup for Claude, Cursor, and other clients. A new bridge package also supports clients that cannot connect to remote servers directly.

Complete MCP tool annotations

Every tool on the MCP server — including global search — now declares its full behavioral annotations (read-only, destructive, open-world), so AI agents and directory reviews see exactly which tools only read your catalog and which ones change it.

New features

Keep any catalog search as a collection

Any question you can ask the catalog, you can now keep. A dynamic collection is written in the same query language as the search box, so it can finally express what the old filter form could not: an OR across kinds, a NOT on a tag, a date range, or a comparison on one of your own fields.

Picking a collection kind up front is gone. What those kinds did is now something you type. Use interface:mcp for the entities publishing an MCP server, hasDocs:true for the ones carrying documentation, and both together with everything else in a single expression. Those four new fields, interface, interfaceVisibility, protocol, and hasDocs, work in the catalog search box too.

The collection editor is the catalog's own search box, with the same field suggestions and syntax help, above a live preview of exactly which entities the collection would contain as you type. A collection's page shows its query and links straight back into the catalog with it loaded, so widening a collection and saving the result as a new one takes seconds.

Your existing dynamic collections keep working. Each one's filter is rewritten as the query that selects the same entities.

Ask the catalog a real question

Search now understands more than words. Type lifecycle:production AND (language:go OR language:rust) AND NOT tag:deprecated into the search box and you get exactly that. You can filter on any built-in or custom field, combine those filters with AND, OR, NOT and parentheses, and use comparisons like replicas:>=3, date ranges, wildcards, and tests for whether a field is set at all. Plain words still work exactly as before, and you can mix the two.

The search box suggests field names as you type, carries a syntax reference, and tells you precisely where a query went wrong instead of quietly returning nothing. Filter chips and expressions work together, and one click rewrites your active filters as a query you can refine.

The same expression works everywhere the catalog does, including the REST API and the MCP tools your AI agents use, so an agent can ask in one call what used to take several.

Improvements

See who's asking before you approve access

When an AI agent or third-party tool asks to connect to your Componecat organization, the approval screen now shows the client's registered name instead of an opaque identifier. You can tell what you are authorizing before you grant it. "Cookie settings" has also moved from the sidebar's app-info popover into your account menu, alongside your other personal settings.

One catalog, however you look for things

Browse and Search were separate screens that did the same job, and only one of them had the good search. They are now a single Catalog page. Open it and you see your whole catalog; start typing and it narrows. Facet counts, the query language, documentation matches, and relevance ranking are there the whole time, not just after you switch screens.

A toggle switches between the hierarchy tree and a ranked list, and your choice sticks and travels in any link you share. Filtering no longer flattens the tree — matches stay where they belong, with any parent that did not match shown dimmed above them, so you can still see where something lives.

Results are properly paged now, so a search that finds 312 things lets you reach all 312 rather than showing 25 under a count of 312. You can also sort the list by relevance, name, or most recently updated. Old /search links still work.

New features

Ask Componecat how Componecat works

Componecat's product documentation is now searchable from inside the app and readable by your AI agents. Press Cmd/Ctrl+K and a Documentation group appears alongside your catalog results. Search "descriptor" or "team sync" and jump straight to the section that answers it. Your catalog still ranks first, so searching for one of your own services finds the service. Agents connected over MCP can read the same pages, so they can walk you through connecting an integration or writing a descriptor file instead of guessing.

Search the whole catalog from one palette

Search just got faster to reach and smarter about what it finds. Press / or Ctrl/Cmd+K from anywhere to open the search palette, jump straight to app pages, and find catalog entities by name — with typo tolerance so a near-miss still lands. The same search now powers the API and AI-agent surfaces, so assistants find entities the same way you do.

Improvements

Search results are easier to scan

Catalog results in the search palette are easy to scan again: each entity shows its kind icon and color, its reference, and the part of the name that matched your query — the same at-a-glance styling you get in the catalog list.

Bug fixes

Signing out now ends your single sign-on session

When your organization signs in through its own identity provider, signing out now ends that session too. Before, you could be returned to the app still signed in. If your sign-in setup expects a different logout address, an administrator can point Componecat at it.

Your primary email address now shows correctly

If your account has more than one email address, for example after you also start signing in with a social account, the app could show an older address instead of the one you set as primary. It now uses your primary address everywhere and keeps up when you change it.

Team syncing from GitHub works from the app

Setting up team syncing on a GitHub integration now asks for the GitHub organization to sync, so your GitHub teams and their members flow into Componecat without a trip through the API. Existing GitLab, Atlassian, and Microsoft team syncs are unchanged.

This release includes behind-the-scenes maintenance and reliability improvements.

New features

See what's new right inside the app

The app now has a changelog. Your version number in the corner opens the full history of what's changed, and a What's New note appears whenever there are updates since your last visit, so you never miss an improvement.

Improvements

Cleaner JSON and YAML field values

Custom field values that hold JSON now open already formatted, so they are easy to read at a glance instead of crammed onto one line. Switching a value between JSON and YAML stays smooth and keeps its expandable view, and the format switch now sits neatly in the corner of the field.

Bug fixes

JSON fields show up properly in entity YAML

When an entity's descriptor is shown or exported as YAML, custom fields that hold structured JSON now appear as proper nested YAML instead of a single quoted string. Whole numbers stay whole numbers too, so a value like 3 no longer turns into 3.0.

New features

Connect Microsoft Entra ID to sync Microsoft 365 teams

You can now connect Microsoft Entra ID (Microsoft 365) as an integration. Add your tenant and app credentials, and your Microsoft 365 groups and teams sync into the catalog as teams.

New features

Sync your teams from GitLab

You can now sync team membership from GitLab into the catalog. Connect GitLab and its teams flow in alongside the providers you already use.

Improvements

Jump to a synced team's source from its details page

A team that syncs from an outside provider now shows a link to where it's managed. Open the team's details page and click straight through to its source.

New features

Catalog every component in a monorepo

Componecat now finds every component defined anywhere in a repository, so a monorepo full of services gets cataloged completely instead of just its root. Each component syncs independently, links between components in the same repo resolve correctly, and a push only re-syncs what actually changed.

Improvements

Find and track monorepo components in the catalog

You can now filter the catalog by the repository a component came from. Each component's page links to its exact subdirectory in the repo and shows a sync status panel, so you can see where it's defined and whether its last sync worked.

Bug fixes

Deep links into settings stay open

Opening a settings dialog from a deep link no longer closes on its own a moment later while the catalog loads its filters. The link now takes you straight there and stays put.

Bug fixes

Audit log shows a clear source for automated changes

Account changes synced from your identity provider now appear in the audit log with a clear source instead of 'Unknown user,' and they link straight to the record they affected. This shows in both the on-screen log and the CSV export.

This release includes behind-the-scenes maintenance and reliability improvements.

Bug fixes

New organizations get their plan set up right away

A new organization now has its plan applied the moment it's created, and a subscription update that arrives right as the organization is being set up is no longer missed. Your plan is in place from the start.

Improvements

See premium features and upgrade right from settings

Features that need a higher plan now stay visible in Organization Settings instead of disappearing. You can see what each one does and which plan unlocks it, with an Upgrade button that opens your pricing options directly. If you've downgraded, your existing data stays visible as read-only.

Bug fixes

AI agent consent screens show what you're granting

When you connect an AI agent through the authorization and device sign-in screens, they now list the access categories you're granting instead of coming up empty. You can review and pick exactly what to allow.

This release includes behind-the-scenes maintenance and reliability improvements.

This release includes behind-the-scenes maintenance and reliability improvements.

This release includes behind-the-scenes maintenance and reliability improvements.

Improvements

Send and review feedback in one place

Submitting feedback and reviewing past submissions now live together in the feedback dialog. Your submitted feedback appears as a tab right where you send new feedback, instead of on a separate settings page.

New features

See and compare plans right in Organization Settings

A new Pricing tab in Organization Settings shows the Free, Basic, and Pro plans side by side and marks the plan you're on. Choose a different plan to start upgrading or changing your subscription without leaving your settings.

Improvements

Your data stays visible after a plan downgrade

If you downgrade to a plan that no longer includes a feature you were using, such as service accounts, integrations, or outgoing webhooks, your existing data stays visible in read-only mode instead of disappearing. Features you never used stay hidden.

This release includes behind-the-scenes maintenance and reliability improvements.

This release includes behind-the-scenes maintenance and reliability improvements.

This release includes behind-the-scenes maintenance and reliability improvements.

This release includes behind-the-scenes maintenance and reliability improvements.

This release includes behind-the-scenes maintenance and reliability improvements.

This release includes behind-the-scenes maintenance and reliability improvements.

This release includes behind-the-scenes maintenance and reliability improvements.

This release includes behind-the-scenes maintenance and reliability improvements.

This release includes behind-the-scenes maintenance and reliability improvements.

Improvements

New organizations start with a Default team

Every new organization now comes with a Default team already set up, so you can start cataloging entities right away instead of creating a team first.

Improvements

Premium features are now tied to your plan

Integrations, outgoing webhooks, service accounts, import and export, and the REST API are now organized by plan. Basic includes import and export plus the REST API, and Pro adds integrations, outgoing webhooks, and service accounts, so it's clear what each plan unlocks.

Bug fixes

Settings dialogs stay open as you switch sections

Moving between sections in Organization Settings or User settings no longer closes the dialog by accident. It stays open until you close it yourself.

Smoother, more reliable sign-in and sign-up

Signing up now sends a single verification code instead of two, so the code you receive always works. The sign-in and sign-up form also stays steady as you move through each step.

Improvements

Manage your organization from one settings dialog

All of your organization's admin tools now live in one Organization Settings dialog, opened from the org switcher, instead of a separate sidebar group. Users, access tokens, integrations, audit log, import and export, trash, and more are all in one place.

Personal access tokens now work across all your orgs

You can now see and manage your personal access tokens across every organization you belong to, not just the one you're currently in, and each token shows which organization it belongs to.

See pending invitations in your member list

Your organization's member list now includes people you've invited who haven't set up their account yet, so you can tell who's still pending. They don't appear in the team member picker until they accept the invitation and set up their account.

This release includes behind-the-scenes maintenance and reliability improvements.

This release includes behind-the-scenes maintenance and reliability improvements.

This release includes behind-the-scenes maintenance and reliability improvements.

This release includes behind-the-scenes maintenance and reliability improvements.

Improvements

Clearer, safer catalog tools for AI assistants

AI assistants working with your catalog now get clearer results. Looking up an entity that doesn't exist returns a plain not-found message, team lists page through correctly, and an assistant can only remove a relationship between entities you're allowed to edit.

This release includes behind-the-scenes maintenance and reliability improvements.

This release includes behind-the-scenes maintenance and reliability improvements.

Improvements

One consistent set of access scopes for your tokens

Access tokens now use one simple set of scopes across the REST API and AI assistant connections. Grant a token access to entities, teams, or schema and it behaves the same way everywhere.

Bug fixes

Connecting an AI assistant reaches the approval screen reliably

When you connect an AI assistant or another tool, you now reach the access approval screen reliably instead of occasionally landing on a not-found page partway through.

This release includes behind-the-scenes maintenance and reliability improvements.

This release includes behind-the-scenes maintenance and reliability improvements.

Improvements

Keep paid features through the end of your billing period

When you schedule a plan downgrade, your paid features now stay available until the end of your current billing period instead of switching off right away.

Improvements

Clearer tool labels for AI assistants

Every catalog tool an AI assistant can use now carries a clear title and behavior labels. Assistants can discover and use them more reliably, including through AI assistant directories.

Improvements

See your organization's icon across the app

Your organizations now show their icon next to the name in the organization switcher and on the organizations page. When there's no icon, you'll see initials instead.

Improvements

Sign in and land right where you work

After you sign in, Componecat takes you straight to the right place in a single step. If you belong to one organization you go to its catalog, if you have several you resume your last one, and otherwise you land on the organization picker.

This release includes behind-the-scenes maintenance and reliability improvements.

This release includes behind-the-scenes maintenance and reliability improvements.

This release includes behind-the-scenes maintenance and reliability improvements.

This release includes behind-the-scenes maintenance and reliability improvements.

New features

Connect your Git and Atlassian tools with Integrations

You can now connect Componecat to your source control and Atlassian accounts. Scan repositories to catalog services automatically, sync your teams, and keep documentation in step.

Bug fixes

Catalog filters stick on refresh and shared links

Filtering the catalog by kind now stays applied when you refresh the page or open a filtered link. The filter and the results no longer fall out of sync.

New features

New ways to connect tools and automation to your catalog

You can now create service accounts to give scripts, tools, and AI agents their own scoped access to your catalog, alongside personal access tokens. Every credential is re-checked on each request, so you stay in control of what it can reach.

This release includes behind-the-scenes maintenance and reliability improvements.

This release includes behind-the-scenes maintenance and reliability improvements.

New features

Export and import your catalog

You can now move your catalog in and out of an organization. Admins can download the catalog and its schema as a single archive, then import it to copy content into another organization or restore a backup. Choose exactly what to include across schema, teams, entities, relationships, and collections, and preview everything before an import is applied.

This release includes behind-the-scenes maintenance and reliability improvements.

This release includes behind-the-scenes maintenance and reliability improvements.

This release includes behind-the-scenes maintenance and reliability improvements.

Bug fixes

A smoother start after you create a workspace

After you create a new workspace, you're now taken straight into its catalog instead of landing on an empty screen and having to refresh.

This release includes behind-the-scenes maintenance and reliability improvements.

This release includes behind-the-scenes maintenance and reliability improvements.

This release includes behind-the-scenes maintenance and reliability improvements.

This release includes behind-the-scenes maintenance and reliability improvements.

New features

Send feedback without leaving the app

You can now report bugs and request features right from the app. A feedback dialog in the header lets you send what you need, and admins get a list to review everything that comes in.

This release includes behind-the-scenes maintenance and reliability improvements.

This release includes behind-the-scenes maintenance and reliability improvements.

New features

Set up single sign-on for your organization

Organizations can now connect single sign-on. A new connections tab under organization settings lets you link your identity provider so your team signs in with the accounts they already have.

Create personal access tokens for programmatic access

You can now generate personal access tokens from your settings to authenticate with the API.

New features

Manage Git-synced documentation through AI agents

AI tools connected to your catalog through its MCP server can now set up and manage Git-synced documentation from start to finish, including listing, updating, removing, and syncing it. This used to be possible only in the app.

Improvements

Create entities with their required fields in one step

When an AI tool creates a catalog entity through the MCP server, it can now fill in the entity's required custom fields in the same step instead of a separate follow-up. It also gets a clear message when a required field is missing.

Bug fixes

Cleaner rendering for documentation synced from Git

Documentation pulled in from a Git repository no longer shows its metadata block as a stray heading at the top of the page.

This release includes behind-the-scenes maintenance and reliability improvements.

Bug fixes

Set custom field values on entities through the API

Creating or updating a catalog entity through the API now accepts your custom field values instead of rejecting the request. The entity's field data is also returned as a single object keyed by field, matching what you send.

This release includes behind-the-scenes maintenance and reliability improvements.

New features

Keep an activity log on your catalog entities

You can now turn on an activity log for a kind of catalog entity to record and review a running history of what has happened to it. Set how long entries are kept and older ones expire on their own. The log is available across the app, the API, and connected AI tools.

Improvements

Entity links in docs and activity now open the entity directly

References to another entity written inside your documentation or activity entries now open that entity directly, instead of running a search for it.