LockIn

Install

Works with Claude Code, VS Code, Cursor, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install connector/sky-walkerx-lockin

About

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list, install config and code. Checked Oct 25, 2026.

Tools

4 read · 13 write · 1 delete

Secrets

None asked for

Install scripts

Nothing to install (hosted)

Runs as

Hosted (remote endpoint)

Tools (18)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

• add_subtaskAdd a subtask

  Add a subtask to a task, at the end of its list. Give parent_id to put it under another subtask instead; nesting goes one level deep.

• add_taskAdd a task to a plan

  Add a task to the user's plan, at the end of a note's tasks (give note_id) or of a subject's tasks that aren't under any note (give subject).

• append_to_noteAdd to a note

  Add text to the end of an existing note. Never replaces what's there. On a note you recorded it simply continues the note; on anyone else's it goes under a line saying it came from you and today's date.

• capture_sessionFile a session's summary

  Keep what a coding session learned before its context is compacted, or when it ends. The LockIn plugin for Claude Code calls this from its hooks: at compaction with Claude Code's own summary, and at the end through a short background run that writes one. Don't call it yourself unless you were asked to file a session. One note per session: each later call adds a dated section to it. The user witnesses it like any note you save.

• confirm_noteConfirm a note still holds

  Say a note still matches the code: you compared its files with what's in the repo now (see the git diff command get_note gives) and nothing it says changed. Moves its anchor to your commit and clears any stale flag. Works on any note, since it doesn't change what it says. Also anchors a note that has no anchor yet.

• edit_noteEdit a note you recordedcan change or delete data

  Change a note you recorded yourself: give it a new title, or replace one passage with new text (copy old_text exactly from get_note; it must appear once). Notes written by the user or another agent can't be edited, only added to with append_to_note. The user witnesses the note again after an edit.

• flag_staleFlag a note that may be out of date

  Tell the user a note may no longer be true, and why (e.g. "lib/auth.ts moved to OAuth in 4f2c1e0; the token section is wrong"). Use it when you can't tell what's true now; when you can, write the correction with supersede_note. The note shows the flag until the user looks at it or an agent confirms the note.

• get_noteRead a note, task or subtaskread-only

  Read one item in full by its id. A note comes with its markdown, subject, who wrote it and its plan: each task with its notes and nested subtasks. A task or subtask comes with its notes, where it sits and the subtasks under it.

• get_planRead a subject's planread-only

  Read a subject's whole plan: every note's tasks and nested subtasks with what's done, plus tasks not under any note. Long notes on an item are cut short; pass its id to get_note for the rest.

• link_replacementSay your note replaces an older one

  Mark a note you recorded as the replacement for an older note it makes wrong, e.g. one save_note listed as related. Your note goes back to the user to witness; once they do, the old page retires from search and Ask. To write a replacement from scratch, use supersede_note instead.

• list_subjectsList subjectsread-only

  List the subjects (sections) in the user's notebook with how many notes each has, plus the Inbox where unfiled notes wait. Call this before save_note to pick the right subject.

• move_noteMove a note

  File a note under another subject, e.g. out of the Inbox. Its tasks go with it. The subject must already exist.

• pickup_handoffPick up where another agent stopped

  Read the baton another agent left, and take it: the goal, where the work stands, what was ruled out, the exact next step, and the text of the pages it pins. Call it when the user asks you to pick up or continue, or at the start of work in a repo that may have one. Give the subject, or the repo or working folder, to find the right one; with neither you get the newest. peek reads it without taking it.

• save_handoffHand your work to the next agent

  Leave a baton for whoever carries on: another tool, or a new session after a usage cap or a /clear. Call it when you stop with work unfinished, or when the user says they're switching. It's a short card, not a note: the goal, where it stands, what you tried and ruled out, the exact next step and where it starts (file:line), and up to 5 notebook pages to read first. Long fields are cut short, so say the essentials first. A newer baton for the same subject or repo replaces this one.

• save_noteSave a note

  Save a new note to the user's notebook. Write the body as markdown: what was learned, with the code or commands that matter. Name an existing subject to file it there; with no subject, or one that doesn't exist, it goes to the Inbox. The user sees it marked as recorded by you until they witness it. When the note describes code in a repo, give repo, commit, commit_date and files, so a later agent can tell when the code has moved on. The reply lists notes that look related: if yours makes one of them wrong, link it with link_replacement.

Signals

Stars

3

Forks

0

Open issues

0

Last commit

Oct 15, 2026 (15 days ago)

Last release

Oct 14, 2026 (16 days ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name

io.github.Sky-walkerX/lockin

Version

1.0.0

Auth

Auth not stated

License

AGPL-3.0

Repository

github.com/Sky-walkerX/LockIn

Website

lockin.namankhandelwal.dev

First seen

Oct 24, 2026

Last checked

Oct 24, 2026

Source

Official MCP Registrygithub-graphql