Live Change Log

Every feature, fix and improvement, posted as it ships. Nothing is held back for a launch.

18,392

Total Changes

6,527

Features

5,537

Fixes

Projects

Filter by project

All Projects18,392 AIService276 APIService177 BillingService161 ConversionService117 DaemonService146 DocsService240 ESigService93 EmailService619 InitializerService344 KBService162 KlusterServices769 MCPGatewayService277 MediaService620 RAGService79 SecurityService1,995 TranslateService62 VOIPService265 VectorService11 kamo-apps26 kamo-asterisk-support28 kamo-capcha17 kamo-capcha-widget4 kamo-internal8,692 kamo-login342 kamo-marketing642 kamo-nowww20 kamo-register213 kamo-shared-library1,824 kamo-signer-monorepo57 kamolos114

Filter by type

All Types Build23 CI525 Chore794 Docs3,286 Feature6,527 Fix5,537 Other1,001 Performance174 Refactor281 Revert23 Style45 Test175 Upgrade1

October 18, 2026

FeatureMCPGatewayService

Leads, accounts and communications timelines for SIs (SITP TP10)

54 tools over SecurityService as the SI member, each right checked there as well as here: - leads: create, edit (masked values never written back), assign, bulk...

Kamo·3w ago

FeatureMCPGatewayService

Shared mailboxes, folders, stars, Trash, labels, attachments in and out, group chats, drips, files_upload, contact groups (SITP TP13)

27 tools and two new arguments, so an SI can work its mail and chat as a person does: - mail: mail_list_folders, mail_flag, mail_delete (to Trash only; a messa...

Kamo·3w ago

FeatureMCPGatewayService

The phone inbox, the do-not-contact list, contact call consent, text templates and MMS (SITP TP11)

22 new SI tools, each checked by the same rights at the gateway and at VOIPService/EmailService: - phone_list_voicemail, phone_voicemail_mark_read, phone_voicem...

Kamo·3w ago

FeatureMCPGatewayService

Every SI gets the report tools by its rights; config_* gated by rights, not audience

SITP TP00, owner decisions 2026-10-18: - reports_list, reports_run and metrics_get drop CP14's WATCH charter switch: an SI is offered them by VIEW_REPORTS and...

Kamo·3w ago

FeatureMCPGatewayService

Classify the ten iot tools; the catalogue guards move 101 to 111 (SP11 P12)

The three iot writes are NOT_DISCLOSING and the seven reads NOT_CONTENT with the spec's reasons (pinned in ContentReadToolsCoverageTest too). RegistryCompletene...

Kamo·3w ago

FeatureMCPGatewayService

IotCallerView and the pure view rules V1-V11 (SP11 §4.4)

A key a device lists twice is a manifest defect and is never used (fail closed).

Kamo·3w ago

FeatureMCPGatewayService

IotManifestClient, a per-session ETag-validated manifest cache with single flight (SP11 §4.4)

Kamo·3w ago

FeatureMCPGatewayService

Per-caller schemas and availability for the ten iot tools (SP11 §4.5)

Kamo·3w ago

FeatureMCPGatewayService

IoT error map, value checks, class check, whitelisted results and the command watch (SP11 §4.7, §4.9)

Kamo·3w ago

FeatureMCPGatewayService

IotPack, the ten iot_ tools on the Tool Plane (SP11 §4.6-§4.10)

Kamo·3w ago

FeatureMCPGatewayService

Downstream approval headers, conditional GET with ETag, opt-in error fields (SP11 P11)

Kamo·3w ago

FeatureMCPGatewayService

CallerSchema per caller after visibility; PHYSICAL after outside content always asks a person; the approval travels on the plan (SP11 P4-P7)

A static tool's schema and availability may depend on the caller (CallerSchema): viewed after visibility for tools/list (one 3 s budget shared by the list) and ...

Kamo·3w ago

FeatureMCPGatewayService

ToolRisk.PHYSICAL, the iot_ prefix, two charter classes, the IOT door and ApprovalRef (SP11 P1-P3, P8-P10)

Kamo·3w ago

October 15, 2026

FeatureMCPGatewayService

The No Insubordination Rule — an SI carries out a teammate's direct order on their rights

Owner 2026-10-15, refined the same day: "It should apply to any team member. But just because a team member (human or SI) has more rights, does not mean that au...

Kamo·3w ago

October 13, 2026

FeatureMCPGatewayService

An offered SI's send says what it was in the result's _meta["kamo.collab"] — purpose, urgency, regarding, intent source, outcome (SEND, or DEFER with deliverAfter), the colleagues reached with kind and person flag (the gate's own recipients when it judged them, else the plan's with CollabCallFacts.kindOf and the org graph), the thread and a consult's id; written before the key is DONE so a replay carries it, on delivered and deferred INTENT calls of SIs IntentOffer offers; content and structured...

Kamo·4w ago

FeatureMCPGatewayService

Tasks_list_comments shows a comment's kind and stance when it is not a plain comment — a POSITION, HANDOFF or ESCALATION row adds kind (and stance when it has one) for the disagreement protocol and the runtime; a COMMENT row, or one KBService gives no kind, is byte-identical to before (KamoCollab CP13 Task 9, D30)

Kamo·4w ago

October 12, 2026

FeatureMCPGatewayService

An SI whose PERSONALITY is configured is offered the intent arguments — IntentOffer = CP12's CollabOffer, or an SI with a configured personality; tools/list adds purpose, urgency and regarding to its INTENT tools, IntentResolver resolves its calls as an offered SI's (MISSING, never NOT_OFFERED) and its stated record joins the communication-policy question; the collab_* tools and the ENFORCE rejection of a missing purpose keep CP12's offer; an SI with neither section keeps the golden schemas byte...

Kamo·4w ago

FeatureMCPGatewayService

An SI hands its task to a colleague and states its position on a task — collab_handoff and collab_position (pack collab, AI_ONLY, EDIT_NOTES, opened by CP11's charterSwitch DocsTION, offered in ENFORCE too): a hand-off names an active colleague other than the SI (else INVALID_ARGUMENTS NOT_A_COLLEAGUE) and a task the SI can read and is the assignee or creator of (a task without a recorded creator is its list owner's; else, or unreadable, INVALID_ARGUMENTS NOT_YOUR_TASK); it is ASSIGN_WORK j...

Kamo·4w ago

FeatureMCPGatewayService

An SI asks a colleague and answers an SI that asked — collab_consult and collab_answer (pack collab, AI_ONLY, opened by CP11's charterSwitch DocsTION, offered in ENFORCE too): a consult to an SI colleague that takes consults (its org in ENFORCE or its own DocsTION switched on, else COLLAB_DENIED NOT_DocsTING) is recorded in kamoai-service's POST /api/kamoai/internal/consults with the asking run as parentRunId and the run's onBehalfOf chain plus the SI (more than five, or back alon...

Kamo·4w ago

FeatureMCPGatewayService

The Tool Plane's build identity and an SI's daily Docstion counts — GET /api/tool-plane/internal/build answers {service:"mcpgatewayservice", version, time} from Spring Boot's BuildProperties (pom.xml runs build-info; both null without it); GET **************** answers {orgId, memberId, day, contacts:{started, replies, deferred, rerouted, denied, approvalRequired}, escalationSends} for one SI and UTC day from its real, gate-stamped calls in its org...

Kamo·4w ago

FeatureMCPGatewayService

An SI's first contact with an outside person needs CONTACT_NEW_PERSON (defect 7) — mail_send and mail_forward list each outside address (email:<lower>), sms_send and an outside phone_call the number (phone:<E.164>), as ToolPlan.FIRST_CONTACT for an SI, and each declares CONTACT_NEW_PERSON; the Docstion gate, for every SI and not on an approved re-execution, drops the people the run already speaks with and asks AIService's POST **************** (FirstContactClient: 20 ...

Kamo·4w ago

FeatureMCPGatewayService

Rehearsal run contexts on the Tool Plane — a run whose context carries CP15's rehearsal block takes dry-run calls only (a call or tools/list without X-Kamo-Dry-Run answers UNAVAILABLE REHEARSAL_RUN_DRY_ONLY before anything runs); simulateEnforce judges that run in ENFORCE (EffectiveDisclosureMode) in the audience filter, the read audience, the disclosure gate and disclosure-check, and the tool list (disclosure_request, basis, sourceRef); a non-blank privateContext is recorded as the run's Confid...

Kamo·4w ago

FeatureMCPGatewayService

SI loop guards in the Tool Plane — an SI's tasks_comment sends aiTurnLimit and its mail_reply the multipart field aiTurnLimit, both its charter's maxAiOnlyChatTurns (6 by default), so KBService's and EmailService's thread turn guards hold it to its own limit (their 429 AI_TURN_LIMIT answers WAIT_FOR_HUMAN, as in chat; a person's comment or reply is unchanged); and the SI pair budget (AiPairBudget): beside the charter's limit counters, an SI's disclosing send takes one unit on kamo:collab:pair:<o...

Kamo·4w ago

FeatureMCPGatewayService

A deferred SI message goes through the disclosure gate to the outbox — when the Docstion gate DEFERs an SI's chat_send in a direct chat or its mail_send to one colleague, the call still meets CP07's disclosure gate (an ENFORCE refusal stops it, nothing queued), the charter's outcome, the limits and the outreach gate, and OutboxDefer then replaces the handler: the gate's snapshot (with the run's sealed excerpts of its sources) is kept 73 h as kamo:tool:held:outbox:<itemId>, the item is poste...

Kamo·4w ago

FeatureMCPGatewayService

The Docstion gate — an SI's call of an INTENT tool is judged where CP04's interaction gate stood: its intent (ToolPlan.INTENT; an offered SI of an ENFORCE org that starts a contact without a purpose is refused INVALID_ARGUMENTS INTENT_REQUIRED), CP04's communication policy as step 1 (a refusal stamps COLLAB_DENY interaction:<ruleId>, an approval it asks for COLLAB_REQUIRE_APPROVAL), then, for an SI whose DocsTION charter is configured only, CollabCallFacts and DocstionPolicy per r...

Kamo·4w ago

FeatureMCPGatewayService

The reports pack — reports_list, reports_run and metrics_get under the caller's own report rights (KamoCollab CP14 Task 12)

reports_list reads SecurityService's report library on the caller's session: the reports they may run, the measurable metrics of those reports and, for an SI ca...

Kamo·4w ago

FeatureMCPGatewayService

The SI intent arguments — purpose, urgency and regarding on an offered SI's INTENT tools (CollabTools: INTENT and NO_INTENT with reasons, every disclosing tool ruled), injected by tools/list only for an SI whose Docstion is configured or whose org is in ENFORCE (an unconfigured SI of an AUDIT org keeps byte-identical schemas), taken out of an SI's arguments beside onRequestOf before the schema check, the planner and the args hash and checked (INVALID_ARGUMENTS with field); IntentResolver: v...

Kamo·4w ago

FeatureMCPGatewayService

Seed an SI run's source ledger, and the WATCH charter switch — POST **************** (X-Internal-Auth) takes {orgId, memberId, items:[{ref, excerpt}]}: 1-5 canonical refs with excerpts of at most 4,000 characters (else 400 items), labels them through LabelService and records each in the run's source ledger as a read of tool runtime:signal, its excerpt sealed (204); a run with no registered context of this SI is 404 RUN_CONTEXT_MISSING; an AUDIT org whose calls go une...

Kamo·4w ago

FeatureMCPGatewayService

Knowledge_context — an SI's standing knowledge through kbservice's GET /api/notes/ai/context, passed through: Our Master Note, the knowledge notes (the charter's, then its teams' and departments' pinned notes) and the decisions in force, each entry its NOTE at /orgMaster/i, /knowledge/i and /decisions/i; pack memory (AI_ONLY, NOTES, READ, VIEW_NOTES), offered only when the SI's charter sets maxContextKnowledgeChars to 1 or more (ENFORCE alone never offers it); at most 8 noteIds; a strict read, s...

Kamo·4w ago

FeatureMCPGatewayService

The SI memory tools, the charter switch and strict reads — memory_record, memory_search and memory_forget (pack memory, AI_ONLY) over kbservice's /api/notes/memory; ToolDescriptor.charterSwitch, the program's one opt-in rule (R1-5): a tool naming a switch is offered to an SI only when its charter sets that LIMIT key to 1 or more, or its org is in ENFORCE and the switch lets ENFORCE offer it, else hidden as CHARTER_SWITCH_OFF; the memory tools' switch is maxMemoryCards with ENFORCE offering nothi...

Kamo·4w ago

FeatureMCPGatewayService

Label on write for SI memory — LabelOnWrite.forMemory links a card or a memory-on SI's journal line to every labelled source of its run, or, in ENFORCE with the leak check on, to its basis alone when the check finds the fact clean of everything else the run read (LEAKS, UNSURE, a failure, a source without its excerpt, AUDIT and a disabled check keep every source); unlabelled content and a source past 49 add AI_RUN:<runId>; the highest sensitivity of every chosen source, Confidential when any is,...

Kamo·4w ago

FeatureMCPGatewayService

Disclosure readiness — GET **************** answers whether an org may switch to ENFORCE: pack coverage (every READ static tool ruled LABELED or NOT_CONTENT), the excerpt key, and one leak-check probe with a fixed synthetic draft and excerpt (REACHABLE on any verdict but AIService's no-model UNSURE, within 8 s; DISABLED when the org's leak check is off), with the org's SI-enabled federated servers and its last seven days of WITHHELD, WOULD_WITHHOLD and UNLABEL...

Kamo·4w ago

FeatureMCPGatewayService

Label on write and the runtime's two internal endpoints — an SI's notes_create, notes_update, notes_append_journal and notes_master_append in a run send, in the same request, LEARNED_FROM links to what the run read (its basis, else every labelled source of its ledger; never an unlabelled one or an AI_RUN; at most 50, newest first), the highest sensitivity among them and the Confidential marker with its highest-ranked setter (org owner, then effective level, then id; an unknown setter stands for ...

Kamo·4w ago

FeatureMCPGatewayService

Decisions and note sharing for an SI of an ENFORCE org — decisions_search lists the decisions and summaries it may read, each named as its NOTE; decisions_create records one released at birth and notes_share gives one of its own notes a new audience, both through kbservice's internal release endpoints with the basis the disclosure gate allowed the call on (CLEARED with no grant, VERIFIED_REQUEST by a verified request's author, APPROVAL by the information owner whose release cleared it; without o...

Kamo·4w ago

FeatureMCPGatewayService

Disclosure_request and the approval status of a proposal — an SI of an ENFORCE org passes a colleague's question on to the owners of what its run's reads withheld: forMemberId must be in the run's audience, each withheld source (newest first) goes to its first release owner other than the requester, at most 5 owners with 10 sources each, one RELEASE_PROPOSAL (reason DISCLOSURE, class RELEASE_INFORMATION) per owner keyed <key>:owner:<id> with only that owner's sources, at most 3 calls a run; the ...

Kamo·4w ago

FeatureMCPGatewayService

Approved releases, their re-execution and chained approvals — the information owner's approval of a held send is recorded in its snapshot as their OWNER_RELEASE over the sources it was asked for (the snapshot now names that asked release), and the gate decides again from the snapshot with fresh labels, needing neither the run's context nor its ledger; a release that no longer covers the send (a marker set meanwhile) is DISCLOSURE_DENIED, never asked again; a release reaches only the recipients i...

Kamo·4w ago

FeatureMCPGatewayService

The disclosure gate — an SI's call of a disclosing tool is judged after CP04's interaction gate and before any approval: the run's source ledger, the records the call carries and its basis (which must be what the run read, else BASIS_NOT_READ in ENFORCE) are labelled now and decided with DisclosurePolicy, the verified request as a VERIFIED_REQUEST grant and a held snapshot's releases as OWNER_RELEASE; in ENFORCE the run's other uncleared reading goes to the bounded leak check (LeakPrefilter, Lea...

Kamo·4w ago

FeatureMCPGatewayService

The basis argument — an SI of an ENFORCE org sees the optional basis (up to 20 sourceRefs, KIND:id) on every disclosing tool, static or dynamic; the pipeline takes an SI's basis out of a disclosing tool's arguments in every mode before the schema check, the planner and the args hash, checks it as its schema would (a malformed item is INVALID_ARGUMENTS) and keeps its refs for the disclosure gate; an AUDIT org's list is byte-identical; DISCLOSURE_DENIED (error, DENIED) and BASIS_NOT_READ (error, I...

Kamo·4w ago

FeatureMCPGatewayService

An SI's task writes, lead notes, master-note entries and workstation typing write their disclosure plans — a task reaches its participants after the call as its TASK label names them (creator, list owner, assignee, and the supervisor of an SI owner or assignee; an update and a comment read the label, a create and an assignment name who they leave, the assignment carrying the task without its old assignee), a lead note the organization through the lead label's required rights, who-i-am the public...

Kamo·4w ago

FeatureMCPGatewayService

An SI's sends write their disclosure plans — chat lines and mentions reach the conversation's members (a support conversation's visitor too), mail the members its addresses reach and every other address (a shared mailbox included) aliased by the lead it is about, a reply or forward carrying the original's thread, a text or call the number aliased by its lead or contact (a colleague call the colleague), an invitation the invited colleagues, a join the meeting's participants and guests with an emp...

Kamo·4w ago

FeatureMCPGatewayService

CRM, document, calendar, call and notification reads name their records — each lead, account, contact and document by its id, each event (an occurrence by its series) and meeting as its CALENDAR_EVENT, each call row by its callLogId (none: unlabeled), each notification as the record it is about when its source is one; in an EXTERNAL or MIXED run of an ENFORCE org leads_get asks for the lead's external projection (fieldAudience=EXTERNAL); federated and workstation reads are one unlabeled item; Co...

Kamo·4w ago

FeatureMCPGatewayService

Notes, tasks, KB and RAG reads name their records — each listed or read note is its NOTE, each task its TASK, each article its KB_ARTICLE by the row id (the output's articleId stays the guid), each RAG passage its note or article and each link target its article; in a filtered run of an ENFORCE org rag_search narrows the search to the run's audience from its context and the org graph (audienceMembers, audienceExternal), never the model's choice, and the audience filter still drops what RAGServic...

Kamo·4w ago

FeatureMCPGatewayService

Chat, mail and SMS reads name their records — every listed or read conversation is its CHAT_SESSION (a support conversation too), every message its EMAIL_THREAD by the threadKey mail summaries and full reads now carry (none: unlabeled), every text conversation its SMS_THREAD; the nine tools leave PENDING_ITEMS, and a result of a tool that names its items but named none (an empty list) is no withheld record (KamoCollab CP07 Task 18)

Kamo·4w ago

October 11, 2026

FeatureMCPGatewayService

The config pack — config_catalog, config_current, config_lookup and config_propose, a person's reads (HUMAN_ONLY, READ, AI Workforce, any of the four hiring and configuring rights) that ask SecurityService's configure endpoints with the caller's OTK, AIService's voice options with the *** and the knowledge base under the caller's own right and app; a refusal reaches the model by its reason; the four tools are not content (CP10 D27), Js gains anyObject, anyObjectList and uuidList, and config_ j...

Kamo·4w ago

FeatureMCPGatewayService

Tool Plane Docstion foundations: SI charter views (Docstion, personality, escalation route members), recipient preferences client, attention and delegation counters, the offer rule, the DEFERRED and REROUTED statuses and the six audit columns (KamoCollab CP12 Task 23)

Kamo·4w ago

FeatureMCPGatewayService

The audience filter on an SI's reads — ToolOutcome.items and ContentItem, ContentReadTools (every READ tool labeled or not content, pre-checks and counts), the pre-check before the handler and the filter after it (ENFORCE removes what the run's audience may not know and answers a withheld record as "Not found."; AUDIT changes nothing and records WOULD_WITHHOLD), the source ledger and withheld store, read stamps through CallLedger.readOutcome, and cached work links (KamoCollab CP07 Task 17)

Kamo·4w ago

FeatureMCPGatewayService

The DDL file for the tool audit's six Docstion columns (KamoCollab CP12 Task 4)

Kamo·4w ago

FeatureMCPGatewayService

The disclosure ledger completeness check, GET **************** every gate-stamped SI call has exactly one matching event, no SI send skipped the gate, no SI event lost its audit row (KamoCollab CP08 Task 11)

Kamo·4w ago

FeatureMCPGatewayService

Every channel's planner writes its interaction plan — an SI's team-chat line and new DM, internal mail (members its recipients reach, the original's sender as a reply), colleague call, meeting invitation, calendar invitation and work given to a colleague carry the communication policy's answer for each colleague, through emailservice's member mailboxes (KamoCollab CP04 Task 22)

Kamo·4w ago

FeatureMCPGatewayService

Labels with the principal-private fallback, the source ledger with encrypted excerpts, withheld items and held decisions; mount the platform key (KamoCollab CP07 Task 16)

LabelService resolves labels through CP05's DisclosureLabelClient over the six owners (60 s cache per org and ref; inherited refs to depth 3); a ref no owner la...

Kamo·4w ago

Like what you see shipping?

All of it arrives in your workspace on its own. Start on the free plan and read this page again in a month.

Start Free Forever View Pricing