Anthropic Unveils โ€œChannels,โ€ a New Way to Control Claude Code Sessions Directly from Mobile


Anthropic has introduced Channels, a new feature that makes it much easier to use Claude Code in mobile environments. With this update, users can control their AI coding agent through messaging apps like Telegram and Discord, sending instructions from their smartphones as casually as they would text a friend.

At launch, Channels supports Telegram and Discord first. This means users no longer need to be sitting in front of a desktop development setup to interact with an active Claude Code session. Whether they are commuting, away from their desk, or simply on the go, they can reconnect to an existing session and send prompts in real time. Requests like โ€œcheck that error again,โ€ โ€œsummarize the test results,โ€ or โ€œcontinue refactoring that codeโ€ can now be handled directly from a mobile device.

What makes this update especially interesting is how it expands the development environment into communication tools people already use every day. Until now, coding agents were typically accessed through traditional developer interfaces such as IDEs or terminals. With Channels, familiar messaging apps themselves become the interface for directing the agent. Instead of learning a new workflow, users can collaborate with AI in an environment that already feels natural and intuitive.

Another important aspect is continuity of context. This is not just about sending isolated commands from a phone. Users can stay connected to the flow of an existing session and continue work without losing momentum. That makes the feature especially practical for developers who are in meetings, traveling, or working asynchronously with teammates. Even when they are away from their main machine, they can still monitor progress and provide instructions as needed.

Ultimately, Channels makes AI coding agents more accessible, more lightweight, and more integrated into everyday work. It reflects a broader shift away from development environments tied to a single device or location, and toward workflows that can continue anywhere. If Anthropic expands platform support and continues refining the experience, messenger-based AI development workflows could become mainstream sooner than many expect.


Today's News/Tips

What are codec and digital container format?

What are codec and digital container format?

Although you generally do not need to understand these two terms to use oCam, you should know them if you want to use the extended functions in oCam.

Codec and digital container format have multiple meanings, but here we explain only the meanings used for oCam.

First, a digital container format refers to common container formats such as AVI, MP4, and MOV.


Wikipedia has more detailed explanations.

http://ko.wikipedia.org/wiki/%EB%94%94%EC%A7%80%ED%84%B8_%EC%BB%A8%ED%85%8C%EC%9D%B4%EB%84%88_%ED%8F%AC%EB%A7%B7


A container format, also called a wrapper format, is a metadata file format that defines how different data components can coexist within a computer file.

In simpler words, AVI, MP4, MOV, FLV, and similar formats refer to the file structure that determines how video or audio data is stored.

And the data stored in that container is related to codecs.


The definition of a codec is described in Wikipedia as follows.

http://ko.wikipedia.org/wiki/%EC%BD%94%EB%8D%B1


A codec (short for coder-decoder) is hardware or software that can encode and decode, or both, a data stream or signal. It also refers to the algorithm used to do so. In telecommunications, the term originally referred to sender and receiver devices, known as a โ€œcoderโ€ and โ€œdecoder,โ€ which originated in 1980s America.

A codec includes software that compresses or decompresses data using compression functions, or devices and software that convert media such as sound and video into different formats.

To explain more simply, in current oCam usage, codecs are used to encode screen data into video, generating encoded video and audio data, and this data is saved as a file according to the container format selected in oCam.

Examples of codecs that we commonly know are XVID, MPEG-1, MPEG-2, MPEG-4, and H264.

For example, if there is a file with an AVI extension, then the digital container format is AVI, and the stored video and audio are saved using the AVI-defined structural format.

At that time, the stored video data may be H264, MPEG-4, and so on, while the audio data may be MP3, PCM, etc.

OhSoft - secretfolder The File Appears to Be Encrypted
oCam - howto How to Record Gameplay