--- title: Build your own Octopus dashboards with llms.txt and an... description: A walkthrough of using Octopus Deploy's llms.txt file together with Claude Code to generate realistic test data and build three custom dashboards via the... canonical: https://daily.dev/posts/build-your-own-octopus-dashboards-with-llms-txt-and-an-ai-coding-agent-vrf8nxra5 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Build your own Octopus dashboards with llms.txt and an AI coding agent | daily.dev og:description: A walkthrough of using Octopus Deploy's llms.txt file together with Claude Code to generate realistic test data and build three custom dashboards via the... og:url: https://daily.dev/posts/build-your-own-octopus-dashboards-with-llms-txt-and-an-ai-coding-agent-vrf8nxra5 og:image: https://api.daily.dev/og/posts/VRF8NXrA5.png og:image:alt: Build your own Octopus dashboards with llms.txt and an AI coding agent og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Build your own Octopus dashboards with llms.txt and an AI coding agent **[OctopusDeploy](https://daily.dev/sources/octopusdeploy)** · 9 min read · 0 upvotes · 0 comments ## Summary A walkthrough of using Octopus Deploy's llms.txt file together with Claude Code to generate realistic test data and build three custom dashboards via the Octopus REST API: a tenant rollout board, a team health board, and a Sankey-style release flow diagram. The llms.txt file condenses API endpoints, request/response types, and deployment step properties into a single Markdown document the coding agent can parse, letting it construct API calls, seed a fictional multi-tenant company, and iterate using error messages when requests failed. The post also covers keeping API keys out of the browser via a small proxy script. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What is llms.txt and how does it help an AI coding agent use the Octopus Deploy API? Llms.txt is a plain Markdown convention published at /llms.txt that condenses API documentation into a single file an AI agent can read, similar to a README for agents. Octopus Deploy serves its own roughly 400 KB llms.txt with five sections covering authentication, space selection, endpoints, types, and deployment step properties, giving an agent enough context to construct valid API requests without reading full Swagger docs. _Developers wiring AI agents into existing APIs can compare llms.txt approaches and workflows on daily.dev._ ### How can I keep my Octopus Deploy API key safe when building a browser-based dashboard? Keep the API key server-side by routing dashboard requests through a small proxy script rather than embedding the key in the page. The proxy serves the static HTML and forwards any request under /api/ to Octopus, attaching the X-Octopus-ApiKey header itself, which also gives the browser a single origin for the page and its API calls, avoiding CORS issues. _Engineers building internal dashboards against vendor APIs can track key-handling patterns like this via daily.dev._ ### Which Octopus Deploy API endpoints are needed to build a tenant rollout dashboard showing how far behind each tenant is? Five endpoints suffice: GET /dashboard?showAll=true for current deployments per project, environment, and tenant; GET /projects/{id}/releases for the newest release per channel; GET /tagsets/all?scopes=Tenant for grouping tags; GET /tenants/variables-missing for tenants blocked by missing variables; and GET /interruptions?pendingOnly=true for deployments paused on approval. _Teams designing deployment visibility tooling can follow concrete API breakdowns like this through daily.dev._ ## Similar posts on daily.dev - [Octopus Easy Mode - Claude Agent](https://daily.dev/posts/octopus-easy-mode---claude-agent-foshisvte) · OctopusDeploy · 0 upvotes · 0 comments - [Agents grew up, so did our docs](https://daily.dev/posts/agents-grew-up-so-did-our-docs-rucdfhfyl) · Neon · 0 upvotes · 0 comments - [How to Make Your Docs Agent-Ready: llms.txt, Parity, MCP](https://daily.dev/posts/how-to-make-your-docs-agent-ready-llms-txt-parity-mcp-3ogzxkxif) · Prisma Blog · 4 upvotes · 1 comments --- Tags: [#ai-agents](https://daily.dev/tags/ai-agents), [#claude-code](https://daily.dev/tags/claude-code), [#rest-api](https://daily.dev/tags/rest-api), [#octopus-deploy](https://daily.dev/tags/octopus-deploy) [View this post on daily.dev](https://daily.dev/posts/build-your-own-octopus-dashboards-with-llms-txt-and-an-ai-coding-agent-vrf8nxra5) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Build your own Octopus dashboards with llms.txt and an AI coding agent","url":"https://daily.dev/posts/build-your-own-octopus-dashboards-with-llms-txt-and-an-ai-coding-agent-vrf8nxra5","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/build-your-own-octopus-dashboards-with-llms-txt-and-an-ai-coding-agent-vrf8nxra5"},"datePublished":"2026-10-02T08:02:17.121Z","dateModified":"2026-10-02T08:02:40.358Z","description":"A walkthrough of using Octopus Deploy's llms.txt file together with Claude Code to generate realistic test data and build three custom dashboards via the...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/95dba9339b1f84035a4d55d7aedda808?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/95dba9339b1f84035a4d55d7aedda808?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"OctopusDeploy","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"OctopusDeploy","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/71110ae886d64eac9f3a01496feb2bd8","url":"https://daily.dev/sources/octopusdeploy"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/build-your-own-octopus-dashboards-with-llms-txt-and-an-ai-coding-agent-vrf8nxra5","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ai-agents,claude-code,rest-api,octopus-deploy","timeRequired":"PT9M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"OctopusDeploy","item":"https://daily.dev/sources/octopusdeploy"},{"@type":"ListItem","position":3,"name":"Build your own Octopus dashboards with llms.txt and an AI coding agent"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/build-your-own-octopus-dashboards-with-llms-txt-and-an-ai-coding-agent-vrf8nxra5#faq","mainEntity":[{"@type":"Question","name":"What is llms.txt and how does it help an AI coding agent use the Octopus Deploy API?","acceptedAnswer":{"@type":"Answer","text":"Llms.txt is a plain Markdown convention published at /llms.txt that condenses API documentation into a single file an AI agent can read, similar to a README for agents. Octopus Deploy serves its own roughly 400 KB llms.txt with five sections covering authentication, space selection, endpoints, types, and deployment step properties, giving an agent enough context to construct valid API requests without reading full Swagger docs. Developers wiring AI agents into existing APIs can compare llms.txt approaches and workflows on daily.dev."}},{"@type":"Question","name":"How can I keep my Octopus Deploy API key safe when building a browser-based dashboard?","acceptedAnswer":{"@type":"Answer","text":"Keep the API key server-side by routing dashboard requests through a small proxy script rather than embedding the key in the page. The proxy serves the static HTML and forwards any request under /api/ to Octopus, attaching the X-Octopus-ApiKey header itself, which also gives the browser a single origin for the page and its API calls, avoiding CORS issues. Engineers building internal dashboards against vendor APIs can track key-handling patterns like this via daily.dev."}},{"@type":"Question","name":"Which Octopus Deploy API endpoints are needed to build a tenant rollout dashboard showing how far behind each tenant is?","acceptedAnswer":{"@type":"Answer","text":"Five endpoints suffice: GET /dashboard?showAll=true for current deployments per project, environment, and tenant; GET /projects/{id}/releases for the newest release per channel; GET /tagsets/all?scopes=Tenant for grouping tags; GET /tenants/variables-missing for tenants blocked by missing variables; and GET /interruptions?pendingOnly=true for deployments paused on approval. Teams designing deployment visibility tooling can follow concrete API breakdowns like this through daily.dev."}}]} ```