Away Mode — Productivity skill for Claude Code

away-mode

A Claude skill for the hours you are not at the keyboard.

You hand over a task list and go to sleep. It works through every job, proves each one with an independent check, never asks you a question, survives a dropped session, and leaves a single handoff report with the evidence.

Why

Autonomous runs fail in two boring ways. Either the agent stops on the first ambiguity and you wake up to a question, or it reports seven jobs done and three of them were never true on the server. `away-mode` closes both: asking is forbidden and every decision is recorded instead, and no job is marked done without a read-back that proves the persistent state changed.

Install

Claude Code, user level (available in every project):

git clone https://github.com/demircigoksu/away-mode.git ~/.claude/skills/away-mode

Or project level, for one repo only:

git clone https://github.com/demircigoksu/away-mode.git .claude/skills/away-mode

Windows: clone into `%USERPROFILE%\.claude\skills\away-mode`.

For claude.ai, zip the skill folder and upload it as a skill.

Use

Write a task file (see `assets/task-file-template.md`), then:

I'm going to sleep. Finish everything in tasks.md, don't ask me anything.

Nothing is hardcoded. The task file's name, the number of jobs, how long you are gone, and where verification runs are all read from your message and your task file at run time.

Variable	Resolved from
TASK_FILE	the name you gave, an attachment, or a search of the project
TASK_COUNT	counted from the file; the number you said is only a checksum
AWAY_MODE	asleep / busy / mobile / unattended / away
AWAY_WINDOW	"overnight", "two hours", or unknown
PROJECT_ROOT	the task file's folder
VERIFY_TARGETS	the verbs in your task file
RESUME_POLICY	a scheduled task that resumes from the state file

How a job runs

READ  ->  PLAN  ->  APPLY  ->  VERIFY  ->  RECORD EVIDENCE  ->  WRITE