You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Git-ignored workspace for agent artifacts, organized by task
62
+
63
+
[Learn more :material-arrow-right:](features/temporary-files.md)
56
64
57
65
</div>
58
66
59
67
## How it works
60
68
61
-
### Session start
69
+
### Session hooks
70
+
71
+
Some AI tools support **hooks** -- scripts that run automatically at specific lifecycle points (e.g., session start, pre-prompt). This workspace uses a session-start hook to inject context into the agent before it begins work.
62
72
63
-
For tools with hook support ([Claude Code](https://code.claude.com/docs/en/hooks), [OpenCode](https://opencode.ai/docs/plugins/)), a session-start script runs automatically when an AI session begins:
73
+
For tools with hook support ([Claude Code](https://code.claude.com/docs/en/hooks), [OpenCode](https://opencode.ai/docs/plugins/)), the session-start script runs automatically when an AI session begins:
64
74
65
75
```mermaid
66
76
graph LR
@@ -78,8 +88,8 @@ The agent immediately knows which repos exist, what branch each is on, whether t
78
88
Separately, on every commit, pre-commit hooks keep the workspace aligned:
79
89
80
90
- Regenerate `AGENTS.md` from templates and config
81
-
- Validate skill and command frontmatter
82
-
-Manage feature directories
91
+
- Validate skill and command definitions
92
+
-Sync workspace structure with config
83
93
84
94
These are two independent flows -- session hooks handle runtime context, pre-commit handles workspace integrity.
0 commit comments