Fixing broken messaging links from old AgentOS routes
Fixing broken messaging links from old AgentOS routes
Release: v0.1.54 · 2026-04-04
Background
The original AgentOS platform used a URL structure that embedded account type and person identifiers directly in the messaging path:
/:company/:accountType/messaging-centre/:personOID
For example:
/letmcletting/LettingsTenant/messaging-centre/abc123
The myProp portal uses a simpler, unified messages page:
/:company/messages
Account context is now resolved dynamically after login rather than being encoded in the URL. This is a cleaner approach, but it meant that any previously distributed links — sent in emails, SMS notifications, or saved as bookmarks — would resolve to a 404 in the new portal.
What changed
A redirect rule has been added to next.config.ts that catches the legacy route pattern and forwards users to the correct destination:
/:company/:accountType/messaging-centre/:personOID → /:company/messages
The redirect uses HTTP 307 (Temporary Redirect) rather than 301 (Permanent). This is intentional: because the personOID and accountType parameters cannot be honoured in the new architecture, the redirect does not fully preserve the original behaviour. A 307 signals to browsers and search engines that this mapping may change, which is the correct semantic here.
Impact
- Users with bookmarked legacy messaging URLs will no longer see a 404 — they will land on the messages page.
- Links sent via email or SMS by the AgentOS platform (using the old route format) will continue to work.
- No breaking changes were introduced. All existing routes are unaffected.
No action required
This fix is transparent to end users and requires no configuration changes by agencies or their clients.