Is this the right repo to report issue?

[kehao95]

Since the cli seem to be closed source.

The confluent part seem to be not feature complete yet?

(however my agent seem to reverse engineered it and found a workaround)

Summary of Discoveries

1. acli confluence CLI Status

Current capabilities (v1.3.13):

• acli confluence auth login - Authentication (OAuth web or API token)
• acli confluence auth status - Check auth status
• acli confluence space list/view/create/archive/restore/update - Space-level operations only

Limitations:

• No page-level commands - Cannot read, search, or create pages via acli
• There's a bug with the space list command - it throws "Activation id for cloudId null not found" error even when authenticated

Authentication methods:

• OAuth via browser (--web flag)
• API token (created at https://id.atlassian.com/manage-profile/security/api-tokens)
• Confluence and JIRA are authenticated separately

2. Credential StorageThe acli stores credentials in macOS Keychain:

• Keychain service name: "acli".
• Format: go-keyring-base64:.
• Can be retrieved with: security find-generic-password -s "acli" -w.
• To decode: strip the go-keyring-base64: prefix and base64 decode.

3. Confluence REST API Works

Since acli doesn't support page operations, we can use the Confluence REST API directly with the stored credentials:
Reading a page by ID:

curl -s -u "EMAIL:API_TOKEN" \
  "https://<>.atlassian.net/wiki/rest/api/content/PAGE_ID?expand=body.storage,version,title"
URL to Page ID extraction:
- URL format: https://<>.atlassian.net/wiki/spaces/SPACE/pages/PAGE_ID/Title
- The page ID is the numeric part in the URL (e.g., 5976785071)

Search API:

curl -s -u "EMAIL:API_TOKEN" \
  "https://SITE/wiki/rest/api/content/search?cql=type=page AND text~\"query\"&limit=10"

...