Before you try Day Shift.

Develop a Project Brief and specifications, prepare scoped tasks, guide your coding agent, and review returned implementation evidence. The browser GUI brings this work together; the CLI supports terminal workflows.

Yes. Open a Git repository and initialize a Day Shift workspace alongside your code. Start with one feature or task, and review the files Day Shift creates before choosing what to commit.

Day Shift assists with planning documents, task preparation, and review. Your external coding agent implements source changes from the handoff. You still decide the scope, review the code, run appropriate checks, and accept the result.

The current GUI build supports Codex app-server and OpenAI-compatible connections. Configure your own provider and model. Endpoint behavior and authentication vary; consult the compatibility page and provider setup docs for the supported scope. These connections are separate from the coding agent you use for implementation.

The workspace and browser GUI run on your machine. Local file operations and license verification do not require online activation. When you use a remote inference provider, prompts and selected project context are sent to that provider; its service terms and costs apply. Your external coding agent has its own data handling.

Planning documents and evidence live alongside your code, commonly under .day-shift/. Conversation history and runtime state also use local storage. Local storage does not mean every file belongs in Git: review ignore rules and keep credentials and private state out of commits.

Review the selected project, document context, and provider before sending a request. Project-aware chat may read permitted project material to answer you. Check context disclosures and citations, and review proposed document changes before saving. Local storage does not prevent remote inference disclosure.

Yes. Terminal workflows do not require a browser or a running GUI server. The docs cover initialization, planning, handoffs, validation, and recovery from the terminal.

Yes. Day Shift 0.3.1 includes the browser GUI and CLI. Install the release, then run day-shift serve --open from your project directory. The walkthrough uses a Taskboard example captured during development. See the installation guide and compatibility page for setup details.

Evaluation lets you try the complete workflow without signup, a license file, or online activation. Commercial use requires coverage for your users and release line. GUI and CLI are interfaces to the same product, not separate purchases; provider and coding-agent charges are separate. See pricing for coverage and support terms.

Start with the work you want to do. These names describe how much planning and review structure a task or project needs. They are not pricing tiers. The docs explain the choices when you need them.

It is the written agreement about the work: intended outcome, scope, validation expectations, decisions, and evidence of what changed. Day Shift keeps that record alongside the code so people and agents can continue from it.