Skip to content

Latest commit

 

History

History
23 lines (12 loc) · 2.38 KB

File metadata and controls

23 lines (12 loc) · 2.38 KB

Aiden Agent

Aiden Agent is a privately owned Electron application. Its only source repository is https://github.com/sambitcreate/aiden-agent.

Project memory

The .memory/ folder contains context and history from previous work on this project. Read the relevant files there before making changes, and keep them updated when work changes the implementation, architecture, decisions, or status.

UI design references

Before adding or materially restyling any UI element or component, always review both docs/chatgpt-desktop-ui-inspiration.md and docs/chatgpt-ui-element-specimen.html for interaction, styling, state, motion, and accessibility inspiration. Adapt the references to Aiden's existing visual language rather than copying them blindly, and use the semantic design tokens in renderer/styles.css and renderer/shared/appearance.ts instead of introducing one-off colors.

Release model metadata

models.dev may be contacted only by npm run models:refresh, the release refresh invoked by npm run dist, the scoped post-merge catalog workflow, or the user-initiated foreground Update model catalogs action in Settings → Providers. The live action may request only the fixed https://models.dev/api.json endpoint without credentials, cookies, prompts, chats, selections, custom endpoints, or a device identifier; its validated device-local cache is display-only and must never change runtime limits, routing, or selectable inventory. Never add a models.dev call to startup, normal development, unpacked builds, ordinary live-app reads, onboarding navigation, or background polling. Artificial Analysis data and credentials must never be bundled: the live Electron app may contact its fixed Free endpoint only after the user explicitly chooses Connect & fetch or Fetch latest with their own key, then reads the normalized device-local cache offline.

Papercuts

For complex workflows, record concise implementation friction in .papercuts/troubleshooting.md as it occurs.

Tests

When adding a feature or changing behavior, layout, configuration, or contracts, always check whether existing tests need updating and add or extend tests when coverage is missing. Run the relevant suites before finishing (npm run test, or the narrower scripts in package.json when the change is scoped). If a new test file is added, register it in the appropriate package.json test script so CI picks it up.