> For the complete documentation index, see [llms.txt](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/.spec_system/prd/phase_41/session_01_local_access_startup_contract.md). # Session 01: Local Access Startup Contract **Session ID**: `phase41-session01-local-access-startup-contract` **Status**: Complete **Estimated Tasks**: \~12-25 **Estimated Duration**: 2-4 hours *** ## Objective Make every normal local startup path establish `AI_OS_LOCAL_ALL_ACCESS=1` and write-ready behavior before middleware or product routes evaluate access. *** ## Scope ### In Scope (MVP) * Implement `AI_OS_LOCAL_ALL_ACCESS=1` defaults in `package.json`, `vite.config.ts`, `scripts/dev.sh`, and `scripts/cleandev.sh`. * Preserve `HERMES_DASHBOARD_ADMIN` and `OPENCLAW_DASHBOARD_ADMIN` only as legacy compatibility aliases. * Update startup hints, failure copy, `.env.local.example`, and focused startup regression tests. ### Out of Scope * Route and component language cleanup beyond startup-facing text. * Bridge status contract rewrites owned by Session 02. *** ## Prerequisites * [x] Phase 41 PRD and session stubs exist. * [x] Current startup commands and Vite env resolution have been inspected. *** ## Deliverables 1. Startup paths that default normal local dev to all-access readiness. 2. Compatibility handling for old admin env keys without making them required. 3. Tests proving `bun run dev`, `scripts/dev.sh`, and `scripts/cleandev.sh` establish the contract. *** ## Success Criteria * [x] Normal local startup does not require manual Hermes or OpenClaw admin env keys for shipped write/edit/action readiness. * [x] Startup failure output names real missing dependencies, token failures, offline states, or recovery actions. * [x] Focused startup tests prove the new default. *** ## Folded Handoff Session Details The following session-specific details were migrated from the former ongoing-projects handoff. They preserve the original objective, scope, outputs, dependencies, notes, and acceptance checks for this session. #### Session 01: Local Access Startup Contract **Objective**: Make every normal local startup path establish `AI_OS_LOCAL_ALL_ACCESS=1` and write-ready behavior before middleware or product routes evaluate access. **Scope**: * Implement `AI_OS_LOCAL_ALL_ACCESS=1` as the canonical local access contract in `package.json`, `vite.config.ts`, `scripts/cleandev.sh`, and `scripts/dev.sh`. * Preserve `HERMES_DASHBOARD_ADMIN` and `OPENCLAW_DASHBOARD_ADMIN` only as legacy compatibility aliases whose absence never blocks shipped local writes, edits, process actions, deploy/spawn actions, voice actions, or Intelligence actions. * Update the clean-dev Hermes runtime hint and failure copy so it reports real startup dependencies and recovery actions instead of telling operators to opt in with `HERMES_DASHBOARD_ADMIN=1`. * Update `.env.local.example` so normal local startup is all access by default and OpenClaw is covered by the same contract. * Add focused startup regressions for `bun run dev`, `scripts/dev.sh`, and `scripts/cleandev.sh`. **Outputs**: * Local startup commands and Vite env resolution that default to full local write/edit/action access. * Compatibility handling for old admin env keys without making them the product gate. * Updated local env example, startup hints, and startup-path tests. **Dependencies / Notes**: * Preserve loopback and same-run token checks as automatic local security controls. * Legacy `HERMES_DASHBOARD_ADMIN` and `OPENCLAW_DASHBOARD_ADMIN` aliases may remain for compatibility, but they must not be required for normal local execution. * Out of scope: route/component copy cleanup except startup-facing text. **Acceptance Checks**: * `bun run dev` resolves Hermes and OpenClaw write readiness without preconfigured admin env keys. * `scripts/dev.sh` and `scripts/cleandev.sh` pass the same local all-access contract into the Vite process and tmux server. * Startup failure output names actual missing dependencies, token failures, or offline states and does not present manual admin env setup as the normal recovery path. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/.spec_system/prd/phase_41/session_01_local_access_startup_contract.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.