Skip to main content

Package AI expertise with Agents and ask about delivery metrics

· 4 min read
Venue.sh Team
Venue.sh Team
Venue.sh

This release lets your organization define purpose-built Agents with custom instructions and capability bindings, select them from the Assistant, and ask delivery questions that the Assistant answers using live Development Insights dashboard data instead of invented numbers.

Define Agents for your team's workflows​

Agents in Venue.sh let you package repeatable AI expertise into organization-scoped assistants. Each agent has its own instructions, example prompts, and bindings to Venue tools, MCP server tools, and other agents.

  • Organization registry - Browse and search agents from Agents in the sidebar (under AI).
  • Custom instructions - Write what the agent does and how it should respond in plain natural language.
  • Capability bindings - Grant access to Venue tools, individual MCP server tools, or other agents. Use Add all to bind every tool from a server at once.
  • Templates - Start from a predefined template to pre-fill name, description, instructions, and example prompts.
  • Safety controls - Require human approval before the agent executes sensitive actions.
  • Lifecycle management - Move agents through Draft, Ready, Disabled, and Archived states. Duplicate, disable, or archive from the detail page.

Admins and Editors can create agents. Contributors, Viewers, and Demo users can browse them. Create, update, and delete actions are recorded in the Activity Log.

See Agents for setup details and example configurations such as an Atlassian-aware agent or a Kubernetes and Helm troubleshooting agent.

Select the right Agent in the Assistant​

The Assistant now supports agent selection alongside the general Venue.sh assistant.

  • Agent selector - Choose a ready agent from the Assistant header before or during a conversation.
  • Scoped tools - When you select an agent, the Assistant uses that agent's instructions and only the tools bound to it, including full MCP server tool access where configured.
  • Page context on AI pages - On supported AI pages (e.g., Agents, MCP Servers, Skills), use Add current page to context so the Assistant understands what you are viewing.

For example, select a DevOps agent and ask:

  • "Why is the payments-api pod crashing in staging?"
  • "Show me the Helm values for the checkout-service release in production."

Or ask the general assistant about your agent catalog:

  • "What agents are available in our organization?"
  • "Which agents have access to Jira tools?"

Ask the Assistant about Development Insights​

The Assistant can now answer delivery questions using live data from your organization's Development Insights dashboards. Answers are grounded in the same Grafana panel data you see in the UI, not invented metric values.

Three read-only tools cover the dashboards most teams use for delivery health:

  • DORA - Deployment frequency, lead time for changes, change failure rate, and recovery time.
  • Engineering Overview - Cross-provider delivery health across Jira and Git.
  • Engineering Throughput & Cycle - Throughput, quality, and cycle-time workflow metrics.

When you ask a delivery question, the Assistant calls the matching tool, applies filters such as project, time range, and DORA report year where relevant, and summarizes the returned panel data. The default time range is the last six months when you do not specify one.

Access follows your existing permissions: you need Development Insights read permission and Development Insights enabled for your organization.

Try asking:

  • "What is our deployment frequency this quarter?"
  • "How does our lead time compare to last month?"
  • "Summarize throughput and cycle time for the platform team."

Provider-specific Git dashboards (GitLab, GitHub, Bitbucket) are not available through Assistant tools in this release. Use the dashboard UI for those views.

Updated Assistant model lineup​

Venue.sh's built-in model catalog now includes newer Anthropic and OpenAI options, including Claude Opus 4.8, Claude Sonnet 5, and GPT-5.5 Pro. Your Venue administrator controls which models appear in the Assistant model dropdown through Settings > Assistant.

See Also​

  • Agents - Define agents with custom instructions and capability bindings.
  • Assistant - Ask questions about your catalog, documentation, repositories, and enabled integrations.
  • Development Insights - Enable and configure engineering metrics for your organization.
  • Dashboards - Filter, refresh, and explore your Development Insights panels.
  • MCP Servers - Register MCP servers whose tools you can bind to agents.