# Offene Punkte — bei jedem Start prüfen und abhaken

1. Herrn Hinz über Vertex & Co aufklären — für Dumme: die Claude-Zugangswege (Abo/oauth, API-Key, Vertex, Bedrock) von Grund auf verständlich erklären. Grundlage für die geplante Vertex-Integration als dritter credentialType (env-Pool).

jq -Rs '{systemMessage: ., hookSpecificOutput:{hookEventName:"SessionStart", additionalContext: .}}' /home/marcuh/claude-projects/ai-control/OFFENE-PUNKTE.md


# Offene Punkte — bei jedem Start prüfen und abhaken

1. Herrn Hinz über Vertex & Co aufklären — für Dumme: die Claude-Zugangswege (Abo/oauth, API-Key, Vertex, Bedrock) von Grund auf verständlich erklären. Grundlage für die geplante Vertex-Integration als dritter credentialType (env-Pool).


das funtioniert ja
ok -- die ai aqpp ist immer noch 2mal im Starter
Sie sgeht auf aurostart - satrtet aber bniucht


CronCreate CronDelete CronList DesignSync EnterPlanMode EnterWorktree ExitPlanMode ExitWorktree Monitor NotebookEdit PushNotification RemoteTrigger SendMessage TaskCreate TaskGet TaskList TaskOutput TaskStop TaskUpdate WebFetch WebSearch


claude claude-code-guide Explore general-purpose Plan statusline-setup

- claude: Catch-all for any task that doesn't fit a more specific agent. FleetView's default when no agent name is typed. (Tools: *)

- claude-code-guide: Use this agent when the user asks questions ("Can Claude...", "Does Claude...", "How do I...") about: (1) Claude Code (the CLI tool) - features, hooks, slash commands, MCP servers, settings, IDE integrations, keyboard shortcuts; (2) Claude Agent SDK - building custom agents; (3) Claude API (formerly Anthropic API) - API usage, tool use, Anthropic SDK usage. **IMPORTANT:** Before spawning a new agent, check if there is already a running or recently completed claude-code-guide agent that you can continue via SendMessage. (Tools: Bash, Read, WebFetch, WebSearch)

- Explore: Read-only search agent for broad fan-out searches — when answering means sweeping many files, directories, or naming conventions and you only need the conclusion, not the file dumps. It reads excerpts rather than whole files, so it locates code; it doesn't review or audit it. Specify search breadth: "medium" for moderate exploration, "very thorough" for multiple locations and naming conventions. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)

- general-purpose: General-purpose agent for researching complex questions, searching for code, and executing multi-step tasks. When you are searching for a keyword or file and are not confident that you will find the right match in the first few tries use this agent to perform the search for you. (Tools: *)

- Plan: Software architect agent for designing implementation plans. Use this when you need to plan the implementation strategy for a task. Returns step-by-step plans, identifies critical files, and considers architectural trade-offs. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)

- statusline-setup: Use this agent to configure the user's Claude Code status line setting. (Tools: Read, Edit)


- git-sync: Commit + Push aller persistent konfigurierten Projekt-Repos
- deep-research: Deep research harness — fan-out web searches, fetch sources, adversarially verify claims, synthesize a cited report. - When the user wants a deep, multi-source, fact-checked research report on any topic. BEFORE invoking, check if the question is specific enough to research directly — if underspecified (e.g., "what car to buy" without budget/use-case/region), ask 2-3 clarifying questions to narrow scope. Then pass the refined question as args, weaving the answers in.
- dataviz: Use this skill whenever you are about to create ANY chart, graph, plot, dashboard, or data visualization, in ANY output medium — an HTML or React artifact, inline SVG, plotting code in any library (matplotlib, plotly, d3, Recharts, …), an image/PNG you will render and upload, or a chart shared into Slack. Read it BEFORE writing the first line of chart code, choosing chart colors, building a stat tile / meter / KPI row, or laying out a dashboard. Produces visualizations that read as one system — elegant, accessible, consistent in light and dark — using a brand-neutral placeholder palette you swap for your own. Teaches a design-system-agnostic method: a form heuristic, a color formula with a runnable validator, mark specs, and interaction rules. A validated default palette is documented in `references/palette.md` — swap that file's values for your brand's. Triggers on: "chart", "graph", "plot", "data viz", "visualization", "dashboard", "analytics", "visualize data", "categorical colors", "sequential / diverging palette", "stat tile", "sparkline", "heatmap", "legend", "axis", "tooltip", "chart colors", "color by series".
- artifact-design: Design guidance and fundamentals for Artifacts.
- update-config: Use this skill to configure the Claude Code harness via settings.json. Automated behaviors ("from now on when X", "each time X", "whenever X", "before/after X") require hooks configured in settings.json - the harness executes these, not Claude, so memory/preferences cannot fulfill them. Also use for: permissions ("allow X", "add permission", "move permission to"), env vars ("set X=Y"), hook troubleshooting, or any changes to settings.json/settings.local.json files. Examples: "allow npm commands", "add bq permission to global settings", "move permission to user settings", "set DEBUG=true", "when claude stops show X". For simple settings like theme/model, suggest the /config command.
- keybindings-help: Use when the user wants to customize keyboard shortcuts, rebind keys, add chord bindings, or modify ~/.claude/keybindings.json. Examples: "rebind ctrl+s", "add a chord shortcut", "change the submit key", "customize keybindings".
- verify: Verify that a code change actually does what it's supposed to by exercising it end-to-end and observing behavior — drive the affected flow, not just tests or typecheck. Run before committing nontrivial changes; bootstraps this repo's project verify skill if none exists yet. Don't invoke it on a diff that only touches tests, docs, or other code with no runtime surface to drive (a change to product source always has one) — there's nothing to observe.
- code-review: Review the current diff for correctness bugs and reuse/simplification/efficiency cleanups at the given effort level (low/medium: fewer, high-confidence findings; high→max: broader coverage, may include uncertain findings; ultra: deep multi-agent review in the cloud). Pass --comment to post findings as inline PR comments, or --fix to apply the findings to the working tree after the review.
- simplify: Review the changed code for reuse, simplification, efficiency, and altitude cleanups, then apply the fixes. Quality only — it does not hunt for bugs; use /code-review for that.
- fewer-permission-prompts: Scan your transcripts for common read-only Bash and MCP tool calls, then add a prioritized allowlist to project .claude/settings.json to reduce permission prompts.
- loop: Run a prompt or slash command on a recurring interval (e.g. /loop 5m /foo). Omit the interval to let the model self-pace. - When the user wants to set up a recurring task, poll for status, or run something repeatedly on an interval (e.g. "check the deploy every 5 minutes", "keep running /babysit-prs"). Do NOT invoke for one-off tasks.
- schedule: Create, update, list, or run scheduled cloud agents (routines) that execute on a cron schedule. - When the user wants to schedule a recurring cloud agent, set up automated tasks, create a cron job for Claude Code, or manage their scheduled agents/routines. Also use when the user wants a one-time scheduled run ("run this once at 3pm", "remind me to check X tomorrow").
- claude-api: Reference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration.
TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens).
SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).
- run: Launch and drive this project's app to see a change working. Use when asked to run, start, or screenshot the app, or to confirm a change works in the real app (not just tests). First looks for a project skill that already covers launching the app; otherwise falls back to built-in patterns per project type (CLI, server, TUI, Electron, browser-driven, library).
- init: Initialize a new CLAUDE.md file with codebase documentation
- review: Review a GitHub pull request; for your working diff use /code-review
- security-review: Complete a security review of the pending changes on the current branch

git-sync deep-research dataviz artifact-design update-config keybindings-help verify code-review simplify fewer-permission-prompts loop schedule claude-api run init review security-review


Fehlerhafte KI-App startet nicht automatisch


Zum Autostart: aus der Ferne unklar. Doppelter Eintrag im Starter plus Nichtstart passt typisch zu zwei BTM-Registrierungen desselben Labels — eine davon veraltet (alter App-Pfad, z. B. von einem früheren Build), und macOS startet beim Login den toten Eintrag. Die tatsächlichen Registrierungen samt Pfaden zeigt `sudo sfltool dumpbtm`. Zum Prüfen im Projekt bräuchte ich ein Go.

---

Offener Punkt 1 (Vertex & Co, von Grund auf):

Es geht immer um dieselben Claude-Modelle — unterschiedlich ist nur, über welche Tür man reinkommt, wer die Rechnung stellt und wie man sich ausweist. Vier Wege:

**1. Abo / OAuth (das, was deine Pools jetzt machen)**
Du hast ein Claude-Abo (Pro/Max) bei Anthropic. Anmeldung läuft über den Browser (OAuth), das Ergebnis ist ein Token, das Claude Code im Keychain ablegt und automatisch erneuert. Bezahlung: fester Monatspreis, dafür Nutzungslimits (5-Stunden-Fenster). Kein Verbrauchszähler — ob du viel oder wenig nutzt, kostet gleich viel.

**2. API-Key (direkt bei Anthropic, Verbrauchsabrechnung)**
Statt Abo: Konto in der Anthropic Console (console.anthropic.com), dort Guthaben aufladen und einen API-Key erzeugen — eine statische Zeichenkette. Abgerechnet wird pro Million Tokens (Input und Output getrennt). Claude Code nutzt das, wenn `ANTHROPIC_API_KEY` gesetzt ist. Kein Login-Flow, kein Keychain nötig — der Key selbst ist der Ausweis.

**3. Vertex AI (Google Cloud)**
Dieselben Claude-Modelle, aber betrieben in Googles Cloud. Anthropic liefert die Modelle an Google, Google betreibt die Inferenz. Man hat kein Anthropic-Konto: Vertrag, Rechnung, Quotas und Datenverarbeitung laufen komplett über das eigene Google-Cloud-Projekt. Ausweisen tut man sich mit Google-Credentials (gcloud-Login bzw. Service-Account), nicht mit einem Anthropic-Key. Existiert, weil Firmen ihre Abrechnung und Compliance in der Cloud haben wollen, in der sie ohnehin sitzen. Claude Code schaltet man darauf um mit `CLAUDE_CODE_USE_VERTEX=1`, `ANTHROPIC_VERTEX_PROJECT_ID` und einer Region — die Google-Anmeldung muss in der Umgebung vorhanden sein.

**4. Bedrock (AWS)**
Exakt dasselbe Prinzip wie Vertex, nur mit Amazon: Claude-Modelle über AWS Bedrock, Rechnung von AWS, Ausweis über die üblichen AWS-Credentials. Claude Code: `CLAUDE_CODE_USE_BEDROCK=1`.

Für die geplante Pool-Integration heißt das: Weg 1 lebt im Keychain (dein heutiger credentialType), Weg 2–4 leben in Umgebungsvariablen. Ein Vertex-Pool ist deshalb ein „env-Pool": statt eines Keychain-Eintrags setzt der Starter beim Spawnen die Vertex-Variablen, und die Google-Anmeldung (ADC oder Service-Account-Datei) muss auf der Maschine liegen.


das funtioniert ja ok -- die ai aqpp ist immer noch 2mal im Starter  Sie sgeht auf aurostart - satrtet aber bniucht


NEIN
Autostart und Doppelter Eintrag
--> TODOS sind ein MERKLISTE niccht der Freischein, mich zuzutexten!!!!!!


Bash

osascript -e 'tell application "System Events" to get {name, path} of every login item'

Login Items auflisten


grep -rn --include='*.ts' --include='*.js' --include='*.swift' --include='*.json' -iE 'openAtLogin|setLoginItemSettings|SMAppService|LaunchAgent|autostart' /home/marcuh/projects/ai-control --exclude-dir=node_modules --exclude-dir=dist --exclude-dir=out -l

Autostart-Registrierungscode im Repo suchen


The user doesn't want to proceed with this tool use. The tool use was rejected (eg. if it was a file edit, the new_string was NOT written to the file). STOP what you are doing and wait for the user to tell you how to proceed.


[Request interrupted by user for tool use]


WAS HAST DU BVOR?


Zwei Lese-Schritte zur Diagnose:

1. `osascript` — die aktuellen Login-Items mit Pfaden auflisten, um zu sehen, worauf die zwei Einträge zeigen.
2. `grep` im Repo — die Stelle finden, an der die App den Autostart registriert (`setLoginItemSettings` / `SMAppService` / LaunchAgent).

Sonst nichts, keine Änderungen.


WÄRE SCHÖN , WENN ICH DAS WÜ?TE
KJETZT KOMMT DER GIMMICK: WARUM WILLSZT DU DAS


Weil beide Symptome am Pfad hängen dürften:

1. **Login-Items auflisten** — zeigt, auf welche zwei Pfade die Einträge zeigen. Vermutung: einer zeigt auf einen alten Build-/App-Pfad, der nicht mehr existiert. Das erklärt beides zugleich — doppelter Eintrag *und* kein Start (macOS startet den toten Eintrag).
2. **Grep im Repo** — zeigt, mit welchem Mechanismus die App sich registriert (Electron `setLoginItemSettings`, `SMAppService` oder LaunchAgent-Plist). Davon hängt ab, wo der doppelte Eintrag herkommt und wo man ihn sauber entfernt.

Ohne 1 weiß ich nicht, welcher Eintrag der tote ist; ohne 2 nicht, warum er entstanden ist.


ok


osascript -e 'tell application "System Events" to get {name, path} of every login item'

Login Items mit Pfaden auflisten


grep -rn -iE 'openAtLogin|setLoginItemSettings|SMAppService|LaunchAgent|autostart' /home/marcuh/projects/ai-control --exclude-dir=node_modules --exclude-dir=dist --exclude-dir=out -l

Autostart-Registrierungscode im Repo suchen


Error: Exit code 1
40:52: execution error: Not authorised to send Apple events to System Events. (-1743)


[Request interrupted by user]