How to Submit Feedback or Vote on a Feature Request on Saga Feedback

To submit feedback or vote on Saga Feedback, open sagahq.canny.io, log in, search the Feature Requests board for an existing item, then either upvote it or create a new request with a clear title and description. After posting, track the item as it moves through the Planned, In Progress, and Complete statuses shown on the board. This process applies to anyone with access to the Saga Feedback site; the page evidence shows a Log in link, so plan to sign in before posting or voting.

Before you start

• Access: The site is the public feedback board for Saga, powered by Canny. The page shows a Log in link, so an account is expected for posting and voting.
• Where to work: The main board is Feature Requests. A Roadmap heading and a Filters control are also present.
• What already exists: The board lists 95 items, so most common ideas may already be there. Searching first saves you a duplicate and adds your vote to the existing thread.

Step 1: Log in

Select Log in on the Saga Feedback page and complete sign-in. The page evidence confirms the login entry point but does not describe the sign-in methods, so use whatever option the login screen presents.

Step 2: Search the Feature Requests board first

Use the search on the Feature Requests board to look for your idea before posting. The board already covers a wide range of requests, including:

If your idea matches one of these, go to Step 3. If not, go to Step 4.

Step 3: Vote on an existing request

Open the matching request and add your vote. Voting on an existing item is the intended way to signal demand, and the board displays vote counts next to each request (for example, Offline mode shows 48 and iOS mobile app shows 38). Adding your vote to an existing thread keeps the signal concentrated instead of splitting it across duplicates.

Step 4: Create a new request

If no existing item covers your idea, create a new request on the Feature Requests board:

1. Title: State the capability in plain terms, in the style of existing items — for example, "Sortable tables" or "Version history."
2. Description: Explain the task you are trying to complete and why the current behavior falls short. Concrete use cases help the Saga team make informed product decisions, which is the stated purpose of the board.
3. Submit: Post the request. It will appear on the board with a vote count starting from your vote.

Avoid posting near-duplicates of existing items; search again with a different phrasing if you are unsure.

Step 5: Track status on the Roadmap

Requests move through three statuses visible on the board:

• Planned — accepted for future work. Examples on the board: "Ability to multi-select pages as tags in a collection from other collections" and "Mention collection as context in Saga AI."
• In Progress — actively being built. Example: "Saga AI search across your workspace."
• Complete — shipped. Examples: "iOS mobile app" and "Wrap code in codeblock."

Check back on your request's status rather than reposting it. The Filters control on the board lets you narrow the view, and the Roadmap section gives the consolidated status picture.

Common snags

• Posting without logging in: The board shows a Log in link; sign in first so your vote and request are recorded.
• Duplicating an existing request: With 95 items on the board, search before posting. If you find a close match, vote there instead.
• Vague titles: Compare with existing entries — short, specific titles such as "Comments" or "Callouts" are easier for others to find and upvote.
• Expecting a timeline: Statuses indicate stage, not dates. The board does not show delivery dates, so treat Planned as intent rather than a schedule.