A mass of black fluid lives in your MacBook notch. Pull a piece off it and drop it on a file, a folder or a window. It bonds there and works on it, running your own Claude Code underneath.
macOS 14 or later. Needs Claude Code on a paid Claude plan or a Console API key; Inkling never touches your credentials.
No chat window to find, no project to configure, no context to assemble.
Drag down out of the notch. A neck stretches like honey and snaps. The mass above gets smaller — that piece is out in the world now.
Let go over anything: a PDF, a folder, a browser tab, a window. The fluid wraps it and stays stuck to it, even when you move or rename it.
A bubble asks what you want. Answers come back with citations you can tap. Drag a tentacle to a second file to pull it in as context.
Chat asks you to describe the thing. Inkling asks you to point at it.
Open a window. Find the file. Upload it. Explain what it is and where it came from. Paste the error. Re-explain after the context runs out.
Drop it on the file. The agent already has the path, the parent folder, the window and the selection, and keeps them until you retire it.
No spinners, no little coloured dots, no log window.
Real targets, real questions, the first line of the answer.
What are the payment terms?
Net 30 from invoice date, 1.5% monthly on late balances. p.4p.11
Rename these by date, oldest first.
14 files, 2024-03-02 → 2026-09-30. Allow · Deny
Summarise this thread and who disagrees with whom.
Three positions; the maintainer and the reporter agree on the fix, not the timing. 42 comments
Why did this fail?
The migration ran before the env file loaded; DATABASE_URL was empty. line 118
Reading and drafting just happen. Anything it can't undo stops and asks, right on the piece.
Send, delete, rename many, pay: the fluid throbs and a chip appears. Nothing happens until you answer. "Allow all for this piece" exists for when you trust it; irreversible steps still ask.
After a run you liked, one tap turns it into a skill with a trigger. Drop a new PDF into that folder and it renames itself. The trust ladder is explicit: ask, then run and tell you, then silent, after it has been right a few times.
Three macOS permissions. Each has a button in the menu bar that opens the right pane. Your Claude credentials never pass through Inkling; it runs the claude you already signed into.
To find what's under the drop point and stay stuck to it when the window moves.
To read window titles and tab names in other apps, and to take a screenshot when the agent needs to look.
To ask Finder and browsers for the file path or URL under the piece instead of guessing.
Only the ones you drop it on, and the ones you tentacle in. It runs locally through your own Claude Code; nothing is uploaded by Inkling itself.
Claude Code today. Codex is detected and shown in the menu; driving it is next.
It lives in the menu bar instead, as a small bead. Same pull, same drop.
Inkling is free. It uses your Claude plan or API key, so the agent's work is billed there, like any Claude Code session.
⌃⌥⌘. retires every piece at once. Input injection pauses whenever you start typing.
Not right now. Inkling is closed source while it is early. The app runs locally and the privacy page says exactly what it does and does not send.
Download the zip, drag Inkling to Applications, open it. It walks you through the three permissions it needs.
Version 0.1.1 · 1.4 MB · Developer ID signed and notarized by Apple, so it opens like any other app. Something wrong? Write to aruntemme@gmail.com.