feat: read devnet manifest from shared data directory#9
Open
Nic-dorman wants to merge 1 commit intomainfrom
Open
feat: read devnet manifest from shared data directory#9Nic-dorman wants to merge 1 commit intomainfrom
Nic-dorman wants to merge 1 commit intomainfrom
Conversation
Check ant_core::config::data_dir() (e.g. %APPDATA%/ant/) for devnet-manifest.json before falling back to the GUI-specific config directory. This lets devnet launchers write the manifest to a shared location that any consumer (GUI, CLI, TUI) can discover, without coupling ant-core to ant-gui's filesystem layout. The legacy GUI config path is kept as a fallback for backward compatibility. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Nic-dorman
added a commit
to WithAutonomi/ant-client
that referenced
this pull request
Apr 8, 2026
Move the devnet manifest from /tmp (or GUI-specific paths) to the shared ant data directory (ant_core::config::data_dir()). This lets any consumer — ant-gui, ant-cli, ant-tui — discover devnet/testnet mode by checking the same well-known location where daemon.port already lives. Changes: - start-local-devnet: 25 nodes (was 5), writes manifest to shared data dir, 8MB thread stack for Windows, cleanup on Ctrl+C - start-devnet-sepolia (new): 25 nodes with ArbitrumSepoliaTest EVM, uses existing deployed Sepolia contracts, no wallet key embedded (user connects their own funded wallet) Companion PR: WithAutonomi/ant-ui#9 (ant-gui reads from this path) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Open
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
devnet-manifest.jsonfrom the shared ant data directory (ant_core::config::data_dir()) instead of only the GUI-specific config directoryThis unblocks devnet/testnet launchers from writing the manifest to a shared location that any consumer (GUI, CLI, TUI) can discover, without coupling ant-core to ant-gui's filesystem layout.
Lookup order
%APPDATA%/ant/(Win),~/Library/Application Support/ant/(Mac)%APPDATA%/autonomi/ant-gui/(Win)First match wins. If neither exists → production mainnet mode (unchanged).
Companion change needed
On the ant-core side, the devnet launcher examples need to write the manifest to
ant_core::config::data_dir()instead of the GUI config path. This is a trivial change — replacedirs::config_dir().join("autonomi/ant-gui")withant_core::config::data_dir().Closes the approach discussed after ant-client#29 was rejected.
Future direction
This is "Approach A" — the simplest fix. Longer-term, the daemon should be network-aware (expose EVM config via its REST API), and
ant node daemon start --network sepoliashould be the way to select a testnet. See discussion in that PR for approaches B and C.Test plan
🤖 Generated with Claude Code