Make CLI agent examples clickable in README

[JayadityaGit]

The CLI agent examples (Claude Code, Codex, and Gemini CLI) under the 'About' section in README.md should be clickable links that redirect to their corresponding documentation pages (e.g., https://www.warp.dev/agents/claude-code, etc.).

[oz-for-oss]

@JayadityaGit

Here's what I found while triaging this issue:

The named CLI agent examples are currently plain text in the README, and the corresponding agent documentation pages are reachable. This looks like a straightforward README documentation improvement.

Maintainer details

I concluded that README CLI agent examples in the About section are plain text and should be linked to their corresponding agent documentation pages..

Triage summary

This is a documentation improvement request for the repository README. The About section currently says users can bring their own CLI agent and lists Claude Code, Codex, Gemini CLI, and others as plain text; the requested target pages for the three named agents resolve successfully.

Likely fix area

Update README.md so the named CLI agent examples in the About paragraph link to their corresponding agent documentation pages, while preserving the surrounding copy.

Reproducibility

High. The current README content is directly visible in the repository and no environment-specific reproduction is required.

Duplicate check

I checked the open issue list and recent closed issues for README/CLI-agent/clickable-link duplicates. I did not find two or more existing issues matching this exact request.

This is my automated analysis and may be incorrect. A maintainer will verify the details.

Powered by Oz

[oz-for-oss]

This issue has been labeled ready-to-implement and is open for contributions involving code changes. If you'd like to tackle it, feel free to open a pull request against this issue. You can also comment @oz-agent on this issue to have the bot draft an implementation PR automatically.

[oz-for-oss]

@kevinchevalier

I'm implementing this issue with no spec context.

You can view the conversation on Warp.

I created a new draft implementation PR for this issue.

Next steps:

• Review the implementation changes in the PR.
• Complete any manual verification needed for this issue before merging.

Powered by Oz

[kevinchevalier]

Thanks for the report.