Press ⌘J: a shell in every channel

The work is in the channel. The tools are in your terminal. ⌘J closes that gap.

Press ⌘J in any Ano channel and Claude Code opens with the channel’s context loaded. It can call workspace tools, local tools, and MCP servers, then post the output back into the same channel.

What ⌘J mounts

• Recent channel context.
• Every CLI, MCP server, and script the workspace has connected.
• Your local terminal tools.
• A return path back into the channel.

That makes ⌘J a shared-output shell, not a private terminal tab.

What it can reach

Anything addressable from a terminal:

• git and gh
• aws, gcloud, and kubectl
• stripe, hubspot, linear, and intercom
• psql, redis-cli, and repo scripts
• MCP servers from @ano-chat/skills or your own registry

If a service has no CLI or MCP server, wrap the action in a script.

First uses

Ask data a quick question.

stripe customers list --limit 5 --json | jq '[.[] | {id,email}]'

Draft from a connected system.

claude "draft a follow-up email for each at-risk deal in HubSpot"

Read across tools. Pull data from one source, enrich it through another, and post the combined answer where the team asked.

Example

Someone in #engineering asks whether last week’s release broke CI.

1. Press ⌘J.
2. Run gh run list --workflow ci --limit 50 --json conclusion,head_sha,createdAt.
3. Let Claude Code parse the JSON and summarize the first failure.
4. Post the summary back to #engineering.

The channel sees the command and the result. No copy-paste.

⌘J vs your terminal

Use your terminal for private exploration. Use ⌘J when the work should leave a trail in chat.

⌘J vs a coworker

Both use Claude. Ownership differs.

• ⌘J: You drive one session. The output is shared.
• Coworker: The workspace owns a persistent agent. Anyone can mention it. Its tools are curated.

If the same ⌘J task keeps falling on one person, promote it into a coworker.

Guardrails

• Do not use ⌘J for prompts the team should not see.
• Keep sessions short. Long multi-tool chains usually belong in a coworker or workflow.
• Remember local tools are included. Custom scripts in your PATH are part of the surface.

Questions

Does ⌘J cost anything? It uses the Claude account connected to the workspace.

Can two people press ⌘J in the same channel? Yes. Each session is separate, and the output shows who ran it.

Does it see secrets? Only secrets exposed through the workspace tool registry or your local environment.

Going deeper

Read How to use Claude Code with your team for the three-surface model, or What is an AI coworker? for the persistent workspace version.