# Keyboard.io mentions application-specific macros?

**URL:** <https://community.keyboard.io/t/keyboard-io-mentions-application-specific-macros/1760>\
**Category:** Help and Getting Started\
**Created:** [July 10, 2018, 4:31am UTC](https://community.keyboard.io/t/keyboard-io-mentions-application-specific-macros/1760 "2018-07-10T04:31:15Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![atimholt](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.keyboard.io/atimholt/32/1310_2.png) [@atimholt](https://community.keyboard.io/u/atimholt)\
**Post date:** [July 10, 2018, 4:31am UTC](https://community.keyboard.io/t/keyboard-io-mentions-application-specific-macros/1760/1 "2018-07-10T04:31:15Z")

</div>

I’ll mention first that I can live without it, it’s not a high priority for me.

…but [keyboard.io](http://keyboard.io) mentions application-specific macros. It’d be _nice_, I wouldn’t have to dedicated whole layers to firmware macros for each program I want to macro-up.

Is there an update or an ETA on this?

I’m running Windows 10.

---

<div class="post-metadata">

**Author:** ![algernon](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.keyboard.io/algernon/32/4404_2.png) [@algernon](https://community.keyboard.io/u/algernon)\
**Post date:** [July 10, 2018, 4:42am UTC](https://community.keyboard.io/t/keyboard-io-mentions-application-specific-macros/1760/2 "2018-07-10T04:42:18Z")

</div>

> [@atimholt](#):
>
> Is there an update or an ETA on this?

This is something that requires a program on the host side to help, [Chrysalis](https://github.com/Lepidopterarium/Chrysalis) will be used for. There is no ETA yet, as we need to get more basic features working first.

---

<div class="post-metadata">

**Author:** ![atimholt](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.keyboard.io/atimholt/32/1310_2.png) [@atimholt](https://community.keyboard.io/u/atimholt)\
**Post date:** [July 10, 2018, 4:52am UTC](https://community.keyboard.io/t/keyboard-io-mentions-application-specific-macros/1760/3 "2018-07-10T04:52:21Z")

</div>

I hope this isn’t too out of scope for this thread, but will Chrysalis work with custom firmware? I’m imagining something like a singular Chrysalis layer, or some kind of plugin that needs to be included. What I’m really hoping is that you won’t have to use a special .ino, or some kind of generated binary that precludes using your own.

---

<div class="post-metadata">

**Author:** ![algernon](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.keyboard.io/algernon/32/4404_2.png) [@algernon](https://community.keyboard.io/u/algernon)\
**Post date:** [July 10, 2018, 5:19am UTC](https://community.keyboard.io/t/keyboard-io-mentions-application-specific-macros/1760/4 "2018-07-10T05:19:40Z")

</div>

> [@atimholt](#):
>
> I hope this isn’t too out of scope for this thread, but will Chrysalis work with custom firmware? I’m imagining something like a singular Chrysalis layer, or some kind of plugin that needs to be included.

You will need the `Focus` plugin, and likely another one which we haven’t written yet, to track the application on the host side, so you can use it in macros. You won’t need a special layer, nor a generated binary or anything like it. (You will be able to use a `MACRO` layer, if so you wish, mind you, but that’s a choice, and not mandatory in any way.)

The goal is to allow Chrysalis to work with custom firmware, as long as a few necessary plugins are included.