L4 0.2.4

Server navigation now uses a compact 72px rail, with Inbox first and a separate Chat menu. This release also adds governed Agent runs, schedules and scoped GitHub code environments.

• Open Inbox for unread channels and direct messages, including thread replies. Chat keeps channels, human direct messages and Agent chats in separate groups. Tasks, Schedule, Mail, Databases, Documents, Canvases and Apps have direct rail entries; resource sections open their own menus without a nested Data switcher. On narrow screens, channel details and threads open over the conversation.
• Roles distinguish Agent use, administration, approvals, Task/Data reading and writing, autonomous execution, computers, schedules and code proposals. Select all or specific Boards, Tables, Documents, Canvases and repositories. Agent tools intersect current Agent permissions with the initiating person's delegation and the original run ceiling; revocation applies during execution.
• Configure the optional Pi runtime on Docker or Cloudflare Containers for durable, bounded Runs with conversation-local sessions, cancellation, archived results and recovery. Compute has no provider or production credentials and no public network access. Existing Agent profiles remain on Think; Pi requires an explicitly configured executor and model provider.
• Use Schedule for one-time, daily or weekly reminders and task execution. Schedules preserve wall time across daylight-saving changes, skip missed repetitions, deduplicate occurrences and recheck current permissions. Autonomous execution, computers and schedules remain opt-in; migrations do not grant them to existing roles.
• Configure a dedicated GitHub App and a source repository plus a separate working fork under Settings → Repositories. Authorized task runs can edit bounded files and propose a draft PR in that fork. Publication requires explicit repository and code-proposal grants. Agents cannot merge, change release workflows or deploy production. Required CI checks refer to the exact proposed commit; network-dependent checks remain the repository's CI responsibility.
• Authorized research and Data tools share scoped services across HTTP, internal tools and MCP. MCP table creation additionally requires explicit data:manage consent; existing tokens do not gain that scope. Private computer output archives retain current task, conversation and repository authorization.

This release appends Server migrations 0004_agent_permissions.sql through 0008_code_environments.sql. Published migrations and the server-v1 baseline are unchanged. Existing Task/Data access is retained until restricted; no existing role gains autonomous execution, computer, schedule or code-publication permissions. See governed agents for runtime configuration, limits and dedicated GitHub App permissions.

Validation includes automated role/resource denial and revocation tests, Server integration, Docker runtime isolation/recovery, a real Workers AI reply and session restore in the isolated Cloudflare Container Preview, reminder deduplication, and desktop/mobile navigation checks. Dedicated-App GitHub publication has protocol tests; live acceptance with an operator-configured source/fork pair remains unverified.

The official site, Shell, standalone Server, portable amd64 runtime, VPS installer and version-pinned Docs share version 0.2.4. Updating llll.gg publishes matching Server artifacts; customer Servers remain pinned until their operators install an update with the documented backup requirements. Native iOS/macOS packaging remains frozen.