Get help & give feedback

Community support

Use the Starter Kit repository to inspect source and existing issues. Search for the error before opening a new issue. Include only the minimum reproducible information.

Pro support

Pro 1.1.0 is private-access-only and provides self-service documentation without an SLA. Use these guides first. For a package-specific issue, return a sanitized report through the authorized channel that supplied your package, following its support instructions. No public mailbox or response-time commitment is offered here. Academy plan delivery is intended, but no live Academy support workflow is claimed.

Report a documentation issue

Prepare this short report for the appropriate package support channel or the person reviewing the docs:

Page URL and heading:
Edition and installed version:
Package/installer version:
Operating system and agent/version, if relevant:
What I tried:
Expected result:
Actual result and sanitized error:
Smallest reproducible example:

If you are reviewing this local site, share the page URL and correction with your reviewer. No feedback form here submits or stores information.

Protect private information

Do not attach the entire vault, credentials, unredacted logs or personal information. For a security issue, use the repository’s private reporting channel only if it is enabled, or an established private contact. Do not post sensitive reproduction details publicly.

Known limits and compatibility

• Agent adapter generation does not prove a working session in every provider version. Record and exercise your own combination using compatibility and verification.
• The Pro 1.1.0 guided workflow is qualified on Windows; see upgrade guidance for the macOS/Linux boundary.
• Existing-vault inspection does not guarantee arbitrary Obsidian plugin or link behavior. Review Community conflict handling and the Pro source matrix.
• Transaction backups cover installer changes. They are not complete vault snapshots, and later edits can prevent full rollback. Follow backup and recovery.
• A local package lifecycle does not establish a hosted marketplace or entitlement to another package. Check Power-Up boundaries.

Common questions

Does KOS train the model on my vault? No. These workflows use files as context for the selected tool. Provider data handling depends on that tool’s configuration and terms.

Do I need Pro for skills or Power-Ups? Not generally. Community has a local package lifecycle; individual packages can have separate requirements.

Does saving a file approve it? No. Review, approval and activation are distinct from storage.