wso2 / wso2/api-platform

[Bug]: Malformed entry for the visible workflow in API Workflows section in llms.txt

Open
#3,111 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Aspect/UI Severity/Major Type/Bug
Dominant language
Go
Stars
71
Forks
111
Avg merge
1d 14h
Merged PRs (30d)
110

Description

Please select the area the issue is related to

Developer Portal

Please select the aspect the issue is related to

Aspect/UI (Frontend layouts, components, styling)

Description

In llms.txt's API Workflows section, the entry for the visible workflow is malformed:

Say the API Workflow name is Test;
It should read - /default/views/default/api-workflows/test.md - Test (or similar) — the link text is empty and the handle is missing from the URL, so the link gives a 404 as below. The adjacent APIs/MCPs sections in the same file render correctly - Catalog API v1.0(.../catalog-api-v1.0.md) — description), so this looks like a template bug specific to the workflow-list generator — likely the handle variable isn't being interpolated into that entry's URL/label. This would break agent discovery via llms.txt specifically (the api-workflows.md list endpoint is unaffected and works correctly).

Image
Steps to Reproduce

Go to https://localhost:9543/default/views/default/llms.txt and check for the API workflow section.

Or reach it from the admin UI: SettingsAI & DiscoveryLLM Instructions — there's a Preview pane there showing the same content, plus a small "open in new tab" icon next to it that links to this same URL.

Severity Level of the Issue

Severity/Major (Important functionality is broken. Should be prioritized. Doesn't need immediate attention)

Environment Details (with versions)

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by opening the llms.txt endpoint and comparing the API Workflows entry with the adjacent APIs/MCPs entries; trace the workflow-list generator or template that produces it. Done means each workflow has its handle in the URL and visible name or description, returns successfully, and the existing api-workflows.md endpoint remains unaffected; run or add the relevant generator test if one exists.

Written by the indexing model from the issue text.

Assessment

Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
62/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.