This prompts for your API key (masked input), verifies it against the platform, and stores a named profile in ~/.config/codika/config.json.For non-interactive environments:
codika login --api-key cko_your_api_key_here
Verify your identity:
codika whoami
Output:
Organization: My CompanyKey name: dev-keyKey: cko_abc...xyzScopes: deploy:use-case, workflows:triggerExpires: 2026-12-31Profile: my-company
codika init my-first-automation --name "My First Automation"
This creates:
my-first-automation/ config.ts # Deployment configuration version.json # Version tracking (starts at 1.0.0) project.json # Platform project ID package.json # Dependencies (codika) tsconfig.json # TypeScript config for IDE support .gitignore # Ignores node_modules/ node_modules/ # Dependencies installed automatically workflows/ main-workflow.json # HTTP-triggered parent workflow scheduled-report.json # Schedule-triggered workflow text-processor.json # Sub-workflow (called by parent) skills/ main-workflow/SKILL.md # Agent skill for the HTTP workflow scheduled-report/SKILL.md # Agent skill for the scheduled workflow
The template includes three workflows demonstrating different trigger types (HTTP, schedule, sub-workflow), the mandatory Codika node pattern, and placeholder usage. It also includes two agent skills that describe how AI agents can interact with the triggerable workflows. Dependencies are installed automatically so the use case is immediately deployable.
Your use case already includes agent skills (created during init). After deploying, agents can download them:
codika get skills
Or download directly into a Claude Code project:
codika get skills --output .claude/skills
Any compatible coding agent (Claude Code, Cursor, …) auto-discovers the skills and knows how to trigger your workflows. See Agent Skills for the full story.