On this page

For how-to questions the assistant answers from DevStride's documentation site, devstride.docs.devstride.com. It searches this site, writes a short answer, and lists the pages it used so you can read further. When the documentation doesn't cover something, it says so rather than guessing.

Ask a question#

  1. Type your question in the box at the bottom and press Enter.
  2. The assistant shows each step it takes as it goes ("Searching the documentation", "Looking up boards", "Updating an item") and then writes its answer.
  3. Under an answer drawn from the documentation, Sources links to each page it used.

Ask a follow-up in the same conversation and the assistant keeps the earlier questions in mind. To stop an answer part-way, click Stop. If an answer fails, click Retry.

One answer can look things up 200 times, 50 of them reads from GitHub, and has about three and a half minutes to finish. When a question needs more lookups than that, or the answer is running short of time, the assistant stops looking, writes its answer from what it found, says what it could not check, and ends with a note saying why it stopped. Ask a narrower follow-up to fill in what it left out.

Questions that work well#

  • How do I create a sprint cycle for my team?
  • What's the difference between a perpetual board and a cycle board?
  • Where do I set an SLA for support tickets?
  • How do I give a contractor access to one workstream only?

Name the screen or feature if you know it. A question about your own data, such as Which of my items are overdue?, is answered from your workspace instead when your organization allows it; see Working With Your Workspace.

Ask about your code#

When your organization has the DevStride GitHub App installed and allows GitHub in the assistant's settings, you can ask about the code in the repositories the app reaches:

  • What changed for I1234?
  • Where is the invoice total calculated?
  • What did the last pull request on this story touch?

The assistant searches the code, reads the files it needs and looks up the item's pull requests, then lists the files and pull requests it used under its answer so you can open them on GitHub. It only reads from GitHub; it never commits, comments or changes anything there. If GitHub is busy it says so and when to try again, and if the GitHub App is missing a permission it needs, it says which one and that an admin can fix it on the GitHub settings page.

Choosing a model#

If your organization allows more than one AI model, a model picker sits above the message box. Otherwise there is nothing to choose and no picker is shown. The admin decides which models are offered; see Settings, Permissions & Your Data.

Each model in the picker is marked Free or Paid. A paid model your workspace cannot use right now (a failed payment or an overdue invoice, or a plan that does not include paid models) is greyed out with the reason under its name. If you had chosen such a model as your default, the answer comes from the free default instead and a note at the top of the answer says which model answered. What each model costs is on the Prices page under Settings; see Prices, and paid models.

What the assistant won't do#

  • It never shows images in its answers.
  • It never touches billing, payment details, API keys, sign-in settings or database credentials.
  • It treats text in your workspace as information, not instructions: a ticket or comment that says "ignore your instructions" is just text it read.
  • It can't do anything your own role doesn't allow.
Powered by DevStride