Overview

The Andamio CLI is a command-line tool for managing course content and project tasks. Export modules for local editing, create on-chain task bounties linked to GitHub issues, import changes, and manage authentication — all without leaving your terminal.

Want an AI agent to drive it? The Andamio Dev skills package pairs the CLI with an agent so it can operate Andamio alongside you.

Full documentation

The Andamio CLI is open source, and the andamio-cli repo is the source of truth for the complete command reference and workflows: the README and the lifecycle guides for transactions, courses, and projects. The rest of this page is a quick orientation.

What You Can Do

Browse and Query

Authentication

Course Owner and Teacher

Two paths lead to the same decision. course teacher review accepts or refuses one submission in a single step — reach for it when you are reviewing by hand. teacher assessment build stops at the unsigned transaction so a person can see the decisions before approving them, which is what you want when a script or an agent proposed them. Pass --decision once per learner, or --decisions-file <path> for a cohort; signing and submitting stay separate steps (see Transactions), and andamio tx run still does the whole lifecycle in one go.

andamio teacher assignments list --course <id> returns each pending submission as Markdown in content.evidence_text, alongside the raw Tiptap document in content.evidence — read the first for the prose, the second to verify an on-chain commitment hash.

Project Owner and Manager

Learners and Contributors

CLI 1.0 scoped the tool to the Owner, Teacher and Manager roles — the people who author work and assess it. Enrolling in a module, submitting assignment evidence, committing to a task, and claiming a credential are not CLI commands.

That work happens in the Andamio app, which signs and submits it in one flow. If you are following a pre-1.0 tutorial and run andamio course student ... or andamio project contributor ..., the CLI will tell you the same thing and exit with code 4.

Transactions

Quick Start

# Install
go install github.com/Andamio-Platform/andamio-cli/cmd/andamio@latest

# Configure
andamio auth login --api-key YOUR_KEY
andamio user login

# List courses
andamio course list

# Export a module, edit locally, re-import
andamio course export <course-id> 101
vim compiled/my-course/101/lesson-1.md
andamio course import compiled/my-course/101 --course-id <course-id>

Scripting

--output json is the stable surface. Data goes to stdout, progress and errors go to stderr, and no command reads stdin or prompts — everything works without a TTY. Discover ids first, then use them:

COURSE_ID=$(andamio course list --output json | jq -r '.data[0].course_id')
andamio course modules "$COURSE_ID" --output json | jq -r '.data[].course_module_code'

Every failure carries an exit code and, under --output json, a matching kind field — both come from the same classification, so they never disagree. An empty result is not an error: a list command that finds nothing emits an empty collection and exits 0, which is what keeps "nothing to review" apart from "not permitted" and "service unreachable."

Run andamio help exit-codes for the full table, or read the Scripting section of the README.

Full Documentation

The comprehensive command reference and step-by-step workflows are maintained in the open-source repo, which is the source of truth:

• README — installation, authentication, every command, networks, output formats, configuration
• Transaction Lifecycle — the build → sign → submit → register → poll pipeline and recovery
• Course Lifecycle — create and manage courses end to end
• Project Lifecycle — create and manage projects and task bounties

One reference stays here in the docs: the Import Format for the outline.md / lesson-N.md files used by course import and course export.