Claude code replaces google workspace with a local folder setup

At a glance:

• Claude Code can read, write and reorganize plain‑text files in a local folder, acting as a note‑taking and task‑management hub.
• The author built four dedicated folders (tracker, planner, tasks, complete) that together replace Google Sheets, Calendar, Tasks and Docs.
• Automation is driven by a CLAUDE.md rule file and reusable Skills, but the system still requires a manual session start.

What the author did

The writer, Nolen, long‑time tech writer at MakeUseOf, decided to abandon a paid Google Workspace subscription in favour of a completely local workflow powered by Anthropic’s Claude Code. After months of hesitation—largely because Claude Code is marketed as a developer‑centric tool—the author discovered that its core capability is simple file access. By pointing Claude at a directory, the AI can read existing files, create new markdown documents, rename them, and even edit YAML front‑matter across multiple files.

The transition was surprisingly quick. Nolen set up a top‑level claude/ directory and created four sub‑folders, each with its own CLAUDE.md rule file. Within minutes the basic scaffolding was ready, and the author began feeding the AI prompts such as “create a new note about X” or “move all LM Studio screenshots into a dated subfolder”. The result is a self‑contained productivity suite that lives entirely on the user’s machine, with optional syncing to Google Drive for NotebookLM compatibility.

How Claude Code works with folders

Claude Code treats every folder as a miniature knowledge base. The CLAUDE.md file at the root defines the rules for that folder—what file types are allowed, naming conventions, and how to handle tags or linked notes. When a session is started, Claude reads those rules and can act on them without further instruction. For example, in a screenshots folder the AI can identify the originating application from the image content and automatically place the file into a sub‑folder named after that app.

Beyond static rules, Claude supports Skills, which are saved workflows that can be invoked by name. A Skill might be “move‑screenshots‑by‑date” or “generate‑meeting‑notes”. Instead of describing the same series of actions each time, the user simply calls the Skill, and Claude executes the predefined steps. This hybrid of rule‑based and prompt‑driven automation gives the system flexibility while keeping the user in control.

Replacing specific workspace apps

The author mapped four core Google Workspace functions to local folders:

• tracker/ – Holds pitches.md, a markdown table tracking article ideas. Columns include title, status, date added, and notes. Updates are made by speaking to Claude rather than editing cells, effectively replacing Google Sheets.
• planner/ – Contains today.md with daily to‑dos and notes. At the start of each day Claude archives the previous file and creates a fresh one, mimicking the daily view of Google Calendar without notifications.
• tasks/ – Serves as a replacement for Google Tasks. It maintains persistent “active” and “done” sections, automatically trimming completed items. Claude can also pull tasks from other folders, e.g., “add a task for every pitch marked drafting in tracker/”.
• complete/ – Stores reusable Skills such as a “meeting‑notes” Skill that generates a markdown template with appropriate headings.

Together these folders cover the majority of the author’s workflow that previously relied on Google Docs, Sheets, Calendar and Tasks.

Automation with CLAUDE.md and skills

The rule files (CLAUDE.md) act as a declarative manifest: they describe the folder’s purpose, naming patterns, and any special handling (e.g., how to parse YAML front‑matter). When Claude starts a session, it parses the manifest and immediately knows how to treat incoming content. This eliminates the need for repetitive natural‑language instructions.

Skills take automation a step further. They are essentially macros stored as named entities. For instance, the “meeting‑notes” Skill creates a new markdown file pre‑populated with sections like Attendees, Agenda, and Action Items. The author can invoke it with a single command, and Claude handles the file creation, naming, and placement. While Claude does not run as a background daemon, the session startup is fast enough that the workflow feels seamless.

Limitations and workflow considerations

Claude Code is not a continuously watching service; it does not monitor folders in real time. Users must start a session whenever they want the AI to act, which means the system cannot automatically reorganise files the moment they appear. However, the quick launch time makes this a minor inconvenience for most users.

Another limitation is the reliance on plain‑text markdown files. Users who depend heavily on rich‑text formatting, complex spreadsheets, or native Google Docs features may need to adapt their documents or accept a reduced feature set. Nevertheless, for note‑taking, simple tables, task lists, and image‑based organization, the local setup proves more than capable.

What to watch next

Anthropic continues to expand Claude Code’s capabilities, hinting at tighter OS integration and background‑process options in future releases. If those features arrive, the current manual‑session model could evolve into a truly autonomous file‑management assistant. Meanwhile, power users can experiment with additional Skills, integrate third‑party tools via the filesystem connector, or even combine Claude Code with version‑control systems for collaborative markdown editing.

The experiment demonstrates that a sophisticated AI can replace a multi‑product SaaS suite with a handful of well‑structured folders, offering privacy, cost savings, and full control over one’s data.