aps-cli

A lightweight command-line interface (CLI) starting point for building agent workflows using Autodesk Platform Services (APS) APIs. Designed to be extended (by agents) for specific workflows, it comes bare-bones by design.

How to Work with an Agent and this CLI

1. Build the CLI (follow steps below).
2. Log in (we recommend using SSA)
3. Define a task you would like the agent to do. Keep it small and simple at first. For example Get the most recent 10 issues from project X. Keep in mind: An agent can only do what the APS APIs support. Make sure your ask is possible by reviewing the APS Doc. To fast-track discovery you can simply ask How would you do X using the APS CLI, here are the docs: docs/README.md. Note: the local docs are not complete but include all the scripts on how to crawl new docs. You can also provide URLs to the live APS docs.
4. Grant the CLI needed access to the resources in your task.
5. Prompt the agent using this template:

Using the aps-cli, complete the following task:

<DESCRIBE-TASK>

<DESCRIBE-THE-BROADER-WORKFLOW-THIS-TASK-IS-PART-OF>

Resources:
<Hub/project URLs, item IDs, or names from ACC/Forma>

Expected output:
<Describe format — e.g. JSON to stdout, markdown table, summary paragraph>

Not all CLI commands needed for this task may be implemented yet. You have the ability to add and augment the CLI source code. Refer to the APS API documentation `docs/README.md`. Follow the guidance in `AGENTS.md` when changing the source code.

From here on, it's up to you to use your knowledge of how to work with coding agents. This repo is designed to fast-track you by providing a framework for the agent to work with, easy access to documentation, and guidance on how to test and self-improve. I wish you luck. If you end up creating a workflow that has value, consider starring this repo.

[BUILD OPTION 1] Open in a Dev Container

Open the repository in VS Code and run Dev Containers: Reopen in Container. Reference: containers.dev This workspace is configured in .devcontainer/devcontainer.json.

[BUILD OPTION 2] Local Build Requirements (Without Dev Container)

To build this project locally (without the provided dev container), install:

• Node.js 22+
• Git
• Bash-compatible shell (Linux/macOS terminal, or WSL/Git Bash on Windows)

Install TypeScript Compiler Globally

Install the TypeScript compiler (tsc) globally:

npm install -g typescript

Setup

1. Clone Agent Friendly APS Docs & Install

git clone https://github.com/adskdimitrii/aps-ai-friendly-docs docs
npm install

2. Configure & Log In

Option A — Interactive browser login (3-legged OAuth):

Register a Traditional Web App at the APS Developer Portal with:

• Callback URL: http://localhost:7482/callback

node src/index.ts configure --client-id <YOUR-CLIENT-ID> --client-secret <YOUR-CLIENT-SECRET>
node src/index.ts login

Option B — Secure Service Account (SSA - For OpenClaw-style agents using Autodesk Secure Service Account):

Register a Server-to-Server App at the APS Developer Portal

This creates a service account identity tied to your APS application. No browser login required — the CLI generates and signs JWT assertions automatically. Ideal for headless/automated environments.

node src/index.ts configure --client-id <YOUR-CLIENT-ID> --client-secret <YOUR-CLIENT-SECRET> --ssa

After running this command, COPY the SSA Email Address the CLI creates and save it for later.

3. Grant APS Access to Forma

Grant APS Access

Add your APS Client ID to your Forma Account

Grant SSA Access [OPTIONAL]

If using the SSA auth option, you must now grant the SSA Email Address access to Forma resources just like you would for a user. It's recommended to limit access to the lowest required level.

Using the APS CLI Manually

node src/index.ts --help

Teaching your Agent to Use the CLI

Edit the path in skills/aps-cli/SKILL.md to the full path on your local machine where src/index.ts is located. Tell the agent to learn this skill as aps-cli.

Design Philosophy

See DESIGN.md for a comprehensive overview of the design philosophy behind this CLI.

Pull Requests

Sure. As long as it's within the Design Philosophy.

Things we could improve:

• Configure & Login UX / AX (agent experience)
• ...

MIT License

See LICENSE for details.