Explicit environments, IndexedDB, and agent plumbing
Tightened environment config, IndexedDB cleanup, mobile PWA details, and repo links used by agent workflows.
Today was about tightening small pieces that define trust in the system.
Client project (NDA)
Environments with no hidden fallback
I started by resolving conflicts and reviewing comments from recent PRs. The focus moved to environment config: the API URL and app environment need to be explicit, with clear values for production, staging, and development.
Removing the hardcoded local development fallback makes the error show up early. That is better than letting the app point to the wrong place while looking healthy.
Local cleanup and IndexedDB
I kept refining the local data cleanup button. The first version did not cover every database and draft in every context, so the change now sweeps environment-scoped stores and clears local state in a more predictable way.
This kind of tool looks simple from the outside, but it matters for an offline-first app. If the user or the test flow needs a clean start, the app needs to keep that promise.
Mobile and PWA
I also fixed mobile UX details: sticky header, the stepper below the header, and the install banner. The close button now has a better touch target, and the iOS install modal no longer fights the banner visually.
Personal agent infra
In personal-os, I organized symbolic links between the repository and the agent runtime.
The goal was to reduce dependence on physical paths and let different tools find the same context without duplicate clones or parallel conventions.
tgmarinho-ai-website
I also brought /daily back into shape, generating the public record for these two work days.
The theme was the same across the work: make the environment more explicit so the behavior becomes less surprising.