Skip to content

Read the AI agent URL from config in ask_assistant #651

Closed

Description

@codebestia

Branch: Open your PR against dev. PRs targeting main are closed automatically.

Description:
The ask_assistant handler in socket/messaging.ts calls a hardcoded http://localhost:8000/chat, so the assistant only works when the agent runs on the same host. Add an AI_AGENT_URL setting to the validated config in config.ts and use it.

Acceptance criteria:

  • AI_AGENT_URL is part of the config schema, defaults to http://localhost:8000 in development, and is listed in .env.example
  • The handler builds the URL from config; no hardcoded host is left in socket/messaging.ts
  • The request has a timeout (for example AbortSignal.timeout), and a timeout emits the existing ask_assistant error to the client instead of hanging
  • Test: the mocked fetch is called with the configured URL

Activity

  1. jamz-dev commented on Oct 22, 2026

    @jamz-dev

    @jamz-dev has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    I’d love to work on this issue

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @jamz-dev to this issue.

  2. stephaniepez21-art commented on Oct 22, 2026

    @stephaniepez21-art

    @stephaniepez21-art has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hello Maintainer, I can fix this please assign.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @stephaniepez21-art to this issue.

  3. Calebstack commented on Oct 22, 2026

    @Calebstack

    @Calebstack has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hello Maintainer, I’d like to work on this issue. I’ll add AI_AGENT_URL to the validated configuration and .env.example, update ask_assistant to use the configured URL with timeout handling, and add tests verifying the configured endpoint and timeout errors. Please assign it to me.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @Calebstack to this issue.

  4. Sharon-dev-create commented on Oct 22, 2026

    @Sharon-dev-create

    @Sharon-dev-create has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    I’d love to help out with this issue. I’ve checked the current codebase/documentation and know exactly what needs to be updated to make this clearer. I will ensure everything aligns perfectly with your existing contribution guidelines.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @Sharon-dev-create to this issue.

  5. anumukul commented on Oct 22, 2026

    @anumukul

    @anumukul has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hi, I’d like to take this issue and can deliver a fix within 24 hours.
    I’ve worked on similar projects before and have relevant experience, so I should be able to handle this efficiently.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @anumukul to this issue.

  6. ayandipe commented on Oct 22, 2026

    @ayandipe

    @ayandipe has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hello maintainer,
    kindly assign issue to me for prompt resolution.

    Regards

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @ayandipe to this issue.

  7. tesleem-28 commented on Oct 22, 2026

    @tesleem-28

    @tesleem-28 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hello, I investigated the affected functionality and understand the changes needed to achieve the expected result. I can take this issue and ensure the implementation is reliable.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @tesleem-28 to this issue.

  8. drips-wave commented on Oct 22, 2026

    @drips-wave

    Congratulations, @anumukul! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.

    🧑‍💻 @anumukul: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

    Warning

    When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

    🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

    🌊 Happy Wave 🌊

  9. github-actions commented on Oct 22, 2026

    @github-actions

    Closed by #685, merged into dev.

  10. drips-wave commented on Oct 22, 2026

    @drips-wave

    This issue has been completed by @anumukul as part of the Stellar Wave Program's 10th Wave 🥳

    😎 @anumukul: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

    🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions