Step-by-step guide to making Cortex your own.
Click Fork on github.com/taskade/cortex. This gives you your own copy with all the starter content.
git clone https://github.com/YOUR_USERNAME/cortex.git
cd cortex
npm installEach file in agents/ is a standalone agent definition. To modify one:
- Open
agents/strategist.json(or whichever agent you want to change) - Edit the
descriptionfield — this is the system prompt - Update
commandsto match your use case - Change
name,avatar, andintroduction
To add a new agent:
- Copy
examples/agent-template.jsontoagents/my-agent.json - Fill in all fields
- Run
npm run validateto check
To remove an agent:
- Delete the file
- That's it
Projects in projects/ are structured knowledge. To modify:
- Open any project JSON file
- Edit the node tree content (see PROJECT-GUIDE.md for the schema)
- Keep the root structure intact — one top-level child with nested content
To add a new project:
- Copy
examples/project-template.jsonintoprojects/ - Replace the title and content nodes
- Set a descriptive avatar emoji
Flows in automations/ define automated processes. To modify:
- Open any automation JSON file
- Edit trigger settings (schedule, webhook schema) or action prompts
- See AUTOMATION-GUIDE.md for available trigger and action types
The app in apps/cortex.json contains a full React SPA. For small tweaks, edit the file contents directly. For major changes, use Taskade's Genesis editor.
npm run validateThis checks that all JSON files are valid and have the required fields.
npm run assembleThis produces cortex.tsk at the repo root — a single file containing your entire workspace.
- Go to your Taskade workspace
- Use the Import feature
- Select your
cortex.tskfile - All agents, projects, automations, and the app will appear
After importing, you can continue editing in Taskade's UI. When you want to export changes back:
- Use Taskade's Export to GitHub feature
- Push to your fork
- Your repo stays in sync with your live workspace
- Start by changing one thing, importing, and verifying it works
- Template files live in
examples/— they are not scanned by the importer - Validation runs in CI on every push — broken JSON will be caught automatically
- See GENESIS-101.md to understand how the four layers connect