Rename the project to Agent Browser by Aether AI - #32
Merged
Conversation
The repository is now AetherAI3/agent-browser, so bring every name in the tree in line with it: - display name "Aether Browser" becomes "Agent Browser", with "by Aether AI" shown under the README title; - the Python package moves from aether_browser to agent_browser and the distribution becomes agent-browser; - the runtime environment prefix moves from AETHER_BROWSER_* to AGENT_BROWSER_*; - the in-container service account moves from aether to agent; - the runner unit and slice templates are renamed to match. The org name AetherAI3, the "Aether AI" vendor name, and the VPS6 infrastructure identities are deliberately left alone. Replace the logo with a real transparent PNG. The previous file was a JPEG with a transparency checkerboard and a dashed border painted into its pixels, which rendered as a grey-and-black frame on GitHub. The replacement is an 848x904 PNG with a genuine alpha channel, the painted border removed, and the palette flattened to 64 colours to clear JPEG ringing: 111 KB against 1.48 MB, committed once for the README and once for the Pages copy. Also add a changelog, package URLs, keywords and classifiers, and ignore the local .release-downloads/ evidence directory. The strict release gate will fail exact-commit-evidence on this commit because the runtime-to-tip diff is no longer evidence-only. That is expected: this commit becomes the new runtime commit and a fresh evidence capture follows it.
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.
Brings the tree in line with the repository rename to
AetherAI3/agent-browser, and replaces thelogo with a real transparent PNG.
Naming
Aether BrowserAgent Browseraether_browser(package)agent_browseraether-browser(distribution)agent-browserAETHER_BROWSER_*(env prefix)AGENT_BROWSER_*aether(in-container account)agentops/runner/aether-browser-*.{service,slice}ops/runner/agent-browser-*Deliberately not renamed: the
AetherAI3org, the "Aether AI" vendor name, and the VPS6infrastructure identities (
aether-vps6-browser-01,aether-ci-browser01), which are externalidentities rather than product naming.
AGENT_BROWSER_*is a breaking change for anyone who set the old variables. That is intended atv0.1.0-rc.1and is recorded in the new changelog.Logo
The old
assets/aether-browser-logo.jpgwas a JPEG with a transparency checkerboard and adashed border painted into its pixels — a JPEG cannot carry alpha, so GitHub rendered that
checkerboard as a literal grey-and-black frame around the logo.
The replacement
assets/agent-browser-logo.pngis rebuilt from the original artwork:had smeared the pixel-art edges;
roughly 2.8 MB out of the published source tarball.
Repo polish
CHANGELOG.mdadded (Keep a Changelog / SemVer) and linked from the README nav.pyproject.tomlgains[project.urls], keywords, and classifiers; author is now "Aether AI"..gitignorenow covers the local.release-downloads/evidence directory.Expected gate behaviour
The strict release gate will fail
exact-commit-evidenceonce this lands onmain, because theruntime-to-tip diff is no longer evidence-only. That is by design: this commit becomes the new
runtime commit, and a fresh evidence capture follows in a separate evidence-only PR, exactly as
the previous cycle worked. PR checks (
quality,unit,security,change-map) should be green.