Skip to content

Add a context-sync input that pulls and pushes the project's context - #12

Merged
asgeirf merged 1 commit into
mainfrom
context-sync
Sep 26, 2026
Merged

asgeirf merged 1 commit into
mainfrom
context-sync

Conversation

@asgeirf

@asgeirf asgeirf commented Sep 26, 2026

Copy link
Copy Markdown
Contributor

A project whose kapi.yaml declares a context backend (context: backend: git|file|s3, from kapi 1.3) keeps its terms, voice profiles, approved wording and decisions there. context-sync: pull runs kapi context pull before the command; true also runs kapi context push after it, except in plan mode. Pushing a git backend needs contents: write; a fork's pull request can pull and cannot push.

Wait for the kapi release that ships kapi context pull|push (neokapi #2971) before merging; nothing here is tagged.

🤖 Generated with Claude Code

A project whose kapi.yaml declares a context backend (kapi 1.3 and later)
keeps its context there; the input pulls it before the command and, when
true, pushes what the run recorded after it.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NcQUx2CZv5hQhQHiNRQyGX
@asgeirf
asgeirf merged commit baf1163 into main Sep 26, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant