feat(cli): agent-native provisioning with init --agent and agents claim - #699
feat(cli): agent-native provisioning with init --agent and agents claim#699wondercreatemaster wants to merge 1 commit into
Conversation
Closes vouchdev#606. Lets an agent provision its own KB and identity, keep a local credential off stdout, and hand a human a claim token that binds the agent to a project through the adopt review gate.
|
flagging three things before a maintainer spends time on the +987 diff, because two of them are mechanical and one is scope. CI is red — the file list has a gap that matters more than the coverage number: on scope: this introduces a credential file, a claim-token flow, an ownership-transfer path and a new persistent proposer identity, in one PR, alongside a rewrite of last, minor but it is a house convention: the description carries a "Made with Cursor" trailer. this repo is explicit about not attaching AI-tool attribution to contributions — worth dropping it. happy to review the substance properly once CI is green and the adopt changes have tests; nothing above is a judgement on the approach. |
|
Superseded by a replacement PR that addresses the review notes on this one:
|
Summary
vouch init --agent --agent-caller <name>provisions an agent-scoped KB, stampsagent.calleras the persistent proposer identity, and writes a local credential (chmod 0600) that is never echoed to stdoutvouch agents claim <token>command (plus--jsonfor skills); claiming from a project KB transfers ownership and adopts knowledge through the same review gate asvouch adopt, leaving the agent credential and agent-KB artifacts untouchedagent.callerwhenVOUCH_AGENTis unsetTest plan
python -m pytest tests/test_agent_provision.py tests/test_adopt.py -qpython -m ruff check src testspython -m mypy srcpytest tests/ -q --ignore=tests/embeddingsgreen locallyvouch init --agent --agent-caller demo --json→ credential path exists, stdout has no credential value →cd project && vouch init && vouch agents claim <token>binds and adopts