VanillaCore Agent Harness
  • TypeScript 97%
  • JavaScript 2.9%
  • Dockerfile 0.1%
Find a file
2026-11-07 10:09:19 +00:00
.agents/skills/web-search feat: skill metadata injection modes with late skill discovery 2026-10-27 15:28:45 +00:00
deploy/kubernetes Complete Hayate public runtime and deployment naming 2026-11-02 06:26:17 +01:00
development-evidence feat(setup): document WebUI and Matrix activation with safe starter defaults 2026-11-06 16:22:14 +01:00
docs build: pin published Matrix attachment plugin 2026-11-07 11:08:59 +01:00
evidence fix: bound and persist retained task assessment retries 2026-10-29 22:01:09 +00:00
scripts build: ship pinned optional WebUI assets in npm and runtime image 2026-11-06 18:20:03 +01:00
src feat(matrix): expose attachment protocol and verify encrypted roundtrips 2026-11-07 11:04:15 +01:00
test feat(matrix): expose attachment protocol and verify encrypted roundtrips 2026-11-07 11:04:15 +01:00
.dockerignore Initial public VanillaCore Agent Harness, Apache-2.0 2026-10-23 10:00:10 +02:00
.gitignore build: ship pinned optional WebUI assets in npm and runtime image 2026-11-06 18:20:03 +01:00
.node-version Pin current dependencies and document runtime operations 2026-10-23 10:13:18 +02:00
compose.yaml feat: use Hayate package CLI and canonical local agent paths 2026-11-01 22:28:41 +00:00
Dockerfile build: ship pinned optional WebUI assets in npm and runtime image 2026-11-06 18:20:03 +01:00
LICENSE Initial public VanillaCore Agent Harness, Apache-2.0 2026-10-23 10:00:10 +02:00
operator-reset-compatibility-IMPLEMENTATION.md docs: hand off legacy operator reset compatibility evidence 2026-10-30 12:54:31 +00:00
package-lock.json fix(cli): separate model reload and make foreground restart functional 2026-11-06 08:44:28 +01:00
package.json build: ship pinned optional WebUI assets in npm and runtime image 2026-11-06 18:20:03 +01:00
plugin-assets.lock.json build: ship pinned optional WebUI assets in npm and runtime image 2026-11-06 18:20:03 +01:00
plugins.lock.json build: pin published Matrix attachment plugin 2026-11-07 11:08:59 +01:00
README.md build: ship pinned optional WebUI assets in npm and runtime image 2026-11-06 18:20:03 +01:00
tsconfig.json Initial public VanillaCore Agent Harness, Apache-2.0 2026-10-23 10:00:10 +02:00

Hayate Agent

Hayate Agent

An AI agent for your terminal, browser and Matrix. Work on code interactively, pick up conversations later, or run Hayate as an always-on assistant for scheduled tasks and longer projects.

Hayate manages conversations, task queues, scheduling and message delivery. It uses Pi as its current model and tool runtime; no separate Pi installation is required.

Get started

You need Git and Node.js 22.19 or newer with npm. Node 24 LTS is recommended. Linux, macOS and Windows through WSL2 are supported.

git clone https://github.com/hayate-agent/core.git "$HOME/hayate-agent"
cd "$HOME/hayate-agent"
npm ci
npm install --global --prefix "$HOME/.local" .
export PATH="$HOME/.local/bin:$PATH"

cd /path/to/your/project
hayate-agent

Keep the checkout: the local installation links to it. Add the PATH setting to your shell profile if needed. In the terminal interface, use /login to connect a model provider and /model to choose a model. Existing Pi provider settings in ~/.pi/agent can be reused; custom providers are configured in models.json.

Ask Hayate to inspect a project, explain code, make a change or run tests. Use /help to explore commands and /sessions to return to an earlier conversation.

What Hayate can do

  • Code in the terminal: streaming responses, tool activity, session history and configurable tools in a fullscreen interface.
  • Work across conversations: keep independent conversations and durable queues, with explicit session selection and resumption.
  • Run ongoing tasks: heartbeats, cron jobs, recurring loops and standing goals.
  • Delegate work: route tasks to model roles and validate sequential steps before moving on. Models and reasoning levels are configurable.
  • Use a browser: an optional local WebUI plugin with persistent chats, streamed responses and agent-configurable presentation.
  • Connect through Matrix: DMs and rooms, encrypted conversations, user allowlists, mention rules and tool-approval handling.
  • Integrate with applications: an HTTP run API with streamed progress, optional MCP tools and trusted plugins for commands, channels and policies.
  • Make it your own: SOUL.md for identity, VOICE.md for tone and skills for reusable procedures.

Choose your interface and starting configuration

The terminal works without an initialization step. For an explicit profile:

hayate-agent init --home "$HOME/.hayate-agent" --cwd /absolute/path/to/workspace
# After enabling the desired gateways:
hayate-agent run --home "$HOME/.hayate-agent"

init creates a commented starter configuration and identity files, without replacing existing files or installing plugins. A copyable starter YAML is included in Core.

Follow the terminal, WebUI, Matrix and dispatcher setup guide:

Interface / feature Activation
Terminal Run hayate-agent; use /login, /model and /help
WebUI Select the packaged optional plugin under dist/optional-plugins/webui (or install it separately); configure gatewayPlugins.webui.module; open http://127.0.0.1:3210
Matrix Bundled plugin; inject MATRIX_HOMESERVER, bot credentials and sender/room policy
Dispatcher Optional; verify backend concurrency, then enable dispatcher and restart
HTTP run API Separately enabled with API_SERVER_KEY or a private loopback key file

WebUI remains local-only; do not forward it into a network before authentication and user isolation are implemented. Matrix encryption requires persistent device and crypto state. Supply credentials through your secret manager or environment, never through a public configuration file. Use a supervisor for always-on use.

The default configuration does not start background dispatch, prescribe a model/context size or grant remote operator rights. See the setup guide for explicit admin/approver configuration and optional WebUI customization tools.

Everyday commands

Task Commands
Start or resume a conversation /new, /title, /sessions, /resume
Control current work /stop, /queue, /steer, /busy
Schedule work /goal, /heartbeat, /loop, /cron
Choose models and reasoning /model, /reasoning, /model-roles, /reload-models
Manage context /compact, /skills
Find help /help, /status

Command availability depends on the channel and your permissions. Use /reload-models after changing provider/model configuration and /reload-skills after changing skills. /restart restarts the installed native CLI after draining work; it resumes the selected interactive conversation.

Configuration and safety

Agent state defaults to ~/.hayate-agent. Set HAYATE_AGENT_HOME to use a separate profile. An optional hayate-agent.yaml configures the agent, tools, scheduling and model roles. Provider credentials live separately in ~/.pi/agent or the configured PI_CODING_AGENT_DIR. Back up both locations for persistent services.

Tool approvals are off by default; enable them for tools that require human confirmation. Plugins run as trusted process code, not inside a sandbox. Queue persistence does not make external side effects exactly-once: after an interrupted operation, reconcile its actual result before repeating it.

Slack and Telegram adapters are not included. Web chat is available through the separately installed WebUI plugin, not as a built-in Core web server.

Contributing

Create a feature branch, add tests for your change and run:

npm ci --include=dev
npm run typecheck
npm test
npm run build

Open a pull request with the problem, the change and its verification. See the development guide for architecture and testing details.

License

Apache-2.0.