プロダクトサーフェス
チームの居場所で、@Cohenta に聞く。
Slack、Microsoft Teams、ChatGPT、Claude に常駐するチームメンバー。CLI と API にも対応。Runner は1つ。キーはあなたのキーチェーンに。
cohenta install slack1人のチームメンバー
どこでも、同じ一言で。
Slack ファースト
あなたのアプリ。あなたのトークン。
コマンド一つ — cohenta install slack — で Slack のアプリ作成ページが Cohenta のマニフェスト付きで開きます。トークンは Slack があなたに発行し、あなたのキーチェーンに保存されます。Cohenta が見ることはありません。
Runner は Slack Socket Mode 経由でアウトバウンド接続します — 外向きの WebSocket のみで、インバウンドポートは不要。ファイアウォール内のラップトップで十分です。
@Cohenta in channels and threads
Bring it into a channel or a thread like any teammate: a brief, a question, a change request.
Live status while it works
Plan, draft, render — the ticks land in the thread while the engine works, so the channel sees progress without asking.
Approval buttons where you asked
Ready work arrives with Approve and Request changes. The run holds until someone presses one.
全 7 チャネル
@Cohenta が応答するすべての場所。
チームが使うチャットで会話し、システムが動く場所で自動化する — 自由に組み合わせて、すべて同じエンジンに届きます。
Where teams already talk
Your own app, your tokens — status and approvals land in the thread.
For M365 organizations
A customer-owned Entra registration and Teams app package, deployed in your Azure from provided templates. Adaptive Card approvals, and proactive pings when work is ready for review.
Through a secure tunnel
Connect ChatGPT to your Runner over OpenAI’s secure outbound tunnel — nothing inbound. Start runs and check status from a ChatGPT conversation.
Local, automatic
The plugin starts your local Runner over MCP automatically. Campaigns from the same terminal you work in.
Connector plus review view
A custom connector reaches your hosted Runner over remote MCP. An interactive review view inside Claude shows campaign status and assets — no separate dashboard.
For pipelines
The same MCP connector, called from code: start, monitor, and fetch campaigns programmatically.
Direct automation
Talk to the Runner itself. Script installs, runs, status, and retrieval into jobs you already operate.
ゼロ・カストディ
7 つの入口。1 つの Runner。
小さなエンジン — ラップトップ、サーバー、コンテナ、またはクラウド。キーはご自身で用意し、設定には参照情報のみを保存します。
Nothing to hand over
Cohenta never receives or stores your provider keys, publishing credentials, canonical assets, or campaign state.
Shared only where you chose
Messages you send in Slack or Teams are processed by those platforms; prompts go to the model providers you configured. Data is shared only with the platforms and providers you have chosen.
A cloud that stays out of the way
Cohenta’s cloud verifies licenses, serves signed updates and docs, and collects optional anonymous telemetry. It is never in the execution path.
一貫したアイデンティティ
一つのキャンペーン、すべての入口。
Slack で始め、Teams や Claude で確認する。同じキャンペーン、同じ状態 — 正規のレコードはあなたのもとに。
最後のゲート
承認を押すまで、一時停止。
The run waits at the gate
The pause is durable — it survives restarts and waits as long as you need. Nothing moves until a decision arrives, and ad creative always lands paused.
A button, never an inference
Approve, Request changes, or Reject — in Slack or Teams — resumes that exact paused run. Consent is a press, not a phrase a model read into your message.
Grounding gates flag, never fix
An untraceable claim gets flagged and annotated for review — never silently rewritten, never silently blocked. Publishing waits for a separate, explicit confirm.
Common questions
Asked and answered.
Is Cohenta a Slack bot?
Do I need to open a port or expose an endpoint?
Where do my Slack tokens live?
What does Teams need that Slack doesn’t?
How do I use it from Claude?
So is Cohenta an MCP server?
Can I start a campaign in Slack and approve it somewhere else?
Is there still a web console?
Your move
Slack に @Cohenta を追加する。
Runner をインストールし、コマンドを1つ実行して @Cohenta をメンション。明示的な確認なしには何も公開されない。