←back to thread

638 points wut42 | 1 comments | | HN request time: 0s | source
Show context
chrismccord ◴[] 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 #
b0a04gl ◴[] No.44329692[source]
how are they isolating ai agent state from app-level processes without breaking BEAM's supervision guarantees?
replies(1): >>44330072 #
chrismccord ◴[] No.44330072[source]
They run on separate machines and your agent just controls the remote runtime when it needs to interact with the system/write/read/etc
replies(1): >>44336012 #
b0a04gl ◴[] No.44336012[source]
appreciate the clarity, that helps.

quick followup if the agent's running on a separate machine and interacting remotely, how are failure modes handled across the boundary? like if the agent crashes mid-operation or sends a malformed command, does the remote runtime treat it as an external actor or is there a strategy linking both ends for fault recovery or rollback? just trying to understand where the fault tolerance guarantees begin and end across that split.

replies(1): >>44347829 #
1. chrismccord ◴[] No.44347829[source]
token auth and re-handshake. Agent is respawned if it's no longer alive, and project index is resynced