Hackable Agentic REPL

npm i -g talkpile

Ensure OPENAI_API_KEY is set, then run:

talkpile-service # Start the service in one terminal

talkpile # Start the client in another terminal

# copy the starter plist file to your LaunchAgents directory
cp ./etc/talkpile.service.plist ~/Library/LaunchAgents/talkpile.service.plist

# edit the file, replacing placeholders
vim ~/Library/LaunchAgents/talkpile.service.plist

# run...
talkpile-service-init

The talkpile-service-init command will register the service with launchctl, kickstart it, and then tail the logs to get you up and running.

Note that if you already have the service running, the talkpile-service-init command will stop the service, unload it, and then re-register it.

Once you have the daemon installed, you can use the following commands to manage it:

# check service status
talkpile-service-info

# start the background service (restart if running)
talkpile-service-start

# tail the logs
talkpile-service-logs

# stop the service
talkpile-service-stop

# kill the service
talkpile-service-kill

# toggle verbose logging
talkpile-service-kill SIGPIPE

# register the service
talkpile-service-load

# unregister the service
talkpile-service-unload

Configuration is stored in a .talkpile.yaml files.

Files are searched for in the following locations:

1. The current working directory, or any parent directory of the current working directory
2. The user's home directory ($HOME or %USERPROFILE%)
3. The system's config directory (/usr/local/etc or C:\ProgramData)

The data of all found files is deeply merged, with the most specific file taking precedence.

Here's an example .talkpile.yaml file:

user:
  name: Mac
  location: Chicago, IL
context:
  notes_dir: /Users/mac/Library/Mobile Documents/iCloud~md~obsidian/Documents/Green
agents:
  pirate:
    designation: pirate
    name: Jackdaw Hawkins

See .talkpile/ directory for more examples.

Apache-2.0