Version 0.56.0

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.