What it is
The project AI agent is a chat on the project page (sparkles button, bottom right). It is not a separate CLI and it is not on the rest of the dashboard. Hamdek.sh is the hands: the model never receives your SSH keys. It can only call platform tools.
The agent is included on Studio and Agency projects. API keys are stored on the project (Settings → AI), not on your user account. Free and Solo cannot run the agent until the project is on Studio or higher.
Set up a provider
- Open the project → Settings → AI.
- Choose Claude (Anthropic), ChatGPT (OpenAI), Cursor, Gemini, or an OpenAI-compatible endpoint (OpenRouter, Groq, Ollama).
- Paste the API key, optionally set the model, then Test.
- Mark one connection as default.
Platform admins can also add a shared key under Admin → Connections. The project key is used first.
How to use it
- Open any Studio or Agency project.
- Click the sparkles button.
- Start a new chat or reopen a previous one. Full history is kept per chat.
- Ask in plain language. You do not pick a branch first. The agent already knows the project plan, subscription number, environments, and staging count. It only uses a branch when the question needs database, logs, or GitHub.
- Optional modes:
- Database report — read-only SQL / Odoo lookups. No code changes.
- Investigate a bug — logs, deployments, SQL, and source files. A proposed fix, no commit until you confirm.
- Change code — outline the files first; commits only after you say apply/commit.
- Odoo records — ORM-style reads.
If you type something ambiguous (“fix partners”), the agent should offer those options instead of writing immediately.
What it can access
- Project facts in the prompt: plan, subscription number, staging count, environment list, GitHub, server.
- Read-only PostgreSQL on a chosen environment (SELECT / WITH only, time limit, truncated results).
- Odoo
search_read when that environment is up.
- Container logs and Hamdek.sh deployments.
- GitHub files. Commits use your GitHub login and trigger the existing webhook deploy.
Safety
- SQL writes and DDL are blocked.
- API keys are encrypted at rest on the project.
- Code writes require Developer (or higher) on the project and a GitHub token with repo access.
- Viewers cannot use the agent.