New Tools For Ikigai

I just merged rel-09 into Ikigai. The headline feature was the web tools; search through brave or google plus a web fetch tool.

What’s Coming in rel-10

The List Tool

Claude Code has a TodoList, but it’s fairly limited. The new Ikigai list tool provides Redis-inspired operations for both FIFO and LIFO queues:

lpush   rpush
lpop    rpop
lpeek   rpeek
list    count

Agents handle this kind of structure well. With clear prompts, they treat queues the same way they treat simple task lists, just with more control over ordering and retrieval.

Distributed File System

The next release adds what I’m calling Ikigai’s internal file system. Since Ikigai maintains a 1:1 relationship with the user (not with a project or machine), it needs a way for agents to share files across contexts.

Files will use a URI prefix: ik://shared/notes.txt. System prompts make clear that agents can use these paths with any file tool. Under the hood, Ikigai translates ik:// to normal filesystem paths, but the agents don’t need to know that.

The first implementation keeps it simple. We map ik:// to $XDG_STATE_HOME/ikigai, which with a default install ends up at $HOME/.local/state/ikigai.

No distributed storage yet, but a good aproximation for now. A true distributed system will come as we move further towards a client/server architecture in the future.

Why These Matter

The queue is useful for everyday agent work. Refactoring a list of files, processing items one by one, tracking what’s done and what’s left. Agents already do this kind of thing, now they have a proper data structure for it.

The internal file system is where shared skills will live. Some skills will be project-specific, but skills that need to work across projects go in ik://.

Co-authored by Mike Greenly and Claude Code