Телеграм канал «Vibecoding Haven (BotfatherDEV)»

Можна попросити поставити /goal ;)

і правда, він з іншого треда надіслав собі повідомлення

каааааайф

Codex може керувати сам собою)

Тобто - і створення розмов, закріплення, зміна назви, архівування, тощо

раджу до перегляду: https://youtu.be/3aMWv9FIu4o

Поки немає гпт5.6 - Тібо сказав що в кодексі вже 5кк юзерів і завтра скидають ліміти

Time to go /fast

Нахрюки пішли що сьогодні буде GTP-5.6

Взагалі багато на твітері хто здивований, що 5.6 не вийшло за 20хв після нового опуса))

Опус 4.8 вийшов)

Спробуйте це в codex

Look back over my recent work from the last 30 days, or all available history if shorter, and identify repeated manual workflows worth packaging.

Use available evidence in this order:

1. Recent Codex sessions and task summaries.
2. Codex Memories and rollout summaries to find patterns repeated across sessions.
3. Chronicle, if enabled, to spot repeated work outside Codex.
- Use Chronicle for discovery only.
- Confirm important details in the relevant source system when possible.
4. Existing skills, custom agents, and automations, so you reuse or extend what already exists instead of duplicating it.

Look broadly for work that is repeated, time-consuming, error-prone, context-heavy, or benefits from a consistent process.

Include workflows across:
- coding
- research
- writing
- planning
- communication
- operations
- analysis
- personal administration

Only act on a candidate when it:

- occurred at least twice, or is clearly likely to recur and costly to repeat;
- has stable inputs, a repeatable procedure, and a clear output or stopping condition;
- would materially improve speed, quality, consistency, or reliability;
- is not already adequately covered.

Choose the smallest appropriate form:

- Skill: a reusable workflow or playbook.
- Custom subagent: a bounded specialist role or investigation task suitable for delegation.
- Automation: a scheduled or recurring check, report, reminder, or monitor.
- Skip: work that is too one-off, ambiguous, sensitive, or poorly evidenced to package.

First produce a compact shortlist with:

- repeated workflow
- supporting evidence and dates
- frequency/confidence
- recommended form: skill, subagent, automation, extend existing, or skip
- why it is or is not worth creating

Then create only the high-confidence missing items.

Keep them narrow, practical, source-aware, and easy to validate.

Do not create speculative, overlapping, or overly broad assets.

Finish with:

- what you created or extended
- what you deliberately skipped
- what needs more evidence before packaging