Multi-agent souls
Every agent has its own personality, memory, relationships,and tools — instantiated from a soul file, with predefined rules and trust levels.
bentokit · canvas runtime
Agent Operating System
Modular operating system for autonomous agents.
Memory, temporal awareness, federation, and a canvas of their own. BentoKit is a sovereign runtime where multi-agents persist, collaborate, and act between turns.
01Canvas Adaptability
The interface is part of the agent runtime.
Agents can create windows, arrange bento grids, surface the right widget, adapt the theme to your brand, and build new tools around your business workflows.
canvas · agent-controlled surface
live
Window Manager
Agents open, arrange, and close their own draggable surfaces.
Brand adaptation
Agents can adapt the theme to your brand — palette, layout, density.
Private extension catalog
Teams can ship internal tools, widgets, and workflow modules around their own operations.
02Federation
Agents that meet other agents.
BentoKit agents discover each other across machines, teams, and organisations — without a central server, without a SaaS handshake, without a shared tenant. Trust is earned, not assumed.
-
Peer discovery over mDNS on local networks or through known peer addresses.
-
Ed25519 verification cryptographic trust escalates on demand.
-
Four trust tiers none, discovered, verified, trusted.
-
A2A endpoints agents serve each other as collaborators.
· peer · london
· peer · tokyo
· peer · berlin
· verified ✓
03Memory isolation
Memory that knows its place.
Other tools rely on prompt-level hygiene to keep contexts apart. In BentoKit, isolation is structural — enforced at the storage layer, keyed to the workspace, scoped to the owner. Client A's context cannot reach Client B's.
-
Workspace-scoped enforced at the database layer, not the prompt.
-
Four privacy levels Public, Internal, Restricted, Secret.
-
Per-owner scoping contact-bound memory stays bound.
-
Decay-aware ages out the irrelevant, keeps the resonant.
Sofia M.
milestones
Q4 deck
design feedback
WhatsApp · Client
Marcus L.
renewal notes
Q3 numbers
agenda Monday
WhatsApp · Client
Riley P.
kickoff brief
milestone review
feedback
WhatsApp · Client
04Temporal Awareness
Agents that own their time.
Most frameworks are reactive — they wait for you to call them. BentoKit agents wake themselves. They schedule check-ins, watch for state changes, and act between turns.
-
Self-scheduling Pulse cadences — 30s, 5m, 1h, daily@09:00.
-
Five trigger types polling, webhook, websocket, file watch, cron.
-
Four-phase lifecycle system → maintenance → tasks → reflect.
-
Active windows quiet hours and timezone-aware sleep.
Tick · 30s
Cron · 09:00
Watcher · file
Webhook
05Tasks & Goals
A backlog of their own.
Agents keep a private board of tasks and long-term goals. They break a goal down, work through it between your turns, and show you what's done, what's stuck, and where the next move is — kanban-clean.
-
Five task states todo, in-progress, blocked, done, canceled.
-
Five goal horizons session, day, week, month, ongoing.
-
Auto-progress a goal's % climbs as its tasks close.
-
Stale-goal nudges neglected goals surface back into the planner.
Ship onboarding redesign
To Do
2
MED
Audit signup flow
LOW
Update screenshots
In Progress
1
HIGH
Draft welcome email
Blocked
1
URG
Approve hero copy
▸ waiting on Sofia
Done
2
Set up project repo
Wire Telegram bot
06Capabilities
The rest of the kit.
The pillars above are why people stay. Below is the runtime that makes them possible — security, observability, and the small decisions that compound into a serious agent platform.
Capability tiers
Clear permissions, clear limits, clear receipts. Everything an agent touches is on the record.
Human-in-the-loop
Dangerous moves wait. Each request explains its scope, lifetime, and consequences before you grant a thing.
Audit trail
Every grant, denial, module load, and approval is captured — per agent, per workspace, append-only.
Modular tools
Hot-reloadable modules ship tools in coherent bundles. Agents enable the right kit for the job and keep the rest out of context.
Team permissions
Define which agents each team member can summon.
Multi-provider
Bring any model — frontier, regional, or local. Switch per agent or per task without rewriting your stack.
Multi-channel
Agents reach you through CLI, Telegram, and the Canvas — any channel that fits where the work is happening.
Single binary
One file. Your machine. No install ceremony, no daemon zoo, no vendor lock-in.
0
runtime dependencies
1
binary, deployed
0%
on your machine
Your data, your hardware, your rules. No vendor will ever throttle, deprecate, or read what your agents remember.
07Built for
For people who treat agents like infrastructure.
Agencies
Run multiple clients in parallel without a single context cross-contaminating another. Memory walls are structural, not procedural.
Builders
Assemble autonomous systems whose agents persist, schedule themselves, and federate with peers across machines.
Teams
Ship internal tools, widgets, and operational workflows around the way your team actually works — modular, auditable, sovereign.
Bring persistent agents into your environment.
BentoKit is delivered as an installable package for teams that need private infrastructure, clear operational boundaries, and a product surface that adapts to the business.