Skip to content
AgentknockAgentknock Docs

Bugs and feature requests

Use GitHub issues to report incorrect behavior or propose a change. Search existing issues first; add relevant details to an existing report when it describes the same problem.

For a problem involving several components, start with the component where you see the failure and include their versions or revisions. Report suspected vulnerabilities through Report a security issue.

Report a bug

Section titled “Report a bug”

Check Troubleshooting for a known explanation or fix. If the problem remains, include:

  • What you tried, what you expected, and what happened instead.
  • The smallest set of steps or commands that reproduces the problem.
  • The relevant versions: agentknock --version for the CLI and Settings → About Agentknock for the app’s version and build number.
  • For skill or plugin problems, the agent host, how you loaded the skill, and its Git commit or the date you obtained that copy, when known. The repository uses Git revisions rather than numbered releases.
  • The operating system and version, CPU architecture, and whether the CLI runs in WSL, a container, or a remote environment.
  • The exact error message and relevant output. For delivery problems, mention whether opening the app or refreshing Requests changes the result.

Issues and their attachments are public. Reproduce with test values, and remove credentials, pairing data, and unrelated personal information from commands, logs, and screenshots before sharing them. Don’t attach the CLI’s pairing file or a copy of the app’s storage.

Propose a feature

Section titled “Propose a feature”

Describe the task you want to accomplish, how you handle it today, and where the current behavior falls short. Explain the outcome you need; a proposed implementation is optional.

Contribute code or a reproduction

Section titled “Contribute code or a reproduction”

Read the CLI contribution guide, Android contribution guide, or skill and plugin contribution guide before preparing code. All start changes with an issue so the problem and design can be discussed together.

For each component, a pull request linked to an issue can demonstrate a prototype or reproduce a bug. Maintainers write the final implementation and close supporting pull requests without merging them.