What if a CLI session could schedule its own next turn?

Looking Glass is a local AI coding CLI built around persistent, automatable sessions. The key feature is that a session can keep existing after you close the terminal, and a scheduler can later trigger new AI turns inside that same session. Those future turns reopen the original workspace, retain the session configuration, inspect files or logs that changed in the meantime, use the CLI tools, run commands, modify code, and write the results back into the session. In practice, this lets you automate workflows such as: Ask the model to deploy or start a long-running task, then have the same session check the result later. Schedule a follow-up turn to inspect test output and fix failures automatically. Run recurring project reviews that read the current codebase, execute tests, and report or resolve issues. Continue debugging after new logs or external processes have produced more information. Leave a session working through scheduled turns even when the interactive terminal is closed. Combine exact scheduled shell commands with context-aware AI follow-ups. Scheduled prompts are not separate stateless jobs or fresh chats. They are future turns attached to an existing session, with access to its: Workspace Previous conversation and tool history Primary model and reasoning settings Permissions and remembered approvals Agent configuration Scheduler results and persistent artifacts Looking Glass also supports concurrent worker agents. The agent model and reasoning level are configured separately from the main model, allowing a stronger model to coordinate while faster or cheaper models handle parallel discovery, implementation, or review tasks. Additional functionality includes: Interactive TUI and one-shot CLI prompts OpenAI-compatible local or hosted gateways File reading, search, patching, and bounded Bash execution Persistent approval modes for interactive and automated turns Scheduled AI prompts, reminders, and deterministic commands SQLite-backed session, scheduler, and artifact state A user-level systemd scheduler that runs independently of the terminal Typical setup: start a coding session, give it a task, attach one-time or recurring follow-up prompts, close the terminal, and let the CLI continue that same workflow later.