5 Commits

Include renames

Author	SHA1	Message	Date
ZacharyZhang-NYandClaude Opus 5.5	245ff66336	1.5.1: refined office, chat in the app language, current OpenAI models, own connector keys ... - Home: the goal title box is two line boxes tall (2.8em), so a third line no longer peeks out. - Chat messages, reply fallbacks and assignment DMs follow the app display language; tasks and documents keep the working language. - OpenAI and GPT-account model lists match OpenAI's current line-up; default gpt-6.1-sol. - Onboarding connectors step takes the operator's Composio and logo.dev keys, then lists the toolkits the Composio project enables; without a key Connectors leaves the sidebar. - Google Antigravity removed end to end (migration 111), with the remote-revocation path only it used. - Office: 2x pixel people with outlines, rim light, walk, typing and blink; dithered real-clock lighting; detailed furniture and floors. - Per-agent model picker lists the provider's whole model list, live when connected. - Chat wake context breaks same-millisecond ties by insertion order; the mid-run inbox dedupes by message id. - The stored "clock" theme reads back instead of falling to "system". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-09 21:12:19 -04:00
ZacharyZhang-NYandClaude Opus 5.5	7eef3d459f	Q88: a sign-in is saved only if a run can use and renew it ... Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-08 15:02:12 -04:00
ZacharyZhang-NYandClaude Opus 5.5	56b0594f91	Move Composio, logo.dev and Antigravity keys into Settings ... The three third-party keys were hardcoded or read from the environment. Operators now enter them in Settings > Integrations; they are stored encrypted in the app-wide integration_keys table (migration 058). An agent holding connector grants fails loudly when no Composio key is saved. The goal-review test no longer depends on absolute dates. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-08 01:34:14 -04:00
ZacharyZhang-NY	327de38e78	Kimi Code joins as an OAuth plan provider: RFC 8628 device flow, verified against the live endpoints ... - New oauth/kimi-code-flow.ts mirrors the official kimi-cli: form-encoded device_authorization + token polling at auth.kimi.com with the required X-Msh-* device headers, pure poll interpreter, 15-minute tokens refreshed via refresh_token grant - Agent loop runs chat completions at https://api.kimi.com/coding/v1 with the Bearer access token; default model kimi-for-coding (kimi-for-coding-highspeed for Allegretto+ plans) - Live model listing via /coding/v1/models; credential refresh wired into the turn credential resolver - Migration 057 seeds the provider (disabled) into existing organizations - Wire protocol probed live: device code issued, authorization_pending poll observed, 401 envelope on the coding API confirmed	2026-07-10 17:18:31 -04:00
ZacharyZhang-NY	07d0b4587d	Promote AgentCompany-New to the repository root and retire the old app ... The legacy application - its src, tests, landing site, promo assets, docs, release tooling, CI workflows, and root configs - leaves the tree; it stays reachable in history. Everything under AgentCompany-New moves up unchanged: same package name, so the production userData/database path is untouched, and e2e/build scripts already resolved paths relative to the project. The developer cred.txt stays gitignored at its new location. Full verify:ci passes from the new root.	2026-07-07 00:04:13 -04:00