log_issue
Log a bug, regression, or unexpected behavior as a new issue before writing fix code, so the issue persists across interruptions and session boundaries.
Instructions
Open a new issue. Returns the issue ID.
MANDATORY: call this IMMEDIATELY when you encounter a bug, regression,
or unexpected behavior — BEFORE writing fix code. Logging up-front
means the issue survives interruptions and session boundaries.
Side effects: appends an `issue` event to .projectmem/events.jsonl,
creates an issue file in .projectmem/issues/, updates summary.md,
and marks this issue as the active one for subsequent
record_attempt calls.Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"summary": "<summary>"
},
"name": "log_issue"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| project | No | Which project this call is about — a registered id, alias, or absolute path (e.g. 'ossdrop'). Omit it when the server was started for a single repo, or when an active project is set with `pjm project use`. Call list_projects to see the registered names. | |
| summary | Yes | One-line description of the bug or unexpected behavior. Becomes the issue title and is matched by search_events. Keep it under 140 characters. | |
| location | No | Optional file path or component where the issue manifests (e.g., 'src/auth.py' or 'login/double-submit'). Used by precheck_file to surface this history later. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |