multica-ai/multica · error
write task context marker: %w
Error message
write task context marker: %w
What it means
Error "write task context marker: %w" thrown in multica-ai/multica.
Source
Thrown at server/internal/daemon/execenv/context.go:231
payload := taskContextMarkerFile{
ManagedBy: TaskContextMarkerManagedBy,
AgentID: ctx.AgentID,
IssueID: ctx.IssueID,
}
data, err := json.MarshalIndent(payload, "", " ")
if err != nil {
return fmt.Errorf("marshal task context marker: %w", err)
}
if err := recordWriteFile(filepath.Join(workDir, TaskContextMarkerRelPath), data, 0o644, manifest); err != nil {
if errors.Is(err, errPathPreExists) {
path := filepath.Join(workDir, TaskContextMarkerRelPath)
existing, readErr := os.ReadFile(path)
if readErr != nil {
return fmt.Errorf("read existing task context marker: %w", readErr)
}
var marker taskContextMarkerFile
if json.Unmarshal(existing, &marker) != nil || marker.ManagedBy != TaskContextMarkerManagedBy {
return fmt.Errorf("write task context marker: %w", err)
}
if writeErr := os.WriteFile(path, data, 0o644); writeErr != nil {
return fmt.Errorf("refresh task context marker: %w", writeErr)
}
if manifest != nil {
manifest.Files = append(manifest.Files, path)
}
return nil
}
return fmt.Errorf("write task context marker: %w", err)
}
return nil
}
// projectResourceFile is the on-disk JSON written into the agent's working
// directory. Schema is intentionally a thin pass-through of the API response
// so consumers (skills, future tooling) don't need a separate parser.
type projectResourceFile struct {View on GitHub (pinned to 2c0912b6ec)
Solutions
- Check disk space and permissions for the task context marker.
When it happens
Trigger: Thrown at server/internal/daemon/execenv/context.go:231 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of multica-ai/multica@2c0912b6ec (2026-08-15).
Data as JSON: /api/errors/8ad5c0ba3f00b70c.
Report an issue: GitHub.