What agents should know before contributing
temporalio/temporal
Temporal service
Read by Bluet from 2 files written for agents and 300 merged pull requests on 2026-09-25. Not reviewed by the maintainers.
Rules its files tell agents (11)
- AGENTS.md
mustNEVER assume standard test commands.
Verify (Tests): If applicable and feasible, verify the changes using the project's testing procedures. Identify the correct test commands and frameworks by examining 'README' files, build/package configuration (e.g., 'Makefile'), or existing test execution patterns. NEVER assume standard test commands.
- AGENTS.md
mustComments should describe WHY something was done, never WHAT was done
Do not litter our codebase with unnecessary comments. Comments should describe WHY something was done, never WHAT was done
- AGENTS.md
mustLibraries/Frameworks: NEVER assume a library/framework is available or appropriate.
Libraries/Frameworks: NEVER assume a library/framework is available or appropriate. Verify its established usage within the project (check imports, and 'go.mod') before employing it.
- AGENTS.md
mustNEVER talk to the user or describe your changes through comments.
Comments: Add code comments sparingly. Focus on why something is done, especially for complex logic, rather than what is done. Only add high-value comments if necessary for clarity or if requested by the user. Do not edit comments that are separate from the code you are changing. NEVER talk to the user or describe your changes through comments.
- CONTRIBUTING.md
shouldPlease don't use very generic titles like "bug fixes".
All commit messages are from the titles of your pull requests. So make sure follow the rules when titling them. Please don't use very generic titles like "bug fixes".
- CONTRIBUTING.md
shouldWhen you are done, don't forget to stop docker compose (with Ctrl+C) and clean up all dependencies:
- CONTRIBUTING.md
shouldIf you started runtime dependencies, don't forget to stop dependencies (with Ctrl+C) and clean up resources:
- AGENTS.md
shouldDo not introduce new third party libraries unless specifically requested.
- AGENTS.md
shouldDo Not revert changes: Do not revert changes to the codebase unless asked to do so by the user.
Do Not revert changes: Do not revert changes to the codebase unless asked to do so by the user. Only revert changes made by you if they have resulted in an error or if the user has explicitly asked you to revert the changes.
- AGENTS.md
shouldConfirm Ambiguity/Expansion: Do not take significant actions beyond the clear scope of the request without con…
Confirm Ambiguity/Expansion: Do not take significant actions beyond the clear scope of the request without confirming with the user. If asked how to do something, explain first, don't just do it.
- AGENTS.md
shouldDo not add explanatory comments within tool calls or code blocks unless specifically part of the required code…
Tools vs. Text: Use tools for actions, text output only for communication. Do not add explanatory comments within tool calls or code blocks unless specifically part of the required code/command itself.
Decisions its pull requests settled (12)
- #11565Recreate only the activity timers whose deadline actually moved
- #11588Fix schedule action delay after refresh
- #11631Align CHASM ALLOW_ALL lifecycle with V1
- #11646Pass the local sub state machine to sanitizeFn on apply
- #11699dynamic partitioning: use probability of AddTask to root partition to estimate overall add task rate
- #11807Dedupe visibility archival
- #11815Replace orphaned child workflows with no worker progress after force failover
- #11820Fix Nexus start-operation retry classification for wrapped service errors
- #11868Fix child completion recovery after late parent replication
- #11924Fix CHASM sentinel handling during scheduler migration
- #11940Return a descriptive invalid argument on branch mismatch
- #12139Avoid mutable state load for verify transition tasks