cabbageaudio.com valid
Cabbage 3
Cabbage 3 is a framework for audio software development. Instruments are written in Csound 7, interfaces are described in JSON or built with HTML, CSS and JavaScript, and plugins are exported as VST3, CLAP or AU from VS Code.
For agents: Cabbage 3: framework for building audio plugins with Csound 7, HTML/JS interfaces, exported as VST3, CLAP or AU from VS Code; full and abridged docs.
audio pluginscsoundvst3clapaudio software framework
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-21T20:04:27.533Z. Cached copy · Source on cabbageaudio.com
# Cabbage 3
> Cabbage 3 is a framework for audio software development. Instruments are written in Csound 7, interfaces are described in JSON or built with HTML, CSS and JavaScript, and plugins are exported as VST3, CLAP or AU from VS Code.
Important notes:
- These docs describe Cabbage 3. Its syntax is different from Cabbage 2: widgets are JSON objects inside a `<Cabbage>` section, and all names are camelCase. Cabbage 2 names such as `rslider` and `combobox` are now `rotarySlider` and `comboBox`.
- Cabbage 3 requires Csound 7 and is used through a VS Code extension, not a standalone IDE.
- The widgets that ship with Cabbage are for prototyping. Custom interfaces are built with web technologies and the Cabbage JS API.
## Documentation Sets
- [Abridged documentation](https://cabbageaudio.com/llms-small.txt): a compact version of the documentation for Cabbage 3, with non-essential content removed
- [Complete documentation](https://cabbageaudio.com/llms-full.txt): the full documentation for Cabbage 3
## Notes
- The complete documentation includes all content from the official documentation
- The content is automatically generated from the same source as the official documentation
Related sites
Other listed sites in Developer tools. See the whole category →
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| 0state.com | 0state | documentation Open source projects AI agents and MCP +1 | 61 | ✓ | |||
| docker.com | Docker Documentation | documentation DevOps and observability Developer tools +1 | US | 75 | ✓ | ✓ | |
| atlassian.com | Atlassian | documentation Developer tools Productivity +1 | 74 | ✓ | ✓ | ||
| getbootstrap.com | Bootstrap | documentation Open source projects Developer tools | 74 | ✓ | ✓ | ||
| pages.dev | Cloudflare Pages | documentation Infrastructure Developer tools | 73 | ✓ | ✓ | ||
| chatgpt.com | Codex | documentation Developer tools AI and machine learning | 72 | ✓ | ✓ | ||
| gitee.com | Gitee | documentation Developer tools Productivity +1 | CN | 72 | ✓ | ✓ | |
| gitlab.com | GitLab | documentation Developer tools Infrastructure | 72 | ✓ |
Machine-readable: GET /v1/resolve?q=cabbageaudio.com · GET /v1/domain/cabbageaudio.com · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage cabbageaudio.com, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for cabbageaudio.com:
1. POST https://agentwebmap.com/v1/sites/cabbageaudio.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://cabbageaudio.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/cabbageaudio.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/cabbageaudio.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.