Skip to main content
​
New

​
Scheduled tasks from Slack

You can now ask Corelayer in Slack to run a task on a schedule and post the result back to the same channel. Recurring checks, fixed intervals, and one-shot reminders are all supported — for example, “every weekday at 9am, post a summary of open critical issues” or “remind me in 20 minutes to check this issue again.”Scheduled runs are read-only: they can investigate, summarize, and report back, but they cannot change settings or create more scheduled tasks. If you use a local time, include the timezone so it’s scheduled correctly.Set up scheduled tasks in Slack
​
Update

​
Service Map removed

Service Map has been retired and is no longer available across integrations. Existing investigations and integrations are unaffected — Corelayer continues to correlate signals from connected sources without it.Browse integrations
​
New

​
Preflight checks before you ship

Check a change against your organization’s memory before opening a pull request. Preflight takes the PR’s description and returns the failure modes, facts, and preferences the org has hit before for a change like that — grounded reminders to double-check, or nothing when memory has no relevant lesson.
Run inside a repository and it derives the change from the current branch. It’s also available to agents as the corelayer.preflight MCP tool and through the Corelayer skill, so an assistant can run it when you’re about to open a PR.Learn about preflight
​
New

​
Organization memory

A per-organization memory that records your feedback and what Corelayer learns from incidents, and applies it automatically.
  • Closing an issue as a false positive, by design, or “don’t alert” records a preference — matching signals are suppressed instead of re-alerting. Feedback like “fixed” or “duplicate” is not suppressed, so regressions still surface. Reopening an issue reverses what closing it taught.
  • Teaching the assistant a preference, fact, or decision in chat saves it to memory.
  • Learned failure patterns from past incidents feed every new investigation, ranked by relevance, confidence, and recency.
Cortex, in the sidebar, shows what Corelayer has learned about each system — read, edit, archive, or restore any memory.Learn about organization memory
​
New

​
CLI issue slug lookup and diffing

The Corelayer CLI now supports issue lookup by either UUID or issue slug:
You can also diff issues changed after a deploy, merge, timestamp, or recent time window:
Diff responses are paginated and include since, issues, total, page, and limit, making them easier to use in scripts and background triage agents.Use the Corelayer CLI