IL Co

Turn a public GitHub pull request into a cited handoff: decision, evidence, unknowns, owner and next check. No sign-in, read-only.

Hosted MCP Server

npx add-mcp 'https://ilco.ilconcetto.org/mcp/public'

Installs into Claude Code, Codex, Cursor and more

Documentation

When work changes hands, the why comes with it.

The next owner gets the decision, the evidence and the next step, and every line is cited. IL Co drafts the handoff from Slack, Linear, Jira, GitHub and GitLab. The author approves it in one tap. It works the same when the next owner is 10 hours ahead, or when the last owner was an AI agent.

It's free for up to 3 people, no card. An admin reviews new accounts before sign-in.

For engineering teams that hand work across time zones, between people and AI agents. Two people or two hundred.

Try it now on a public pull request. No sign-in.

Recorded in IL Co with sample data: Priya hands ENG-142 to Marco. You see the cited draft, her approval and his acceptance.

Sample data: Acme Engineering, Priya, Marco, ENG-142 and #418 are made up for this picture.

Your AI agents finish tasks. IL Co makes them hand off to people, with citations.

Most tools stop when the agent stops. IL Co picks up there. Claude, ChatGPT, Cursor and Codex connect to IL Co over MCP. When an agent finishes, a person gets a cited handoff to check. They don't have to reverse-engineer a diff. Agents can read on every plan. Recording progress and drafting handoffs come with Solo, Team and Business.

  1. It reads the work first.

    Before it starts, an agent reads what was done, why, who owns it and what is blocked.
  2. It records what happened.

    It records real results, which tests ran and which did not, and what it could not finish.
  3. A person approves the handoff.

    The agent drafts it from cited sources. Nothing reaches the next owner until its author approves. Connect your AI client

Your work is spread across your tools, and often across time zones.

The discussion is in a Slack thread. The task is in Linear or Jira. The code is in a GitHub pull request or a GitLab merge request. Follow one piece of work and it touches all of them. Then it moves to someone else, sometimes in another city who starts their day as you end yours.

  1. WhenWhereWhat happened to the work
  2. MondaySlack · #auth-engThe bug is reported, argued about and narrowed down in a thread.
  3. TuesdayLinear · ENG-142It becomes an issue with a title, a status and an owner.
  4. WednesdayGitHub · acme/api #418The fix is written, reviewed and half-merged.
  5. Next MondayMarco Silva picks it up
    • Why fifteen minutes?
      • Is #418 safe to merge?
      • Who decided that, and where?

The information exists. The context doesn't. When the person who knows is asleep on the other side of the world, nobody can just ask.

The same story plays out in Jira and GitLab. IL Co reads both.

When it kicks in.

IL Co notices the handoff moment, so nobody has to remember to write one. That includes the end of someone's day.

  • An issue is reassigned in Linear The previous owner gets a draft to approve, and the new owner receives it.
  • Someone goes on leave An out-of-office status in Slack drafts a handoff for each of their open issues.
  • /handoff in Slack Run it from any thread, whenever someone decides it is time. That could be before a long weekend, at the end of a shift, or before a reorg.
  • An issue reaches your handoff status Pick the Linear statuses that mean "ready to hand over".
  • An AI agent finishes a task An agent connected over MCP drafts the handoff to a person, who approves it.
  • The on-call rotation changesNext The outgoing engineer's open incidents are handed to the next one.

What IL Co reads and writes.

We state this before you connect anything. IL Co works with Slack, Linear, Jira, GitHub and GitLab. Each one was switched on only after it passed a test against the real service.

  • Slack
  • Linear
  • Jira
  • GitHub
  • GitLab

Using something else? Tell us.

  • Nothing posts without approval.

    A handoff reaches Slack or Linear only after its author approves it. GitHub, GitLab and Jira are read-only and are never written to.
  • You pick what it can read.

    It reads only the channels you add the IL Co app to, and only the projects and repositories you grant. Private channels are never imported.
  • It never guesses.

    Every line cites its source. What the sources don't say is marked Unknown. A search with nothing behind it answers "Not enough evidence found."

Why not Slack AI or Unblocked?

They answer when you ask. IL Co acts at the handoff, across your tools, including when the one handing off is an AI agent. The author approves before anything is shared.

Slack AIUnblockedIL Co
When it worksWhen you ask: summaries, recaps, answersWhen you ask a questionAt the handoff: reassigned, on leave, /handoff, agent finished
What it readsYour Slack conversationsThe code, docs and chat you connectSlack, Linear, Jira, GitHub and GitLab, stitched around one issue
What you getA summary in SlackAn answerA cited handoff: done, why, decisions, state, unknowns, next steps
AI agents handing off to people——Agents over MCP draft a cited handoff, and a person approves it
Before it is sharedShown to the person who askedShown to the asker, and to the team in a shared questions feedThe author approves it, then it posts to the issue and the thread

From each product’s own public pages, checked October 2026. They are good at what they do. IL Co does a different job.

Questions.

Short answers about tools, time zones, agents and approval.

Do you support Jira and GitLab?

Yes. IL Co works with Slack, Linear, Jira, GitHub and GitLab. On Jira and GitLab it reads the issues, merge requests, reviews and comments a handoff cites, and writes nothing. On Linear it can also post one approved comment and change status only if the author picks one.

Does IL Co work for teams across time zones?

Yes. That is where handoffs hurt most. When the next owner starts their day after you've logged off, they get the decision, the evidence and the next step, each one cited, so they don't wait a day to ask.

How do AI agents fit in?

Claude, ChatGPT, Cursor and Codex connect over MCP. On every plan, agents can read what was done, why, and what is blocked. On Solo, Team and Business they also record progress and draft handoffs to a person, who approves before anything reaches the next owner. Agents never count as seats.

Will IL Co post or change anything without us?

No. Nothing posts until its author approves it. GitHub, GitLab and Jira are read-only. IL Co reads only the channels you add it to and the repositories you grant, and it never imports private channels.

What if the sources don't have the answer?

IL Co marks it Unknown. It does not guess. Every line in a handoff cites where it came from, and a search with nothing behind it answers "Not enough evidence found."

Request beta access. Upgrade when handoffs are how you work.

Free for up to 3 people and 7 handoffs a month. No card. Works with Slack, Linear, Jira, GitHub and GitLab.

Want a reply before you sign up? Tell us about your team and we will email you.