Echo Agents

Echo Agents connect Dradis to your configured LLM providers and extend the platform with AI-assisted capabilities. Each agent has a specific purpose and can be enabled or disabled independently. Enable an agent and assign it a provider to start using its features across your projects.

To manage agents, as an Admin user, navigate to Tools › Echo in the navbar and select the Agents tab. You will see all available agents listed, along with their current status and assigned provider. Click Edit next to any agent to configure it.

Dradis Echo Agents page showing the Roslin agent

Roslin

Roslin is a writing assistant that provides two independent capabilities:

  1. AI-assisted writing - summarize, rewrite, or adapt finding content for your audience using a configured LLM provider.
  2. Grammar and spell checking - detect grammar and spelling errors inline as you work, powered by a local LanguageTool instance.

You can use either capability on its own. Grammar and spell checking does not require an LLM provider, and AI-assisted writing does not require LanguageTool.

Roslin currently works on Issues only. It isn’t available on Evidence, Notes, or Content Blocks.

Setting up LanguageTool

Grammar and spell checking requires a running LanguageTool server that Dradis can reach. The quickest way to get one running is with Docker:

docker run -d -p 8081:8010 erikvl87/languagetool

Once the container is running, confirm it is ready by visiting http://localhost:8081/v2/languages in your browser. You should see a JSON list of supported languages.

Personalizing LanguageTool

Pentest reports are full of terms LanguageTool won’t recognize out of the box — tool names, CVE IDs, client and target names, security jargon — and it will flag every one of them as a misspelling. LanguageTool supports personal dictionaries and other ways to cut down on this noise; see LanguageTool’s own guide on building a personal dictionary for how to add words and fine-tune which rules apply. This is configured on your LanguageTool server or account directly, not from within Dradis.

Configuring Roslin

On the Agents page, click Edit next to Roslin.

Edit Roslin form configuring provider and LanguageTool address

Enabling the agent

Use the Enabled toggle at the top of the form to turn Roslin on. The toggle must be enabled for the Roslin sidebar widget to appear on Issue pages.

AI-assisted writing

To use AI-assisted writing, you need at least one Echo Provider configured. Once a provider exists, select it from the Provider dropdown. If you want to use a different model than the provider’s default, enter it in the Model override field; leave it blank to use whatever model the provider has configured.

If you want grammar and spell checking but not AI-assisted writing, you can leave no provider configured and point only to a LanguageTool server.

Grammar and spell checking

Grammar and spell checking is configured with variables in the ENV Variables section of the form. Each variable is a row with a key on the left and a value on the right. To add a row, click Add variable. To remove one, click the X button at the end of the row.

Roslin uses two variables:

Key Value Default
LANGUAGETOOL_ADDRESS The base URL of your LanguageTool server http://localhost:8081
LANGUAGETOOL_LANGUAGE The language code to check against en-US

Click Update Agent to save your changes.

Setting the server address

Set LANGUAGETOOL_ADDRESS to the base URL of your LanguageTool server, the part that comes before /v2/. If you followed the Docker setup above, the value is:

http://localhost:8081

When entering the address:

  • Include the scheme. Start with http:// or https://, to match how your server is served. localhost:8081 on its own won’t work.
  • Include the port if the server doesn’t use the default port for its scheme (80 for http://, 443 for https://).
  • Don’t include the API path. Roslin adds /v2/check itself, so http://localhost:8081/v2 and http://localhost:8081/v2/check won’t work. If LanguageTool is served from a sub-path behind a reverse proxy, include that sub-path, for example https://tools.example.com/languagetool.
  • A trailing slash is optional. http://localhost:8081 and http://localhost:8081/ both work. Spaces before or after the address are ignored.

To check an address, add /v2/languages to the end and open it from the Dradis server, in a browser or with curl. If you get a JSON list of languages, the address is correct. Checking from your own computer isn’t enough, because Dradis connects to LanguageTool from the server.

To disable grammar and spell checking, keep the LANGUAGETOOL_ADDRESS row but leave its value blank. If you remove the row entirely, Roslin falls back to the default address, http://localhost:8081.

Choosing the language

By default, Roslin checks content against US English (en-US). To use a different language:

  1. If there’s no LANGUAGETOOL_LANGUAGE row in the ENV Variables section, click Add variable and enter LANGUAGETOOL_LANGUAGE as the key.
  2. Enter a LanguageTool language code as the value.
  3. Click Update Agent.

For example:

  • en-GB for British English
  • de-DE for German
  • auto to let LanguageTool detect the language of each field

See LanguageTool’s list of supported language codes. Your own server lists the languages it supports at /v2/languages, as described in Setting up LanguageTool. Use the value from the longCode field, for example en-GB.

The language applies to every Issue in every project. It can’t be set per project or per Issue.

Using Roslin in a project

Once Roslin is enabled, a Roslin widget appears in the sidebar on every Issue page.

Grammar and spell check

When you open an Issue, Roslin analyses the rendered content against LanguageTool and highlights any grammar or spelling errors with an underline. The sidebar widget shows a summary of the results:

  • No errors found — the widget collapses and shows a green check mark.
  • Errors found — a red indicator appears with a count (e.g. 3 issues found).

Click any underlined word or phrase to open a popover with the error description and one or more replacement suggestions. You can:

  • Apply a suggestion — click the replacement text to update the field and remove the underline.
  • Dismiss a suggestion — click the dismiss action to hide this specific match without making a change. Dismissed suggestions are stored in your browser and will not reappear when you reload the page.

Once all errors have been resolved or dismissed, the sidebar widget collapses and shows a green check mark.

When the grammar check fails

If Roslin can’t check an Issue, the Roslin widget shows the reason instead of a result:

  • LanguageTool server is not reachable. means Dradis couldn’t connect to LANGUAGETOOL_ADDRESS when the Issue page loaded. Check the address against Setting the server address. Dradis remembers the result for up to five minutes, so after you start the server, the message can take a few minutes to clear. Changing the address takes effect right away.
  • Could not reach LanguageTool. Is the container running? means Dradis couldn’t connect to the LanguageTool server. Check that the server is running and that LANGUAGETOOL_ADDRESS points to it.
  • LanguageTool error: ... followed by Check the Roslin agent settings. means the LanguageTool server rejected the request. The message shows the start of LanguageTool’s explanation. The most common cause is an unsupported LANGUAGETOOL_LANGUAGE code. See Choosing the language.

Next help article: Dradis Echo Prompts →

Seven Strategies To Differentiate Your Cybersecurity Consultancy

You don't need to reinvent the wheel to stand out from other cybersecurity consultancies. Often, it's about doing the simple things better, and clearly communicating what sets you apart.

  • Tell your story better
  • Improve your testimonials and case studies
  • Build strategic partnerships

Loading form...

Your email is kept private. We don't do the spam thing.