# Make meta-data URL accessible from UI

**URL:** <https://forum.buildkite.community/t/make-meta-data-url-accessible-from-ui/4556>\
**Category:** Features Requests\
**Created:** [January 7, 2026, 3:11pm UTC](https://forum.buildkite.community/t/make-meta-data-url-accessible-from-ui/4556 "2026-01-07T15:11:05Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![0m1xa](https://avatars.discourse-cdn.com/v4/letter/0/5e9695/32.png) [@0m1xa](https://forum.buildkite.community/u/0m1xa)\
**Post date:** [January 7, 2026, 3:11pm UTC](https://forum.buildkite.community/t/make-meta-data-url-accessible-from-ui/4556/1 "2026-01-07T15:11:05Z")

</div>

Hello!  
It would be nice to have access to metadata directly from the UI by clicking on the button.  
Some of our pipelines are heavily dependent on metadata.

At the moment, to get access to such information, we need to open a new tab and use a URL like [https://buildkite.com/\<pipeline\_name\>/builds/\<build\_number\>/meta-data](https://buildkite.com/%3Cpipeline_name%3E/builds/%3Cbuild_number%3E/meta-data)

It would perfectly land next to the existing `Summary`, `Steps`, and `Annotations` without the need to open another tab.

---

<div class="post-metadata">

**Author:** ![Micheal](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.buildkite.community/micheal/32/1588_2.png) [@Micheal](https://forum.buildkite.community/u/Micheal)\
**Post date:** [January 7, 2026, 4:10pm UTC](https://forum.buildkite.community/t/make-meta-data-url-accessible-from-ui/4556/2 "2026-01-07T16:10:39Z")

</div>

Hi @0m1xa  
Welcome to the Buildkite community!  
I believe we have seen similar requests on this and I will raise this to follow up.  
In the meantime, I believe the workaround you can try here is to create a step that fetches all metadata keys and displays them as a build annotation using `buildkite-agent annotate`, which would then let the Metadata show up in the Annotations tabs without needing a separate browser tab  
Something like

```yaml
---
steps:
  - label: ":label: Set Metadata"
    command: |
      buildkite-agent meta-data set "env" "production"
      buildkite-agent meta-data set "version" "1.2.3"

  - label: ":label: Display Metadata"
    command: |
      {
        echo "## Metadata"
        echo ""
        for key in $$(buildkite-agent meta-data keys); do
          VALUE=$$(buildkite-agent meta-data get "$$key")
          echo " **$$key:** \`$$VALUE\`"
        done
      } | buildkite-agent annotate --style info --context metadata

  - label: ":label: Simple test Annotation"
    command: |
      buildkite-agent annotate "Hello! This is your regular annotation." --style success --context greeting

```

I also added another annotation(Simple test Annotation) just under the Metadata annotation to show how it can be differentiated as the “Context” for the annotation would be what helps differentiate them. You can also add the metadata step to [pipeline templates](https://buildkite.com/docs/pipelines/governance/templates) to re-use with other builds.
