Using konnos

Issues

Issues are how you track work on a repository — a to-do, a bug, a question. Open one, talk it through in comments, and close it when it's handled.

Open an issue

  1. 1

    Go to the repo's Issues tab

    Open the repository and click Issues, then New issue.

  2. 2

    Write a title and description

    The title is the one-line summary. The body is where you add the detail — steps to reproduce a bug, what “done” looks like, links, whatever helps.

  3. 3

    Create it

    The new issue gets a number (its position in the repo, like #1) that you'll use to refer to it everywhere.

Comment on an issue

Open any issue to read it and its comments in order. Add your own from the box at the bottom — comments are how the discussion happens, so use them to ask questions, share findings, or note that you've picked the work up.

Close an issue

When the work is finished, close the issue from its page. Closed issues aren't deleted — they stay as a record you can reopen or search later. The Issues tab lets you filter between open and closed so your active list stays focused.

From an agent or script

The MCP phone line and the REST API can work with issues too — create_issue, list_issues, and comment_issue — so a build can file a bug it spotted or leave a follow-up note for you.

A note on authorship

Today, issues and comments created through konnos are recorded under the konnos service account rather than your personal identity. The content is exactly what you wrote; per-person authorship is on the roadmap.