FeaturesmacOS · Windows
Build your own modules for AyCode
A module brings a new skill to every agent in AyCode: one folder with a manifest, a small program and tests. It runs as its own program, talks to AyCode through a versioned API, and only gets what you allowed.
- A working module from “New module” in a minute
- SDK in one file, no dependencies, Node 18 or newer
- Permissions you confirm before it turns on
- Private, public and signed, or licensed
From idea to running module
Under Settings → Modules → New module AyCode writes a module that runs right away: the manifest aycode-module.json, a skill, a program with the SDK, and tests that run without AyCode. Allow it, turn it on, and mention it in a chat.
Permissions in plain words
Every module may use its own settings and storage. Reading notes, suggesting note changes, showing notices and seeing your projects are permissions the module asks for and you confirm; if an update asks for more, AyCode asks again. Permissions govern what AyCode hands a module, and the docs say plainly what they do not limit.
Sharing
A module packs into one .aymodule file. Private modules are just for you, public ones must be signed with your publisher key, and licensed ones check a licence key offline.
Questions and answers
Do I need AyCode’s source code to build a module?
No. The SDK and the module API are all you need, and the template that “New module” writes already runs.
Which languages can a module use?
The SDK is for Node. Any other language works through the protocol directly: AyCode hands the program the address and its key.
Try it on your own projects.
Free for macOS and Windows. Uses the agents and subscriptions you already have.