Skip to main content

Tech Landscape shared Assistant conversations and catalog import fixes

· 3 min read
Venue.sh Team
Venue.sh Team
Venue.sh

Tech Landscape gives you one place to see which technologies your repositories use and where they overlap. You can also share an Assistant conversation with teammates in your organization and continue the thread from a frozen copy. Catalog import now handles repository display names that contain spaces.

Tech Landscape​

Tech Landscape in Venue.sh aggregates technology signals from your ingested repositories. You see a sorted list of technologies filter by one or more of them and browse repository cards that show what each repo uses.

  • Open the page - Choose Tech Landscape in the left-side navigation or open /tech-landscape. You can also use global search and type phrases such as "tech stack" "technologies" "languages" or "frameworks".
  • Permissions - You need the same catalog read access as for the rest of the software catalog. If you cannot browse the catalog Tech Landscape is not available to you.
  • Technology list - Technologies that differ only by letter case or spacing count as one entry. The label uses the most common spelling in your data.
  • Repository cards - Each card links to the catalog entity when one exists. When there is no entity the card still shows the repository name or remote identifier.
  • Filters - Selected technologies appear as chips so you can see what you filtered on and clear filters quickly.

On the Tech Landscape page the Assistant includes page context and starter prompts. You can ask which repositories use specific stacks. For example:

  • "Which repositories use TypeScript and React?"
  • "What are the most common technologies in our organization?"

See Tech Landscape and Assistant for full details.

Shared Assistant conversations​

You can share a conversation from the full Assistant page with up to 50 people in your organization. Sharing is useful when a teammate needs the same context you already explored with the Assistant.

  • Share - Open a conversation on the Assistant page and click Share. Pick teammates and confirm. You can remove access later from the same dialog.
  • Shared with me - Recipients open Conversations then the Shared with me tab. Each entry shows who shared it.
  • Read-only copy - Opening a shared conversation shows a frozen snapshot. New messages you send in your own chat do not change what the recipient sees.
  • Start from shared context - Recipients can click Start new conversation with this context. Venue.sh copies the messages into a new conversation they own so follow-up questions can use that history.
  • Your history - Conversations you shared show secondary text such as "Shared with N" in your history list.

Demo accounts cannot share or fork shared conversations.

See Sharing conversations in the Assistant docs.

Organization details for API clients​

GET /api/organization returns the organization id name and slug for the signed-in caller. The route accepts a session cookie a personal API key or an OAuth bearer token. OAuth-based clients can use it to show your organization name instead of only an internal identifier.

Fixes​

  • Repository import - Importing a repository whose display name contains a space (for example "Venue View") no longer fails during catalog registration. The entity keeps the display title and opens from the catalog as expected. See Importing repositories.