Skip to content

Plan: Slack live cards for coding-session progress #8

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Yeshwanthyk wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Plan: Slack live cards for coding-session progress #8

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions LOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -285,3 +285,5 @@ results.
**Compile-in bundled extensions.** Restored the compile-all decision: approved shelf packages are generated into the executable instead of being copied from a checkout or downloaded from GitHub. A catalog generator emits metadata, Bun `type: "file"` embeds, and Pi factory imports. `extensions list/show` read that metadata; `extensions add` selects an ID already in the binary and provisions owned automations from embedded files without copying the package. Runtime loads Profile-owned paths plus selected bundled factories and embedded skills, with required `pi-packages`, `extension-authoring`, and `ziggy-operations`. Profile-local packages still win on collision.

**Compile-in skill copy.** Corrected required `pi-packages` guidance so `extensions add` selects a compiled ID and provisions owned automations from embeds instead of installing an approved remote package into the Profile.

**Slack live-cards plan.** Recorded how Slack Thinking Steps (task/plan stream chunks) map onto Ziggy's current placeholder and `Using <tool>…` stack, after checking Hermes `main` (native cards still unmerged; live per-tool status shipped) and Slack/Linear docs. Implementation stays sliced: stream identity + typed API, native stream as the working message, tool cards, path previews, then long-turn rollover. See `docs/research/slack-live-cards-plan.md`.
5 changes: 5 additions & 0 deletions docs/research/slack-agent-feedback-options.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -366,6 +366,11 @@ That lifecycle statement is Ziggy design guidance, not a Slack API contract.
- [`chat.startStream`](https://docs.slack.dev/reference/methods/chat.startStream/)
- [`chat.appendStream`](https://docs.slack.dev/reference/methods/chat.appendStream/)
- [`chat.stopStream`](https://docs.slack.dev/reference/methods/chat.stopStream/)
- [Thinking Steps announcement (2026-02-11)](https://docs.slack.dev/changelog/2026/02/11/task-cards-plan-blocks)
- [Make your AI agent think out loud in Slack](https://slack.dev/slack-thinking-steps-ai-agents/)
- [`task_card` block](https://docs.slack.dev/reference/block-kit/blocks/task-card-block)
- [`plan` block](https://docs.slack.dev/reference/block-kit/blocks/plan-block)
- Ziggy follow-up: [Slack live cards plan](./slack-live-cards-plan.md)
- [`chat.postMessage`](https://docs.slack.dev/reference/methods/chat.postMessage/)
- [`chat.update`](https://docs.slack.dev/reference/methods/chat.update/)
- [Sending and scheduling messages](https://docs.slack.dev/messaging/sending-and-scheduling-messages/)
Expand Down
Loading