Pi Alignment
Anyy v0.1.107 is a native Go personal assistant. Its shared assistant behavior uses Pi v1.2.0, commit 06a466935536f8c9bcacb2d5efc0fc021be1bdff, as the fixed reference. The release commit is da60fa116a7d23c9989b9a9181b861b1e838716c.
This page describes the shipped release. Development milestones and private test-instance handoffs are historical engineering records, not prerequisites for using these features.
Shared contracts
| Area | Implemented behavior | User documentation |
|---|---|---|
| Agent loop | Fixed-source message, event, tool-call, cancellation and loop-control behavior | Sessions |
| Canonical messages and providers | Preserve message/tool declarations and lower requests at the provider boundary; five native inference API families are in scope | Provider protocols |
| Prompt construction | Pi construction and request ordering, with the defined Anyy identity and personal-assistant context supplied by the product layer | Roles |
| File and shell tools | Native read, bash, edit, write, grep, find and ls, subject to actual tool selection | Files and terminal |
| Skills | Discovery, selection and reading of Skill instructions; Anyy's managed installer accepts local ZIP packages | Skills |
| MCP | stdio and Streamable HTTP, authentication, tool exposure and resource interfaces | MCP |
| Codemode | JavaScript execution with the Session's callable tools and selected branch store; independent of Roles | Codemode |
| Tool search | Discovery of inactive tools and activation for subsequent requests | Tool search |
| Conversation inputs | Steering, follow-up and abort, with each surface's documented controls | Dashboard Chat, TUI |
| Compaction and branches | Context compaction, branch summaries and selected-history behavior for ordinary Sessions | Compaction |
Product ownership
Gateway orchestration, persistence, Profile isolation, interfaces and platform delivery remain outside internal/agent. Anyy also owns Roles, personal memory, tasks, schedules, background work, credential protection and sender authentication. These product responsibilities do not create a second loop inside the Pi-aligned kernel.
Canonical tool declarations and executable handles are separate. A historical tool name does not grant execution access. Configuration, registration and a successful external call are distinct states; consult the feature's setup and troubleshooting instructions.
Independent system notifications have recoverable display history. They are not manufactured assistant messages and do not enter model context merely because a page is reopened. See Notifications and delivery.
Scope exclusions
The full experimental Durable Harness/Chord framework is not included. Ordinary persisted Sessions, branch compaction and Anyy's personal memory are separate capabilities.
The additional Pi native APIs for Azure, Bedrock, Vertex, Mistral Conversations and pi-messages are outside this release's five-family inference scope. A vendor available through a compatible endpoint does not imply support for its separate native API.
Tool approval modes, ChangePlan and dedicated Browser Use/Computer Use are retired. OAuth authentication and sender pairing remain real access boundaries.
Verification and source
Use anyy --version to identify the binary you are running. Releases include macOS and Linux artifacts for amd64 and arm64. Mac scenario acceptance and cross-compilation do not certify every external account, provider, OAuth deployment or device; TR3000 runtime qualification is separate.
Implementation details are recorded in the release-pinned alignment contract and the fixed upstream source. Earlier snapshots retain their provenance in the repository's phase records rather than appearing as current setup steps.