←back to thread

Phoenix.new – Remote AI Runtime for Phoenix

(fly.io)
638 points wut42 | 2 comments | 20 Jun 25 14:57 UTC | HN request time: 0.503s | source
Show context
chrismccord ◴[20 Jun 25 15:54 UTC] No.44328933[source]▶
Phoenix creator here. I'm happy to answer any questions about this! Also worth noting that phoenix.new is a global Elixir cluster that spans the planet. If you sign up in Australia, you get an IDE and agent placed in Sydney.
replies(21): >>44329010 #>>44329145 #>>44329199 #>>44329447 #>>44329669 #>>44329679 #>>44329692 #>>44329699 #>>44329766 #>>44330059 #>>44330099 #>>44330127 #>>44330670 #>>44331525 #>>44331688 #>>44334922 #>>44335271 #>>44336137 #>>44336958 #>>44337485 #>>44344757 #
miki123211 ◴[20 Jun 25 17:46 UTC] No.44330099[source]▶
1. What's your approach to accessibility? Do you test accessibility of the phoenix.new UI? Considering that many people effectively use Phoenix to write front-ends, have you conducted any evals on how accessible those frontends come out?

2. How do you handle 3rd party libraries? Can the agent access library docs somehow? Considering that Elixir is less popular than more mainstream languages, and hence has less training data available, this seems like an important problem to solve.

replies(1): >>44331554 #
1. chickensong ◴[20 Jun 25 20:06 UTC] No.44331554[source]▶
It seems like they're giving you lower level building building blocks here. It's up to the developer to address these things. Instruct the agent to build/test for accessibility, feed it docs via MCP or by other means.
replies(1): >>44334723 #
2. rramon ◴[21 Jun 25 05:16 UTC] No.44334723[source]▶
They use the Daisy UI component library in 1.8+ Phoenix versions which should have basic accessibility baked in.