> ## Documentation Index
> Fetch the complete documentation index at: https://docs.alesta.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Signals

> Review Alesta remediation feeds and use their prompts, files, GitHub actions, and correction controls safely.

Signals turns verified findings into reviewable next-step material. A signal can explain that a website issue needs business input, a codebase change, or service access, then expose only the actions currently available for that feed.

Signals is separate from Analytics. Analytics contains the finding and its evidence; Signals contains a proposed way to move the work forward.

## Signal feed types

Alesta orders the main website-remediation families first:

* **Business input:** a prompt or list of facts that needs a person to clarify the business context;
* **Codebase:** a coding-agent prompt or GitHub issue artifact for repository work;
* **Service operations:** instructions or a runbook for work in hosting, DNS, CMS, or another service.

Other feed types can appear after these when the server makes them available.

## Open a signal

A signal starts as a compact row with a title, description, revision or issue count, and any follow-up status. Select the row to expand it.

Available actions can include:

| Action                           | Result                                                                       |
| -------------------------------- | ---------------------------------------------------------------------------- |
| View prompt or View instructions | Opens the exact server artifact for review                                   |
| Copy                             | Copies the artifact content and records the interaction when possible        |
| Download                         | Downloads the server-provided file with its original filename and media type |
| Improve                          | Re-runs the signal analysis using your correction                            |
| Dismiss                          | Hides the remediation feed from Signals                                      |
| Connect GitHub                   | Starts or repairs the GitHub connection required for an issue action         |
| Create GitHub issue              | Opens a confirmation flow for an external write                              |

The server can hide, disable, complete, or make an action unavailable. Read the reason shown beneath the buttons instead of assuming every feed supports the same controls.

## Create a GitHub issue safely

Creating an issue is an external write and requires explicit confirmation.

<Steps>
  <Step title="Open the signal">
    Expand a codebase signal and select **Create GitHub issue**. Connect or
    reconnect GitHub if prompted.
  </Step>

  <Step title="Choose an eligible repository">
    Select a repository from the list Alesta can access. Archived repositories
    and repositories with Issues disabled are not offered.
  </Step>

  <Step title="Review the immutable artifact">
    Read the exact title and body that will be sent. The preview is tied to the
    signal revision and content hash.
  </Step>

  <Step title="Confirm the external write">
    Select the confirmation checkbox, then choose **Create GitHub issue**.
  </Step>

  <Step title="Open the result">
    When successful, the feed shows the created issue number and a link to
    GitHub.
  </Step>
</Steps>

<Warning>
  Creating a GitHub issue does not change code, create a branch, open a pull
  request, or deploy anything.
</Warning>

If the result is unknown, check the selected repository before trying again. Reusing the same request identity protects against accidental duplicate issues.

## Improve a signal

Select **Improve** and describe what the analysis missed or got wrong. Alesta uses the correction as input to a new analysis revision. The current card can become superseded when the replacement arrives.

This is a model-backed workspace action and can require an eligible plan and credits. Only an active feed can accept a correction.

## Dismiss a signal

Dismissal removes the feed from Signals. It does not resolve, suppress, or change the issue in Analytics. Use dismissal when the remediation card is no longer useful, not as a substitute for fixing the underlying finding.

## Empty and unavailable states

* **No signals right now:** no active feed currently needs input or exposes a next step.
* **Signal feeds are not enabled:** the workspace does not have the feature enabled.
* **Permission denied:** ask a workspace Owner or Admin to review your access.
* **Could not load:** retry the feed; Analytics remains available separately.

## References

* [Panels, documents, and signals](/concepts/panels-documents-and-signals)
* [Workspace actions](/workspace/workspace-actions)
* [Integrations and permissions](/account/integrations-and-permissions)
* [Locked and unavailable actions](/troubleshooting/locked-and-unavailable-actions)