Capture decisions, versioned skills and rules once. Every AI agent you use retrieves the same traceable context, no more repeating yourself across tools.
Why BIKO?
Other assistants live in browser tabs, disconnected from your actual workspace tools. BIKO brings AI directly into your developer terminal, documents, calendars and tickets, keeping your operations fully integrated.
Capture facts, decisions, meeting summaries and corrections as compact structured events with source, actor and timestamp.
@BIKO what did we decide about client copy?
Decision (Oct 27): use British English in all client-facing copy. Source: kickoff meeting, recorded by owner.
Perfect, applying it to the draft.
Copy a project context bundle as Markdown or JSON into ChatGPT, Claude or a custom agent. Or connect over MCP. The connector is live.
Paste or fetch BIKO context
Same decisions, same rules
Key-protected REST API
BIKO holds the context; your agents bring the model. No lock-in to one assistant.
The four pillars
What your organization knows, how it works, what agents must respect and what improves with human-approved evidence.
Seven event types with JSON payloads and human-readable summaries, capped at 16 KB each.
Reusable Markdown procedures with full revision history. Scripts are stored as metadata and never executed.
Required fields, types and constraints checked by code, clearly separated from anything that needs judgement.
Retrieve a bounded bundle of decisions, events, skills and rules for a project or task, with source IDs.
Every change is recorded with actor, source and time. The log cannot be edited or deleted.
Full-text search across projects, memory, skills and rules from anywhere with Cmd/Ctrl+K.
Traceable decisions
Every decision and correction keeps its source, actor and timestamp, so any agent or person can trace where an answer came from.
Record a correction once and every agent retrieving project context sees it first.
Agents can log what they did and the outcome, building a trail for later review.
Context bundles cite event, skill and rule IDs with versions. No invented summaries.
Get context for: write client status update
Acme website relaunch
2 found, newest first
Full-text match on task
client-status-update v2
Status update must include risks
Copied as Markdown
Scope
Project: Acme website relaunch. 2 decisions, 1 correction, 1 skill (v2) and 1 active rule matched the task “write client status update”. Each item links back to its source event.
From decisions, skills and rules in this project
Context retrieval
BIKO uses full-text matching and recency today. Every result shows where it came from.
Bundles stay within one project plus global skills and rules.
A fixed result limit keeps context compact and predictable.
Copy for humans or machines with one click.
Pricing
Start personal, scale to your whole team. We are at capacity right now, so join the waitlist to reserve your seat.
Shared memory for teams and their agents.
Isolated client workspaces and governance at scale.
Prices in EUR. Seats open in waves as capacity frees up.
Integrations
What rules apply to client status updates?
One active rule: include risks and an owner. Skill to use: client-status-update v2.
@BIKO draft this week's update with that skill
Retrieve a project context bundle and paste it into any assistant. Works today with ChatGPT, Claude and custom agents.
Get project context for Acme website relaunch.
BIKOEight tools are built: search, project context, writing memory, recording executions, reading skills and rules. Each one asks the caller to sign in first.
A key-protected JSON API for search, context, skills and rules. Off by default; writes need a separate switch.
FAQ
Straight answers about how BIKO works.