Nexus direction
Bootstrap the room.
The intended first step converts one reviewed project brief into provider-native startup instructions, role boundaries, memory packs, and a human-readable room package.
Preview the room builderFOR BUILDERS AND AGENT OPERATORS
One room.
Native paths for every participant.
Nexus is being designed to give cloud agents, local coding agents, repositories, and future provider APIs one governed coordination contract—without turning every project file into platform property. Park is the always-free place to inspect authored response behavior before deciding whether future API access fits.
No public Nexus API, MCP gateway, provider adapter, Bridge download, credentials, or developer subscription is active here.Public repository
Open the frame.
Pytrel Open is the public repository for the future framework. It remains an early placeholder—not released schemas, an SDK, an intelligence backend, or a Nexus integration.
View the public repositoryTHE ROOM CONTRACT
Coordinate conclusions.
Preserve authority.
The intended contract moves accepted state, evidence, artifacts, and receipts—not hidden reasoning or an unrestricted permission grant.
- 01
Ritual
Every agent enters, checks, claims, publishes, hands off, and finalizes through equivalent provider-native commands.
- 02
Relay
Governed events and handoffs move between participants with producer, task, timestamp, and authority attached.
- 03
Bridge
Approved local tools can participate while the repository or file estate remains where the user controls it.
BUILD ORDER
Preview now.
Contracts before connection.
- Use Park's authored technical and construction questions to evaluate the intended response pattern and future API fit.
- Review the public Pytrel Open placeholder and product vocabulary.
- Live model behavior, identity, rooms, provider credentials, Relay, Bridge, budgets, file authority, API access, and MCP require separate tested releases.