Skip to content

Comments

Manage Confluence page comments - footer comments, inline comments, replies, and resolution.

  • Authenticated profile (atlcli auth login)
  • Space permission: View to list comments, Edit to add/modify comments

Confluence supports two types of comments:

  • Footer comments - Appear at the bottom of the page
  • Inline comments - Attached to specific text selections

atlcli fully supports both types with CRUD operations.

Terminal window
atlcli wiki page comments list --id 12345

Options:

Flag Description
--id Page ID or page URL (required)
--comment Show only the thread of this comment
--json JSON output

A link to a comment (?focusedCommentId=…, as Confluence puts it in notifications and “Copy link”) shows that comment’s thread, the comment itself marked with ▶. Footer comments, inline comments and replies all work:

Terminal window
atlcli wiki page comments --id "https://acme.atlassian.net/wiki/spaces/DOCS/pages/10001/Design+Review?focusedCommentId=20002"
Comment 20002 on "Design Review"
────────────────────────────────────────────────────────────
• Ann Lee (11/12/2026)
Should we split this section?
▶ Bob Ray (11/12/2026)
Yes, see the API page.

With the page id, --comment does the same: atlcli wiki page comments --id 10001 --comment 20002. For an inline comment the thread starts with the text it is about (On: "important phrase").

With --json, the full comment list is returned with a focusedComment object added (found, kind, thread).

If the comment no longer exists (deleted, or not visible to you), the command says so and lists the page’s other comments instead of failing.

Terminal window
# Using positional argument
atlcli wiki page comments add --id 12345 "Great documentation!"
# From a file
atlcli wiki page comments add --id 12345 --file ./comment.txt

Options:

Flag Description
--id Page ID (required)
--file Read comment text from file
Terminal window
atlcli wiki page comments reply --id 12345 --parent 67890 "Thanks for the feedback!"

Options:

Flag Description
--id Page ID
--parent Parent comment ID to reply to
--file Read reply text from file

Inline comments are attached to specific text in the page content.

Terminal window
atlcli wiki page comments list --id 12345 --inline
Terminal window
# Match text in page and attach comment
atlcli wiki page comments add-inline --id 12345 --selection "text to match" "Consider rewording this"
# If text appears multiple times, use --match-index
atlcli wiki page comments add-inline --id 12345 --selection "common phrase" --match-index 2 "Comment on third occurrence"

Options:

Flag Description
--id Page ID
--selection Text string to match in page content
--match-index Which occurrence to match (0-indexed, default: 0)
--file Read comment text from file

Mark inline comments as resolved (for review workflows). Only inline comments have a resolved state in Confluence; footer comments cannot be resolved.

Terminal window
# Resolve an inline comment
atlcli wiki page comments resolve --comment 67890
# Reopen a resolved inline comment
atlcli wiki page comments reopen --comment 67890

atlcli reads the comment back after the update and fails if Confluence still reports the old state, so a reported success means the comment really changed.

Options:

Flag Description
--comment Comment ID
--type inline (default). footer is rejected: footer comments have no resolved state
Terminal window
# Delete footer comment
atlcli wiki page comments delete --comment 67890 --confirm
# Delete inline comment
atlcli wiki page comments delete --comment 67890 --type inline --confirm

Options:

Flag Description
--comment Comment ID
--type Comment type: footer (default), inline
--confirm Skip confirmation prompt

During docs pull and docs push:

  • Comments are not synced by default (they’re metadata, not content)
  • Use --include-comments to export comments alongside pages
  • atlcli preserves comment IDs in a .comments.json sidecar file when exported
Terminal window
atlcli wiki docs pull ./docs --include-comments

Creates files like:

docs/
├── my-page.md
└── my-page.comments.json
{
"pageId": "12345",
"comments": [
{
"id": "67890",
"type": "footer",
"body": "Great documentation!",
"author": "alice@company.com",
"created": "2025-01-14T10:00:00Z",
"resolved": false,
"replies": []
}
]
}

All comment commands support --json for scripting:

Terminal window
atlcli wiki page comments list --id 12345 --json
{
"schemaVersion": "1",
"comments": [
{
"id": "67890",
"type": "footer",
"body": "Great documentation!",
"author": {
"displayName": "Alice",
"email": "alice@company.com"
},
"created": "2025-01-14T10:00:00Z",
"resolved": false,
"replies": []
}
],
"total": 1
}
Terminal window
# List unresolved comments
atlcli wiki page comments list --id 12345 --json | jq '.comments[] | select(.resolved == false)'
# Resolve after addressing
atlcli wiki page comments resolve --comment 67890
Terminal window
# Export all comments from a space
for page in $(atlcli wiki page list --space TEAM --json | jq -r '.pages[].id'); do
atlcli wiki page comments list --id $page --json > "comments-$page.json"
done
Terminal window
# Check each page for unresolved comments
for page in $(atlcli wiki page list --space TEAM --json | jq -r '.pages[].id'); do
COUNT=$(atlcli wiki page comments list --id $page --json | jq '[.comments[] | select(.resolved == false)] | length')
if [ "$COUNT" -gt 0 ]; then
echo "Page $page has $COUNT unresolved comments"
fi
done
  • Pages - Page operations
  • Sync - Export comments with --include-comments
Jira and Confluence are trademarks of Atlassian Corporation Plc. atlcli is not affiliated with, endorsed by, or sponsored by Atlassian.