NanoClaw
NanoClaw rebuilds hosted iMessage registration around Photon
NanoClaw’s Photon proposal replaces an earlier hosted-iMessage path with a registration flow that exchanges a provider token for runtime credentials, stores them in channel config and redacts secrets from responses. A unified adapter targets local and hosted backends while Apple Container users still report proxy reachability problems inside the microVM.
nanocoai/nanoclaw PR #3164 is the inspected primary source: “Hosted iMessage (Photon): supersede #2999 with a working registration flow.” The two related records below were inspected as supporting context, not treated as independent confirmation.
The facts
- nanocoai/nanoclaw PR #3164 was created 2026-07-31T21:44:42Z and was open at inspection; its title is “Hosted iMessage (Photon): supersede #2999 with a working registration flow.” - nanocoai/nanoclaw PR #3076 was created 2026-07-17T22:58:50Z and was closed at inspection; its title is “feat(imessage): unified local+hosted adapter targeting spectrum-ts v11.” - nanocoai/nanoclaw issue #2589 was created 2026-05-22T15:09:24Z and was open at inspection; its title is “Apple Container: host.docker.internal in OneCLI proxy URL doesn't resolve from inside the microVM.” - The repository reported 30402 stars, 861 open issues, default branch main, and last push 2026-07-31T21:28:04Z. - The latest tagged-release baseline checked was v2.1.17 published 2026-06-17T14:51:14Z.
What changed
nanocoai/nanoclaw PR #3164 reports: Type of Change [x] **Feature skill** - adds a channel or integration (source code changes + SKILL.md) [ ] **Utility skill** - adds a standalone tool (code files in.claude/skills/ /, no source changes) [ ] **Operational/container skill** - adds a workflow or agent skill (SKILL.md only, no source changes) [ ] **Fix** - bug fix or security fix to source code [ ] **Simplification** - reduces or simplifies source code [ ] **Documentation** - docs, README, or CONTRIBUTING changes only Description Supersedes #2999, which no longer merges cleanly against main. This PR carries the photon-hq commits unchanged, a merge of current main, and four
nanocoai/nanoclaw PR #3076 reports: Type of Change [x] **Feature skill** - adds a channel or integration (source code changes + SKILL.md) [ ] **Utility skill** - adds a standalone tool (code files in.claude/skills/ /, no source changes) [ ] **Operational/container skill** - adds a workflow or agent skill (SKILL.md only, no source changes) [ ] **Fix** - bug fix or security fix to source code [ ] **Simplification** - reduces or simplifies source code [ ] **Documentation** - docs, README, or CONTRIBUTING changes only Description Companion to #2999, splitting the iMessage landing per review: this PR carries the adapter code on the registry branch — trunk (#2999) keeps
nanocoai/nanoclaw issue #2589 reports: Summary When NanoClaw runs on Apple Container (per the /convert-to-apple-container skill), the OneCLI proxy URL passed to spawned agent containers contains the hostname host.docker.internal. **Apple Container does not auto-resolve this hostname**, and **does not support --add-host** to inject the mapping. The result: every Anthropic API call from inside the agent container fails with ConnectionRefused / "Could not resolve host", the agent retries forever, and the user never gets a response. This is invisible to the user — the container appears to be running, the host log shows "Spawning container" and "OneCLI gateway applied", but no message ever comes back. Steps to reproduce 1. Install Apple
Why it matters
Hosted messaging turns channel setup into an identity and secret-lifecycle surface. Registration, storage, redaction, deletion and transport selection must agree before the adapter can be treated like another harmless channel toggle. This is an operator boundary: persisted state, execution ownership and visible controls must describe the same event. A workaround that broadens access, deletes state or hides the symptom would trade a visible defect for an unmeasured one.
Current
The primary record was open when captured on 2026-08-01. The release baseline was v2.1.17 published 2026-06-17T14:51:14Z. Current repository metadata, pull requests, issues, release records, Google News discovery, Hacker News discovery, Lobsters, Metamesh and the rendered ClawCharts row were checked. ClawCharts selected the subject; it did not prove the claim.
Evidence
The primary URL is https://github.com/nanocoai/nanoclaw/pull/3164. Supporting records are https://github.com/nanocoai/nanoclaw/pull/3076 and https://github.com/nanocoai/nanoclaw/issues/2589. Their source bodies, timestamps and states were captured in the daily evidence bundle. Test counts, reproductions and deployment observations remain attributed to their authors unless explicitly identified as independently rerun.
Source boundary
Open work is described as open, closed work as closed, and operator reports as reports. A pull request is evidence of proposed or reviewed direction, not proof of a shipped release. Issue closure would not by itself prove a deployed fix. Search residue, package mirrors and historically published source spines were excluded.
Operator take
Verify token exchange and credential deletion end to end, keep provider claims scoped to the selected channel, and test local, hosted and Apple microVM networking as distinct environments. Preserve a before-state receipt, make the smallest reversible change, and verify the original failure independently after intervention.
Caveat
Public project records are mutable. Status, scope and evidence can change after publication. This brief records the inspected state and does not authorize changes to a reader’s deployment.
Source inspected; source state, environment and release boundary remain explicit.