> ## Documentation Index
> Fetch the complete documentation index at: https://docs.blocks.team/llms.txt
> Use this file to discover all available pages before exploring further.

# Global Configuration

> Load shared skills, hooks, and sub-agents into every coding agent session from a central repository

## Overview

A global configuration repository lets you maintain shared skills, hooks, and sub-agents in one place and have them automatically loaded into every coding agent session across your workspace — regardless of which repository the agent is working in.

Configure it at **Dashboard → Settings → Global Configuration**.

## What gets loaded

When a session starts, Blocks loads the following from your global configuration repository:

* **Skills** from `.claude/skills/`, `.codex/skills/`, and `.agents/skills/`
* **Hooks** for customizing agent behavior
* **Sub-agents** configuration

These are merged with skills from the active repository and any skills created directly in the dashboard. See [Skills](/using-blocks/features/skills) for how merging works.

## Setting a global configuration repository

1. Go to **Dashboard → Settings → Global Configuration**
2. Select a repository from the dropdown — only repositories already connected to your workspace are shown
3. Click **Save**

To remove the global configuration repository, select the blank option at the top of the dropdown and save.

<Note>
  Changes take effect in new sessions. Existing sessions are not affected.
</Note>

## Setting up sandbox environments

The global configuration repository can also include a `.blocks/post-clone` script. This script runs automatically after Blocks clones the global configuration repository into each sandbox, making it a convenient place to set up environment configuration that should apply to every session — regardless of which repository the agent is working in.

Common uses include installing global tools, setting environment variables, or applying workspace-wide configuration.

```bash theme={null}
#!/bin/bash
set -e

# Install a global CLI tool used across all projects
curl -L https://example.com/mytool -o /usr/local/bin/mytool
chmod +x /usr/local/bin/mytool

# Configure AWS CLI for shared infrastructure access
aws configure set region us-east-1
aws configure set output json

echo "Global environment setup complete!"
```

See [Post-clone scripts](/using-blocks/features/post-cloning) for details on how to write and configure these scripts.

## When to use this

A global configuration repository is useful when:

* Multiple repositories need the same set of skills (e.g., `/review-security`, `/gen-tests`)
* You want to enforce consistent agent behavior across your workspace
* Your team maintains shared hooks or sub-agent configurations
* You need a consistent sandbox environment setup applied to every session

For repository-specific skills that only apply to one project, commit a `SKILL.md` directly to that repository instead. See [Skills](/using-blocks/features/skills) for details.