{% extends "base.html" %} {% block title %}File Reservations — {{ project.human_key }}{% endblock %} {% block breadcrumbs %} {% endblock %} {% block content %}

File Reservations

When agents want to edit files, they can "reserve" them to signal their intent to other agents.

Advisory system: Reservations are signals, not hard locks. Agents can still edit files, but they'll see warnings if conflicts exist. Install a pre-commit hook to enforce reservations at commit time.
{% if file_reservations %}
{{ file_reservations|length }} active reservation{{ 's' if file_reservations|length != 1 else '' }}
{% endif %}
{% if file_reservations %}
{% for c in file_reservations %} {% endfor %}
ID Agent Path Pattern Type Created Expires Status
#{{ c.id }}
{{ c.agent }}
{{ c.path_pattern }} {% if c.exclusive %} Exclusive {% else %} Shared {% endif %} {{ c.created }} {{ c.expires }} {% if c.released %} Released {% else %} Active {% endif %}
{% else %}

No Active Reservations

File reservations help agents coordinate who's working on what files to avoid conflicts.

How File Reservations Work

1
Agent reserves a file
Agent calls file_reservation_paths(paths=["src/api.py"])
2
Other agents see the reservation
They'll get warnings if they try to edit the same file (and automatic messaging is blocked)
3
Reservation expires or is released
Reservations auto-expire (typically 1 hour) or agents can manually release them
Important: File reservations are advisory only. They're signals to help coordination, not hard locks. To enforce reservations and block conflicting commits, install the optional pre-commit hook in your code repository.
{% endif %}
{% endblock %}