Move Agent Assist into Attik repos
Objective
- Put the Agent Assist application source code under Attik-controlled version control so routine fixes and releases no longer depend on an external contractor for repo access or merge rights.
- Unblock the rest of the ownership transition (accounts, TestFlight, internal QA) by making the codebase internally cloneable, branchable, and releasable.
Background
- May 15 feature sync (Chris): Bring Agent Assist in-house; back-and-forth with the outside developer on small changes had become too slow; the team already has API endpoints on the Attik side and does not want to keep re-translating minor technical requests.
- Getting the app into Attik repos was called out as the first concrete handoff step—it establishes internal control over the codebase before operational moves (accounts, distribution).
- Related milestones: work is sequenced with ATT-1680 (Attik accounts), ATT-1681 (TestFlight build), and ATT-1682 (internal testing)
Scope
Agent Assist application repository (primary)
- Decision needed: target hosting model (new Attik GitHub org/repo vs import into an existing org), default branch, CI skeleton, and secret scanning policy before first push of vendor history.
- Decision needed: how licenses, third-party SDKs, and vendor credentials in the imported tree are reviewed for redistribution.
Attik product repos (context only — avoid conflating names)
- In
attik-backendandattik-frontend, the stringagent-assistalready denotes portal permissions,AIChunkdataType, and the report chat tool path aroundsrc/routes/reportChunk.tsandscripts/uploadAssistMaterial.ts— that is inspector/client report coaching, not the standalone Agent Assist mobile app this ticket moves. No change required there unless product explicitly wants naming or docs aligned after the app repo lands.
References
Status: Completed
Log in to comment and vote
No comments yet
Be the first to share your thoughts.