Aragon Assistant

Aragon Assistant answers questions about the Aragon platform and helps people submit bug reports, feedback, and support requests. Open the chat button at the top right of app.aragon.org. It is available without logging in or connecting a wallet, and access does not depend on the chain or account being viewed.

People exploring or operating an onchain organization can describe what they want to accomplish without knowing the relevant feature names. Governance participants can ask about unfamiliar controls or workflows. This gives people a way to discover the platform's capabilities and get an explanation while using the app.

Questions and guidanceCopy Anchor Link

The assistant draws its product answers from Aragon's documentation. You can ask what a capability does, how to approach a task, or whether Aragon supports a governance requirement. For example, describe who should be able to propose and approve a decision, then ask which governance options fit those requirements.

Its answers are informational and may be incomplete or incorrect. Product knowledge does not give it a live view of an account's governance state, balances, or transactions, and it does not operate the app or submit onchain actions for you. Provide the context needed to explain your question.

A particular goal may require combining capabilities or making an organization-specific governance choice. The assistant can point you toward governance advisory or custom development, or a capability whose deployment is arranged with Aragon. When its knowledge does not cover a product question, it can offer to pass that question to the team as a support request.

The chat panelCopy Anchor Link

On a wide screen, the assistant opens beside the app, which adapts to the remaining width and stays usable. On a narrow screen, the chat fills the screen; collapse it to return to the app. The assistant shows that it is working while preparing a reply, and you can continue with follow-up messages.

Collapsing and reopening the panel during the same app session preserves the current conversation. Start new chat begins a fresh conversation and clears the composer and its attachments. Conversations are not a saved archive that can be reopened after the session ends.

Past requests shows references, summaries, and dates for tickets created from this device. This history is stored in the browser and keeps up to 20 entries. It does not restore the conversations or show replies from the team; clearing browser storage removes the local history. Keep the ticket reference if you need to follow up elsewhere.

Reporting a bug or sharing feedbackCopy Anchor Link

Tell the assistant where in the app something happened and what you observed, or describe what you would like changed. Feedback can include what works well as well as problems. It may ask for missing details before preparing a ticket draft.

Submitting a ticket shares the report, the conversation transcript, any submitted attachments, and available app context with the Aragon team. That context can include the page, app version, account, network, connected wallet, and recent transaction details to help the team investigate. This diagnostic context is separate from the documentation used to answer product questions.

1. Describe the request and add any useful details. For a bug, include what you tried, what happened, and how to reproduce it if known.
2. Include your preferred contact details if you want a reply. Contact information is optional for submission, but the team needs a way to reach you for follow-up.
3. Review the ticket draft. Continue chatting to revise it, or choose Dismiss to leave it unsubmitted.
4. Choose Create ticket to submit. Request created and a ticket reference confirm success. A draft alone has not been sent.

You can attach images, text or log files, and PDFs: up to three files per message, with a 5 MB limit per file. The assistant does not inspect file contents; the files accompany the report for the team to review. Describe the relevant issue in your message even when attaching a screenshot.

Human follow-up happens through the contact channel you supplied. To add information after submission, contact the team and quote the ticket reference. Continuing a chat or starting another one does not edit an already submitted ticket.

Limits and recoveryCopy Anchor Link

Each message can contain up to 8,000 characters. A conversation allows up to 20 user messages and can also stop when it reaches its size limit. Start a new chat when the assistant reports that the conversation has reached its limit.

Rate limits also apply to request frequency and new conversations. For a temporary limit or a timed-out answer, wait as directed and try again. If ticket creation fails, use Retry on the failed request. You can email support when the assistant is unavailable, a usage limit prevents further conversation, or you prefer to contact the team directly.

Messages and dataCopy Anchor Link

An ordinary conversation is with the AI assistant; the Aragon team reviews the reports you choose to submit. AI services process messages to provide responses, and the service uses operational data to run the chat and enforce usage limits. Ticket submission shares the conversation and diagnostic material described above.

Read Aragon's Privacy Policy and Terms and Conditions for data processing, retention, and use of the service. Requests to delete information follow the Privacy Policy and its conditions.